coverage. We’re backed by industry leaders in insurance and tech, and we still have room to grow — that’s where you come in. Our Backend Software Engineer can expect to work with the latest backend technologies and progr…
Backend Developer jobs in Boston, MA
Backend developers build the server-side logic, APIs, and data layers that applications run on. The job is designing services that stay correct, fast, and secure as usage 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 backend developer roles
12 shown of 757 · sorted by freshness
fun, collaborative, efficient, and adaptive team. As a Senior Backend Engineer focused on data integration, you will own how data is... ...designing, building, and consuming REST APIs ~ Extensive experience developing fo…
engineering simulation market. Role Overview We are looking for a Backend Software Engineer to help us design and implement scalable... ...for a web API in a multi-physical simulation context. Develop and maintain hybrid…
Veeva Systems is a mission-driven organization and pioneer in industry cloud, helping life sciences companies bring therapies to patients faster. As one of the fastest-growing SaaS companies in history, we surpassed $3B…
code repositories Implement test strategies analyse results and coordinate bug fixes to uphold the software quality standards Develop user training programs documentation and support frameworks to ensure a smooth transit…
________This is an example!________ PLEASE READ: these jobs are testing jobs of Lever's testing environment - please do not apply for this job. Lever was founded ten years ago to tackle the most strategic challenge that…
data pipeline underneath it: get that wrong and the agent's calls get worse, at the customer's expense. We're looking for a Senior Backend Engineer to join our core engineering team. You'll design and build the data pipe…
financial opportunity should be more personalized and fair. We develop innovative technologies that provide underserved and overlooked... ...Manager to join our engineering team, with a focus on leading backend developme…
homes and businesses. The Opportunity We're looking for a backend- focused engineer to join our lean, high-leverage engineering... ...scalable backend services that power our core marketplace platform Develop and maintai…
Job Title: Senior Java Backend Developer Job Duration: 8+ Months Job Location: Boston, MA (Hybrid 2 3 days onsite) Need a local candidate Job Summary We are seeking an experienced Senior Java Backend Developer to join th…
Role: Backend Engineer Location: Fully Remote (Headquarters in Boston, MA) Working Hours: 9-5 EST Onsite: Travel every 8-10 weeks for a multi-day onsite Join Us At Product Genius, we don't tell people what to do—we give…
quality to provide personalized insights into users' fitness, health, and recovery. As a Backend Software Engineer II, you will build on WHOOP’s generative AI capabilities to develop and maintain exciting, member-facing…
What backend developers earn in Boston
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $44–$62 | $92k–$128k |
| Mid level | $62–$89 | $128k–$186k |
| Senior | $86–$117 | $179k–$243k |
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
Design an API for a feature like comments or notifications.
Clarify requirements, then cover endpoints, data model, pagination, and error handling. Mentioning versioning and rate limits shows production experience.
How would you find and fix a slow database query?
Walk through reading the query plan, checking indexes, and considering caching or denormalization. Ground it in a query you actually fixed.
How do you keep two services consistent when both need to update data?
Discuss transactions, idempotency, and eventual consistency with outbox or saga patterns. Acknowledge tradeoffs rather than promising perfect consistency.
What do you monitor on a service you own?
Name the basics — latency, error rate, saturation — plus business-level signals. Bonus points for talking about alerts you tuned to reduce noise.
Tell me about a production incident you handled.
Structure it: detection, mitigation, root cause, prevention. Emphasize what changed afterward, not just the firefight.
How do you approach securing an API?
Cover authentication, authorization, input validation, and secrets handling. Naming OWASP-style risks concretely is enough; you are not expected to be a security engineer.
When would you choose a message queue over a direct call?
Talk about decoupling, retries, and absorbing spikes, and be honest about the added complexity of async debugging.
Resume tips that move the needle
For backend developers specifically — generic advice costs you here
State scale where you can: requests per second, data volume, or number of services — it is the fastest way to signal seniority.
Name the databases and infrastructure you ran in production, not just languages.
Describe reliability work — migrations without downtime, incident reduction, test coverage on critical paths.
If you designed an API others consume, say so and note how many teams or clients depend on it.
Avoid listing every framework you have touched; two stacks with depth read better than eight without.
Where this role goes
Typical progression
Applying for backend developer 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.