Member of Technical Staff

Role Description

We are looking for a Full-Stack Product Engineer to join our team at Obvious. In this role, you will:

• Ship at least 3 PRs on your first day
• Drive full-stack feature development from conception to deployment, owning key product initiatives end-to-end
• Collaborate on the design and implementation of user-facing features that improve the experience
• Build robust, performant web applications using modern frontend and backend technologies
• Identify opportunities for optimization and enhancement in existing systems
• Contribute to the architectural decisions that shape the product
• Set the industry standard for the UX of agent products
• Build AI/LLM integrations as a core part of the product, not a bolt-on—agent-facing UX, not just prompting

Qualifications

• Genuine full-stack range, frontend-leaning: strong TypeScript/React paired with real API and backend chops—not a single narrow lane
• AI/LLM integration experience you can point to, not just talk about—production work building agent-facing features, ideally with the eval harnesses or quality feedback loops behind them
• An engineering bar we hold at staff level regardless of how you're titled—we'll ask about design-system fluency and client-server/UI performance judgment, not just ship velocity
• A track record of end-to-end ownership—driving ambiguous problems from first idea to shipped, not executing a spec handed down
• Strong problem-solving skills and attention to detail
• Excellent communication skills and the ability to work cross-functionally
• Willingness to work hard, move fast, and grow quickly in a rapidly changing environment
• A humble, team-first attitude and a desire to do whatever it takes to make the team succeed

Requirements

• Background in coding agents or multi-agent systems (nice to have)
• Informed opinions on agent orchestration (nice to have)
• Contributions to open-source projects or developer tools (nice to have)
• Previous experience at a high-growth startup (nice to have)

This role may not be a fit if:

• You need fully-specced requirements to operate—at our size, you'll define scope as often as you're handed it
• You see frontend and backend as separate lanes rather than one job
• You can't handle startup pace