Close runs on Python: Flask web apps, TaskTiger, billions of MongoDB documents, a public REST API that customers and external agents both build on. Four product teams ship features on top of that every week. Backend Platforms owns the foundation underneath it all.
As an Engineer on our Backend Platforms team, you’re building for other engineers. When a product team adds a new API endpoint, most of what they write isn’t their feature — it’s wiring: authentication, permissions, rate limiting, the shape the endpoint has to take so it looks like every other endpoint when you squint. Multiply that across telemetry, eventing, database migrations, authorization, and local development, and you get the problem this team exists to solve: make the paved road faster to walk than the trail.
The other half of the team’s mandate is the AI development platform. We’ve built DevDawg, cloud-based development environments preconfigured for our entire application stack and our engineering practices, and Spice, our extension layer on top of a coding agent that runs internal review workflows and root cause analysis. Spice is hooked into GitHub and can already approve mergeable pull requests on its own for simple changes. This team is responsible for expanding what it can safely handle.
This is a new team. You would be one of the first hires, and you’d have unusual influence over what the team owns and how it operates.
One thing to know: we do move people between teams as the work shifts. Most engineers here end up on more than one team over their time at Close — this team is where you’d start, but over time you’ll likely have the opportunity to work on many different projects.
This role is open at the Senior and Staff levels. You don’t need to pick one when you apply: we’ll calibrate together during the process.