The opportunity
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.
What you'll do
A seasoned Python engineer. Python is our backbone and it matters in this: role more than on other teams at Close. Architectural patterns don't port cleanly between languages, and you'll be setting the patterns. Go, Rust, or TypeScript alongside it is welcome.
Drawn to meta-problems. This team doesn't ship features to customers; it changes how features get built.
AI-native in production. You've shipped meaningful LLM-backed or agentic work: to real users. For a team building AI tooling that other engineers depend on, this is foundational to the role.
Working with AI in your day-to-day. You use coding agents in your own: workflow and have a real POV on where they help and where they get in the way. On this team, your POV becomes the product. We fund best-in-class developer tools and treat experimentation as part of the work.
Fluent in observability and production practice. Telemetry, metrics, tracing,: alerting, Sentry ownership, what production-ready actually means. You've been the person who made a system legible when it broke.
Opinionated about API design. You've shipped internet-facing APIs and you: think about who's on the other end — apps, agents, humans reading docs — and what each needs.
What they're looking for
- Battle-tested. You've debugged incidents where latency budgets didn't hold,: owned a system everyone else relied on, or carried a pager for something with real customer impact.
- A builder first. You'd rather get a rough v1 in front of five engineers than: spend three weeks on abstractions.
- Energized by internal customers. Your users are a Slack DM away. You'll talk: to them directly instead of through a PM, and you'll use most of what you build yourself.
- Expand DevDawg and Spice. Cloud development environments for our full stack,: paired with automated review and root-cause tooling that can approve real pull requests. Making that safe enough to cover more of our review surface is one of the team's biggest projects.
