Lead Engineer, Electronics System Engineer Lead Engineer, Electronics System EngineerTowson, Maryland, United StatesCome make the world... ...scope creep.Collaborate closely with mechanical, hardware, and software teams…
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
12 shown of 246 · sorted by freshness
Position Summary Lead Cloud Infrastructure Engineer II - Workplace Engineering/M365 AI & Engineering helps organizations build, deploy, and operate integrated solutions across software, data, AI, networks, and hybrid clo…
Job Title: Software Engineer - Windows IntegrationJob Category: EngineeringTime Type: Full timeMinimum Clearance Required to Start: TS/SCI with PolygraphEmployee Type: RegularPercentage of Travel Required: Up to 10%Type…
Agency: Social Security AdministrationDepartment: Other Agencies and Independent OrganizationsSub agency: Chief Information Officer (CIO)Salary: Starting at $121,785 Per year (GS 13)Dates: Open 09/28/2026 to 10/02/2026Sc…
Troubleshooting There is a possibility of an extension or conversion to FTE. We are seeking an experienced NICE SmartReach / LiveVox Platform Engineer to join our Contact Center and Telephony team. This role requires dee…
variety of business applications, helping clients optimise operational efficiency. These individuals analyse client needs, implement software solutions, and provide training and support for seamless integration and utili…
s Degree in computer science, information technology, network engineering, or a related field (Required) One year of relevant education... ..., CiscoWorks and network analyzers; isolate hardware vs software/ firmware/OS…
ensuring the integrity of access to data.QualificationsRequired:BA/BS Degree in Computer Science, Cyber Security, Information Security, Engineering, Information Technology, Finance, Business, or relevant fields.Overall m…
Job-ID27127872Reference26-01207Information Technology - Engineer, Software Sr PURPOSE: Performs complex analysis, design, development, testing, and debugging of computer software ranging from operating system architectur…
agile environment and follows best practices for agile/scrum and meets sprint commitments.Required skills and experience:7+ years: Software development experience (portal application as well as client/server applications…
The Impact You'll MakeAs an Application Engineer with Danfoss Climate Solutions, you’ll use your HVAC and refrigeration expertise to help original equipment manufacturer (OEM) customers across Canada and North America so…
Software Engineer (MongoDB) *This role is eligible for up to 1 day a week of telework* Summary Join a mission-focused team developing modern, automated capabilities that improve how enterprise systems manage security, da…
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.