global economy, yet the way factories are fundamentally run have used the same control philosophies, manual operations, and legacy software for the past 60 years. Laminar deploys state-of-the-art patented sensors and edg…
Software Engineer jobs in Boston, MA
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 2,327 · sorted by freshness
Tittle: Senior Full Stack Software Engineer Location: 101 Summer Street, 2nd Floor, Boston, MA 02110 Job Description We are seeking an experienced Senior Full Stack Software Engineer to join our engineering team and help…
Mission Summary: The Data Platform team is the vital link between our company's expansive data and the engineering teams that rely on it. We architect and operate the core services and infrastructure necessary to transfo…
creators to own their own destiny. The mission of the Platform Engineering team is to provide infrastructure primitives, platforms,... ...core platform services and developer experience. As a Senior Software Engineer, yo…
About the Role Companies have multiple founding moments and Pelico is going through a new one. You would be one of the founding engineers of our new agentic platform, building alongside a small, super talented, high-bar…
embedding it at every stage of R&D. Come build the future of biological discovery with us. Position Overview As a Senior Software Engineer you’ll work to build the connective tissue of our data platform, in both what you…
Developer Experience is a crucial function that empowers our engineers to excel in their craft. As a technical leader in the Platform... ...feedback. Implement feedback loops that integrate quality into software developm…
building an AI-first company—and that starts with how we support and scale our people. We’re looking for a Lead People Technology Engineer to be the first dedicated AI engineer within our People Technology (KPPL) team. A…
Protecting our members’ data and ensuring our systems scale securely and reliably is core to this mission. WHOOP is hiring a Software Engineer II focused on backend development to build and enhance systems that power our…
networking technology to the military in months, not years. ABOUT THE TEAM The Software Platform team at Anduril is dedicated to building the products and systems that empower our engineering teams to develop, test, and…
Location: On-site onlyType: Full-TimeCompany OverviewWe are a dynamic, growing company in the digital health sector, revolutionizing healthcare through innovative technology. As we expand our digital presence, we're seek…
scaling globally alongside Fortune 500 customers, backed by Bessemer, Craft, and TLV. About the role: As a Full Stack Software Engineer, you'll work across the stack to design, implement, and ship high-quality workflows…
What software engineers earn in Boston
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $46–$64 | $96k–$134k |
| Mid level | $64–$92 | $134k–$192k |
| Senior | $89–$123 | $186k–$256k |
Adjusted for the Boston 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 Boston?
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.