Omni - Frontend Engineer
Requirements
• Working confidence in Java or Python • Experience building SaaS applications that run in the cloud • JavaScript / TypeScript • Location • Location • This role is based in San Francisco, or remote for candidates based near one of Omni's engineering hubs (Philadelphia, Boulder/Denver, Santa Cruz, or Seattle); final-round interviews are conducted in person.
Responsibilities
• Own features across Omni's frontend end-to-end: technical decisions, implementation, and delivery • Partner directly with customers and the product team to scope integration requirements • Design and build the APIs, SDKs, and front-end surfaces that let companies embed Omni in their own products • Move quickly and ship iteratively, refining based on customer feedback • Use AI coding tools (e.g., Claude Code) to maximize velocity and focus on the highest-leverage technical work • Collaborate with engineers across the stack as needed, without requiring day-to-day oversight • Represent Embed customer needs in broader product and engineering planning • 5+ years of software engineering experience, including 2+ years operating at a senior level and shipping production software independently • Strong proficiency in JavaScript and TypeScript • Proven track record delivering senior-level projects to customers • Experience with data or business intelligence tools or applications (e.g., SQL, Looker, Tableau, Mode, Amplitude, Google Analytics) • Demonstrated bias to action — comfortable making decisions and shipping with limited oversight • Proficiency with AI coding tools and workflows (e.g., Claude Code, Cursor) • Experience building and maintaining APIs or SDKs consumed by external customers
Benefits
• Base Salary $160K – $250K • Offers Equity • Upload your resume here to autofill key application fields. • Drop your resume here! • Parsing your resume. Autofilling key fields... • or drag and drop here • JavaScript / TypeScript • None of the above • 1 – Occasional: I sometimes use AI chat or autocomplete for snippets, syntax questions, or debugging (e.g., asking ChatGPT why a CSS layout is breaking). • 2 – Regular assistant: AI is part of my daily workflow. I use it to generate components, write tests, refactor code, or explain unfamiliar parts of a codebase, and I review everything it produces. • 3 – Agent-driven: I hand off full tasks to AI coding agents (e.g., Claude Code, Cursor agent mode), such as building a feature across multiple files, turning a design into working UI, or running and fixing tests, then review and ship the result. • 4 – Orchestrator/builder: I run multiple agents in parallel, build custom tooling or workflows for them (e.g., rules files, MCP integrations, design-to-code pipelines), or build AI-powered features into the product itself. • None of the above • Greencard Holder
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT