# Senior Backend Engineer - Backend Platform (USA Only, 100% Remote) at Close

- Company: Close
- What the company does: Close is the CRM with a built-in AI teammate that works with your team to call leads, qualify prospects, book meetings, and keep your CRM up to date automatically, so you can focus on selling. Backed by Y Combinator.
- Company website: https://close.com
- Type: Startups
- Level: Senior
- Location: USA - Remote
- Work setup: Remote
- Pay: $140K to $210K base salary per year (USD)
- Posted: 2026-09-01
- Apply by: 2026-10-16
- Apply: https://jobs.ashbyhq.com/close/5bf4629b-d2ee-4129-980f-e31b96185c9c
- Page: https://www.1752.vc/careers/jobs/close-senior-backend-engineer-backend-platform-usa-only-100-remote/

## About the role

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.

## What they're looking for

- 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
- 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
- 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

Tags: Engineering