The individual will work with a team of dynamic and innovative engineers to develop new capabilities supporting the front end... ...modernization of the front end processing services. The Software Engineer develops, main…
Software Engineer jobs in Baltimore, MD
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 635 · sorted by freshness
is rare within our industry. We are seeking an experienced Software Developer who will provide full-stack java software development... ...the Data Transformation Solutions (DTS) TTO. The candidate will engineer end-to-en…
security tool. Essential Duties and Responsibilities: •The engineer will be heavily involved with the creation, maintenance, and... ...into the system. •Analyze user requirements to derive software design and performance…
Job Overview AEVEX Maritime Systems is seeking a Lead Software Platform Engineer to provide technical leadership for the shared software delivery platform supporting our uncrewed maritime systems. Reporting to the Direct…
designing, modifying, developing, writing, implementing, and testing software and software applications. The primary role will be leading... ...software development and maintenance with a BS in Electrical Engineering, Co…
SECURITY CLEARANCE: TS/SCI with both Polygraphs is required POSITION: Sr. Back-End Software Engineer / (AE,L4) REQUISITION: NIN-AE4-30.051925 LOCATION: Laurel, Maryland SEAT LOCATION: Emerson JOB DESCRIPTION: As part of…
Job Title: Senior Software Engineer Cloud & Data Services Job Category: Engineering Time Type: Full time Minimum Clearance Required to Start: TS/SCI with Polygraph Employee Type: Regular Percentage of Travel Required: No…
annual health and technology allowances, and access to a state-of-the-art technology lab. Learn more at Your Mission As a Software Engineer III, you will work on high-impact analytics development projects that support cr…
SECURITY CLEARANCE : TS/SCI with both Polygraphs is required POSITION: Senior Software Engineer REQUISITION: NIN-AE4-17.022425 LOCATION: Ft. Meade, Maryland JOB DESCRIPTION: • The Software Engineer will be heavily involv…
traditionally defined problem space. We bring Public and Private, Civilian and Military expertise to every case. We are hiring a Software Engineer (Data Management) in Linthicum Heights, MD. Position location is subject…
Job Title: Senior Software Engineer - Machine Learning & Cloud Technologies Job Category: Engineering Time Type: Full time Minimum Clearance Required to Start: TS/SCI with Polygraph Employee Type: Regular Percentage of T…
What software engineers earn in Baltimore
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $38–$53 | $79k–$110k |
| Mid level | $53–$76 | $110k–$158k |
| Senior | $73–$101 | $152k–$210k |
Adjusted for the Baltimore 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 Baltimore?
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.