Job Description Job Description Job Title: Software Perception Engineer Job Description The Software Perception Engineer designs, implements, and tests advanced perception algorithms for mobile off-road machines, with a…
Software Engineer jobs in Pittsburgh, PA
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it grows.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open software engineer roles
11 shown of 542 · sorted by freshness
passion towards our work. We warmly welcome individuals of similar mindset to join our ranks. What You'll Be Doing As a Software Engineer, you will be collaborating with an interdisciplinary team focusing on developing r…
trains, metros, trams, maintenance services and integrated systems. More than a job: a mission Join us in Pittsburgh as a Software Engineer and help shape the future of mobility. Here, your expertise will directly contri…
Infrastructure team and play a key role in developing and enhancing mission-critical dispatching software that supports the safe and efficient movement of rail networks. As a Software Engineer, you will contribute to the…
Description: Hybrid 4 days onsite in Pittsburgh, PA Our client seeks a Senior Software Engineer to build a secure, fault-tolerant Azure-based platform for high-volume data ingestion, ledger-style recordkeeping, and analy…
Job Description Job Description Title - Software Engineer - Power Apps Location- Pittsburgh, PA - 5 days Onsite Roles and Responsibilities: Health checks, process improvement, potentially on call for issues and releases,…
operational demands, the front line gets what it needs to succeed. Job Description We are seeking a skilled and dedicated software engineer to join our Engineering team. As a Software Engineer at Air, you show a clear pa…
diverse, innovative and collaborative candidates who want to impact the world in a positive way. To learn more visit: As a Software Engineer on our Labelling and Data Automation team, you will build pipelines, tools, and…
Job Description Job Description Software Engineer II Summary Do you have a passion for building market leading software solutions for the Metals Industry? As the biggest full-liner for the metals industry, we deliver by…
work. We warmly welcome individuals of similar mindset to join our ranks. For this role, we are seeking a solid Embedded Software Engineer who can take full end-to-end ownership of software for our robotics components an…
mindset to join our ranks. For this role, we are seeking a solid engineer who can take full end-to-end ownership of cloud projects.... ...and keep it running smoothly. What You'll Be Doing As a Software Engineer focusing…
What software engineers earn in Pittsburgh
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$49 | $73k–$102k |
| Mid level | $49–$70 | $102k–$146k |
| Senior | $68–$93 | $141k–$194k |
Adjusted for the Pittsburgh market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through a project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
Applying for software engineer jobs in Pittsburgh?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.