Job Opportunities API

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 frontend is a single-page TypeScript web app built in React. We bundle with Vite and target modern browsers only. We test with Vitest, React Testing Library, Playwright, and Chromatic for visual regression. Our UI updates in near real-time using WebSockets and WebRTC, is styled via CSS modules, and is performance-tuned with route-based code splitting and skeleton UI. We've built our own design system, documented in an extensive Storybook. We sweat the UI/UX details and work collaboratively with Product throughout the design process - from lo-fi wireframes through Figma and into code. Our frontend is built on top of our REST API and GraphQL endpoints, backed by a Python/Flask/FastAPI, MongoDB, Postgres and Elasticsearch stack running on AWS. We love open sourcing our code and ideas on our GitHub https://github.com/closeio and on The Making of Close https://making.close.com/, our behind-the-scenes Product & Engineering blog. Check our projects such as react-custom-scroller https://making.close.com/posts/introducting-react-custom-scroller-component, use-infinite-scroll https://making.close.com/posts/introducting-use-infinite-scroll-react-hook, use-abortable-effect https://making.close.com/posts/introducting-use-abortable-effect-react-hook, and smart-tooltip-delay https://making.close.com/posts/introducing-smart-tooltip-delay-library or insights from our day-to-day work like Under the Hood: Developing Close's AI-Powered Call Assistant https://making.close.com/posts/developing-the-call-assistant, Cutting our Lead page LCP by half https://making.close.com/posts/cutting-our-lead-page-lcp-by-half, and Highlights From a Complex Downshift.js Refactor https://making.close.com/posts/highlights-from-a-complex-downshift-js-refactor/. 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. OUR TEAMS When you apply, you’ll have an opportunity to highlight the team that appeals to you the most. We’ll do our best to honor this preference, but we'll also be evaluating skillset fit and the needs of the business. One thing to know up front: 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’ll start, but over time you’ll likely have the opportunity to work on many different projects. The work splits roughly like this. Pick the team that excites you most: - Agents. Build the UI that puts AI in the hands of Close customers. This means the creation and configuration experiences for Close's growing family of agents, the conversational interface through which users ask questions and get answers in plain language, and the observability surfaces that let customers see what their agents are doing and why. The design challenges here are genuinely new: you'll be figuring out how AI capabilities should surface in the product. - Communications. Own the UI for one of the most real-time, high-stakes surfaces in Close: calls. You'll build in-call experiences that run on WebRTC and WebSockets, live transcript and coaching views where latency visibly matters, power dialing flows built for reps making hundreds of calls a week, and the email, SMS, and scheduling surfaces that keep async outreach moving. - CRM. Build the core surf