Skills this job asks for
CRMPythonMongoDBPostgreSQLRedisAWSCI/CDDockerKubernetesJavaScriptTerraformREST APIs
Add your CV (free) to see which of these your CV is missing.
Where you can work from
United States only
Based on the listing's location: Remote (USA).
The company's headquarters is not the same as where you may work from. Visa sponsorship only matters if you would relocate; see below.
Visa sponsorship, if you would relocate
Sponsorship verdict
No sponsorship evidence yet
No government record and no wording either way. Not a refusal: ask the recruiter.
-
?
No government sponsor record hereThis employer posted directly and does not match a government sponsor register.
-
?
The posting doesn’t mention sponsorshipSilence isn’t a refusal — ask the recruiter before investing much time.
-
?
No salary bar for this routeH-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area.
-
✓
Confirmed live todayWhen a source last listed this job as open.
Details and sources
- No salary bar for this route
- H-1B has no fixed salary bar: the employer must pay at least the prevailing wage for the role and area. Cap-subject employers enter a lottery weighted by wage level. Source: https://www.federalregister.gov/documents/2025/12/29/2025-23853/weighted-selection-process-for-registrants-and-petitioners-seeking-to-file-cap-subject-h-1b, rules effective 2026-02-27.
US H-1B: cap-subject employers enter a lottery weighted by wage level — Level I gets 1 entry, Level IV gets 4 (DHS projected selection odds ≈15% at Level I to ≈61% at Level IV). Universities and non-profit research employers are cap-exempt. The $100,000 fee for new petitions from abroad is currently blocked by a court order (appeal pending).
A verdict summarises public evidence. It is not legal advice and never a guarantee: the employer and the immigration authority decide. Sign in to factor in where you can already work.
Before you apply
Sponsorship unknown
No register record and no sponsorship wording in the posting. Worth asking the employer before investing significant time.
These come from the posting’s own wording. Read the original listing to confirm. See better-fit alternatives →
About the role
About Us
Since 2013, we’ve been building a CRM that gets out of your way and helps your team sell more, faster. Now we’re building AI into every part of it, so Close does the busywork and your team does the selling. No manual data entry, no 10-click workflows. Just communication-first, AI-powered sales software designed to help you succeed and scale.
We're bootstrapped and profitable which means we answer to our customers and play by our rules. We're proud of our 120-person, 100% remote team, focused on building Close so that no small, scaling business fails because it can't figure out sales.
Our Stack
Our backend tech stack consists primarily of Python Flask web apps with our TaskTiger scheduler handling many of the backend asynchronous task processing chores. Our data stores include MongoDB, PostgreSQL, Elasticsearch, and Redis. The underlying infrastructure runs on AWS using a combination of managed services like EKS, MSK, RDS and ElastiCache and non-managed services running on EC2 instances. We have CI/CD pipelines that build Docker images, run automated tests and deploy to Kubernetes clusters. We also use these images in our local development environment allowing coding locally against all of our services. We have a well-documented public API that is consumed by our front-end JavaScript app as well as numerous integrations. Our infrastructure is heavily automated using Terraform, Ansible and other AWS tools.
We love open sourcing our code and ideas on our GitHub and on The Making of Close , our behind-the-scenes Product & Engineering blog. Check out our open source projects like SocketShark , TaskTiger , LimitLion and ciso8601 .
AI is both how we build and what we ship, and that's reshaped what engineering looks like. This is a transformation we’re embracing and find deeply exciting.
About the Role
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.
You are
•
A seasoned Python engineer. Python is our backbone and it matters in this role more than on other teams at Close. Archi
View original listing ↗