> Markdown version of [/jobs/ext/4503567-staff-backend-engineer-data-platform](https://www.wearedevelopers.com/jobs/ext/4503567-staff-backend-engineer-data-platform). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Staff Backend Engineer, Data Platform

- **Company:** OSMO
- **Location:** Elizabeth, NJ, United States
- **Experience:** Starter
- **Contract:** Internship / Graduate position
- **Skills:** Application Programming Interfaces (APIs), Databases, Data Infrastructure, Python (Programming Language), Performance Tuning, SQL Databases, TypeScript, Workflow Management Systems, ReactJS, Backend, Golang, Programming Languages
- **Published:** November 2, 2026
- **Apply:** https://www.careerbuilder.com/job-details/staff-backend-engineer-data-platform-elizabeth-nj--0addef7d-e340-4c95-b81e-0780f10b6997

## About the Role

On Call, Database Architecture, Problem Solving Skills, Application Programming Interface (API), Diving, Performance Tuning/Optimization, Call Monitoring, Scala Programming Language, Go Programming Language (Golang), Diversity, * 6-15 Years of Non-Internship Experience- Staff-level backend engineer; internships, co-ops, and student roles don't count toward this.

 * A Designer, Not Just an Implementer- Real system or workflow design ownership, not just "built X, shipped Y" without design-level involvement.
 * Real Production Ownership- Has run services in production, including on-call and monitoring responsibility.
 * Staff-Level Problem Solver- Can take a large, ambiguous problem, question whether it's the right one to solve at all, and scope a sensible first chunk instead of diving straight in.
 * Comfortable Building the Foundation- Not chasing scale for its own sake; ready to do foundational reliability and robustness work first.
 * Python and SQL baseline expected; TypeScript, Go, or Scala experience is a plus, not a requirement.
 * NYC/NJ based.

Ways to Stand Out:

 * Mentorship Mindset- Experience leveling up a team, valuable given how junior Osmo's engineering team is today.
 * Full-Stack Exposure- React/TypeScript experience, even though this isn't a full-stack role.
 * Broader Systems Experience- Go or Scala exposure, as a signal of real distributed-systems depth.

## Description

Osmo's engineering team is currently junior, and we're looking for the senior backend voice to help it grow up. This is a backend-forward seat with a data component on the side, not a database architecture role: you'll own systems up through the API layer, bringing production judgment, on-call experience, and structured problem solving the team doesn't have yet.

You'll have the trust to question whether a big, ambiguous problem is even worth solving, and the autonomy to scope the right first chunk of it rather than diving straight into code. This isn't a scale or performance role at this stage. It's about laying a robust foundation, handling long-running requests and calls to systems that can fail, and building real recovery paths, not just happy-path code.

What You'll Do:

 * Own Backend Systems Through the API Layer- Handle the complexity underneath the API contract, not just define it.
 * Bring Production Judgment- Take on monitoring and on-call responsibility, knowing what should be watched and why.
 * Build for Failure, Not Just the Happy Path- Handle long-running requests and calls to other systems that might fail or crash, with real recovery paths.
 * Lay the Foundation for Scale Later- Focus on robustness and foundational reliability now, not premature scale or performance optimization.
 * Work With Data the Way a Backend Engineer Does- User-oriented data work, not database architecture.
 * Be the Senior Backend Voice- Bring structured problem solving and production experience to a team that doesn't have it yet.