Senior Backend Engineer - Backend Platform (USA Only, 100% Remote)
Close · USA
About this role
## Senior Backend Engineer — Backend Platform (USA Only, 100% Remote) ### About Close Since 2013, Close has been building CRM software that gets out of your way and helps teams sell more, faster. Close is bootstrapped and profitable—so we answer to our customers and play by our rules. We’re proud of our 120-person, 100% remote team. Close is also building AI into every part of the product—so the busywork is handled by the system, not your team. ### Our Backend & Infrastructure (high level) - **Backend:** Python **Flask** web apps + **TaskTiger** for asynchronous task processing - **Data stores:** MongoDB, PostgreSQL, Elasticsearch, Redis - **Infrastructure:** AWS (EKS, MSK, RDS, ElastiCache) + EC2 - **Delivery:** CI/CD builds Docker images, runs automated tests, deploys to Kubernetes - **Automation:** Terraform, Ansible, and other AWS tooling - **API:** Well-documented public API consumed by the front-end and many integrations ### About the Role **Backend Platforms** owns the foundation underneath Close—building for other engineers. When product teams add new API endpoints, much of the work is “paved road” engineering: authentication, permissions, rate limiting, consistent endpoint shapes, telemetry, eventing, database migrations, authorization, and local development. This team also builds an **AI development platform**: - **DevDawg:** cloud-based development environments preconfigured for the full stack and engineering practices - **Spice:** an extension layer on top of a coding agent that runs internal review workflows and root-cause analysis (including approving mergeable PRs for simpler changes) This is a **new team**—you’d be one of the first hires, with unusual influence over what the team owns and how it operates. > Note: Close may move engineers between teams as the work shifts. You’ll likely work across multiple projects over time. ### What You’ll Do - **Expand DevDawg and Spice** to safely cover more of the review surface (including automated review + root-cause tooling) - **Build paved roads for the API layer** (REST blueprints, GraphQL schema, OpenAPI, realtime, auth + permission plumbing) - **Modernize the backend framework layer** (web + async compute frameworks, performance, migration paths like **Flask → FastAPI**) - **Own how we see production** (observability, metrics, alerting, readiness bar) - **Ship shared backend services and primitives** (eventing patterns, event log, migration guardrails, auditability, internal admin framework) - **Set guardrails for coding agents** (static analysis, linting, hooks, test harnesses to keep agent-written code safe at volume) - **Partner across the org**: infrastructure owns the substrate; you own the application layer on top ### You Are - A **seasoned Python engineer** (Python patterns matter here more than on other teams) - Drawn to **meta-problems** (you’re building how features get built, not just shipping features) - **AI-native in production** (you’ve shipped meaningful LLM-backed or agentic work to real users) - Fluent in **observability and production practice** (telemetry, metrics, tracing, alerting, Sentry ownership) - Opinionated about **API design** (internet-facing APIs; you think about the consumer—apps, agents, humans) - **Battle-tested** (debugged incidents, owned systems others rely on, carried pager responsibility) - A **builder first** (you prefer rough v1s over over-abstracting) - Energized by **internal customers** (Slack DM away; you’ll talk directly
Listing freshness
CronJobs last confirmed this listing 2h ago. If its source stops confirming the opening for seven days, this page is removed from active inventory.