Senior Frontend Engineer – Growth (USA Only, 100% Remote)

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. ABOUT THE ROLE The Growth team owns the surfaces that turn someone who just signed up into a paying customer who sticks around — onboarding, activation, billing and checkout. The operating mode is simple: find the fastest path to learning, ship it, then standardize and clean up. The Growth team ships in weeks what other teams might take months to do. Two of our exciting projects right now: - Agent-forward experience. We're exploring how agents and AI can make the experience better for our customers and demonstrate the value of Close faster. Our focus is helping users get real value from the product, not just automating on their behalf.

• Creating data from unstructured sources. We're building ways to turn the information customers already have, like their inbox, into a working CRM, so they can skip the manual data entry and see value from Close faster. One thing to know up front: we do move people between teams as the work shifts.

• Fluent in experimentation.

• Experienced with B2B experiment structure. A strong bonus: you've worked in Amplitude on the implementation side, not just the technical configuration side.
• Building AI-powered interfaces.

• Working with AI daily. You use AI tools in your own workflow to ship faster, write tighter code, and reason about unfamiliar parts of the codebase.

• A builder first. You'd rather get the first iteration of a feature in front of fifty customers than spend three weeks fretting over a perfect PR. You ship — and you're comfortable standardizing and cleaning up after the learning lands.

• Turn an inbox into a CRM.

• Design experiments, not just features. Decide what to instrument, define the funnel, and structure metrics so a B2B reality (org-level conversion, user-level behavior) still yields clean answers.

• Work across the whole app. Growth doesn't stay in its lane — onboarding, activation, billing, import, and whatever surface the next experiment needs. The Growth team experiments touch every aspect of the product.
• Move at learning speed. Fastest path to insight first, then standardize and clean up.

• Have ownership and autonomy. The team is relatively new. How Growth frontend engineering works at Close is, in part, yours to shape. Tech you'll touch: TypeScript, React, Vite, Amplitude, CSS Modules, Storybook, Playwright, WebSockets — plus the agent stack behind Chloe.

Compensation

• 80% Work Option: Work with your manager to choose between a standard 5-day week or a 4-day week at 80% pay - Parental Leave: Paid leave for primary and secondary caregivers - Sabbatical: A 1-month paid sabbatical every 5 years with the team - Healthcare (US residents): Two medical plans with Close covering 99% of your premium, plus Dental, Vision, HSA, FSA, and company-paid Long-Term Disability - 401k (US residents): We match your contributions up to 6%, vested immediately OUR VALUES Build a house you want to live in - Examine long-term thinking and action No BS - Practice transparency and honesty, especially when it’s hard Invest in each other - Build successful relationships with your coworkers and customers Discipline equals freedom - Keep your word to yourself and others Strive for greatness - Constantly challenge yourself and others LEARN MORE Listen to our CEO and Founder, Steli Efti, tell the story of Close’s journey in the $0-30m Blueprint https://www.close.com/blueprint.

• Showcase a portfolio that includes live React projects with clear experiment tracking or analytics hooks.
• Highlight any LLM‑driven UI components you built; include screenshots or a short video demo.
• Mention specific AI coding assistants you use daily and how they improve your workflow.
• Prepare to discuss a recent experiment you shipped: the hypothesis, metrics captured, and outcomes.
• Be ready to write a small component on the spot that handles streamed data and displays loading/error states.
• Research Close’s open‑source repos beforehand; referencing them in interview answers signals genuine interest.
• During salary discussions, emphasize the equity component and remote‑work flexibility as part of the total compensation.