The opportunity
We’re hiring a Software Engineer to build the tools and AI Systems that our Support team runs on. Support is one of the things our customers love most about Close, and as ticket volume grows and AI rewrites what good support looks like, we’re adding another embedded engineer…
What you'll do
A Software Engineer who builds for the person sitting next to you. You have: 3+ years of Software Engineering experience and can write clean, production-quality code. You’re drawn to problems where you can watch a Support Rep get faster and more effective within a few days of shipping. You're excited by the idea of a tight, collaborative feedback loop.
Backed by a degree or experiences in the sciences. You have a degree or: rigorous experience in Computer Science, Mathematics, Physics, Electrical or Mechanical Engineering. This shows up in how you reason through systems and approach problems.
Technically deep. You're fluent in Python, Rust, Go, or: Typescript/Javascript. You have built information retrieval systems using semantic search / RAG.
A systems thinker. When you see a manual process, you have an unignorable: itch to fix it. You think about upstream and downstream consequences before you commit.
AI-fluent, not AI-dependent. You use Claude, Codex, Pi, or whatever makes you: faster. You also understand what the code is doing, can debug it when it breaks, and know when to set the tools down and think from first principles.
A clear, async communicator. You write well. Your technical specs are: readable, your PRs are well-documented, and your Slack messages don't create more questions than they answer. You thrive in a fully remote, async-first environment.
What they're looking for
- Comfortable with autonomy. You scope your own work, manage your own: priorities, and don't need heavy oversight to ship. You're pragmatic over theoretical and have a strong bias toward action.
- Located in US time zones. (ET, CT, MT, or PT)
- Build internal tools that scale Support. Design and ship the systems that: Support Engineers and Support Reps rely on daily — AI drafting tools, autonomous reply systems, workflow automation, reporting dashboards, and anything else that removes friction from the support operation.
- Own projects end to end. You're the engineer who takes "this part of the: workflow is painful" to "this part of the workflow doesn't exist anymore." No PM intermediary, no thrown-over-the-wall requirements. You work closely with the Support team to understand what to build, then you build it.
