above). Typical work hours are Monday-Friday, 8:00am-5:00pm local time. WHO WE ARE LOOKING FOR We are looking for a Senior Software Engineer to design, build, and operate foundational services for our enterprise AI platf…
Software Engineer jobs in Philadelphia, 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
9 shown of 690 · sorted by freshness
Job Title: AWS Engineer Location-Type: Remote Start Date Is: ASAP Duration: (contract, perm, etc) Contract to Hire Compensation... ...: Substantial experience building and running production software for seven years or m…
The FreedomPay Commerce Platform is the technology of choice for many of the largest companies across the globe in retail, hospitality, lodging, gaming, sports and entertainment, foodservice, education, healthcare and fi…
By joining our team as a Jr. Forward Deployed Engineer (FDE) you will serve as a key member of our Data and AI Solutions team and partner... ...2027 preferably in fields such as Computer Science Mathematics Software Engi…
By joining our team as a Jr. Forward Deployed Engineer (FDE), you will serve as a key member of our Data and AI Solutions team and partner with our customers to understand their most complex challenges and design and imp…
company (Nasdaq: CRWV) in March 2025. Learn more at . What You’ll Do: Applications Engineering, part of CoreWeave’s Data Infrastructure organization, builds the software CoreWeave uses to plan and operate its own infrast…
AVEVA is creating software trusted by over 90% of leading industrial companies. Salary Range: $145600.00 - $290000.00 T his... ...attainment and/or training. Job Title: Product Security Software Engineer Location: Philad…
Description The Software Engineer Client Data Services supports client data integration file-based workflows reporting automation and production issue resolution. This role partners with engineering infrastructure operat…
company (Nasdaq: CRWV) in March 2025. Learn more at . What You’ll Do: Applications Engineering, part of CoreWeave’s Data Infrastructure organization, builds the software CoreWeave uses to plan and operate its own infrast…
What software engineers earn in Philadelphia
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $39–$54 | $81k–$113k |
| Mid level | $54–$78 | $113k–$162k |
| Senior | $75–$104 | $157k–$216k |
Adjusted for the Philadelphia 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 Philadelphia?
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.