Snorkel AI
Software Engineer — Product
About this role
Snorkel AI is seeking Product Engineers to build end-to-end features for their AI data platform, working across React/TypeScript frontends and supporting backend services. You'll own product features from design through production, collaborating with cross-functional teams to make complex workflows intuitive for enterprise users.
What you'll do
- Build and ship full-stack product features with ownership from design through production
- Design and implement APIs and services to support frontend requirements
- Collaborate with product, design, and engineering teams on technical solutions
- Contribute to architecture decisions emphasizing scalability and maintainability
- Drive accessibility, responsiveness, and cross-browser compatibility standards
- Troubleshoot and resolve production performance issues across the stack
What they're looking for
- React and TypeScript
- HTML5, CSS3, and modern CSS frameworks (Tailwind)
- State management libraries (Redux, React Context API)
- RESTful API design and consumption
- Backend fluency (Node.js, Python, or similar)
- Accessibility standards (WCAG) and responsive design
- Full-stack development and system architecture
- Cross-functional communication and collaboration
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Snorkel AI
Snorkel AI builds data and AI platforms that transform enterprise data into AI-ready solutions and enable organizations to develop machine learning workflows at scale. The company is hiring software engineers, infrastructure specialists, and applied AI professionals to strengthen its testing and core services infrastructure, deploy customer-facing AI solutions, and advance its data pipeline and ML tooling capabilities.
- Website
- snorkel.ai
Likely interview questions
- Walk us through a complex product feature you've shipped end-to-end — what were the key technical decisions?
- Describe your experience working with state management in React; what patterns do you prefer and why?