Product Engineer

Product Engineer I — Voice AI (Customer Impact Track)

About the role

Build and evolve production-grade Voice AI systems used by real customers. You’ll work close to live deployments: identify gaps from usage, design fixes, and ship to production. Priorities are driven by customer outcomes, not quarterly roadmaps. You’ll configure/extend AI-native workflows on our platform and write production-quality code as needed. You’ll work in a small pod with Customer Success + AI PM; you own technical execution end-to-end.

What you’ll do

• Build custom integrations, internal tools, and AI workflows to unblock customer needs
• Design/refine prompts, RAG systems, and LLM-based solutions
• Write high-quality Python/JavaScript with reliability, testing, and maintainability in mind
• Decide whether a solution stays custom, becomes reusable, or should be upstreamed into the core product
• Partner with core engineering to share learnings and reduce future friction

What you will NOT do

• Run customer calls
• Own accounts
• Chase stakeholders
• Do repetitive support

Not Solutions Engineering

No one-off scripts and move on. Every solution is evaluated on leverage:

• Can it be reused?
• Can it become a product primitive?
• Can it remove future manual work?
• Strong solutions often become core platform capabilities, internal tooling, or roadmap items.

How success is measured

Reduced future friction and repeat issues (not “number of customers unblocked”). Same high bar for code quality; real-world problems are messy and time-sensitive.

What we’re looking for

Technical:

• Strong fundamentals (Python/JavaScript preferred; talent > language)
• Comfort with ambiguity and incomplete requirements
• Curiosity about AI/ML in production (experience is a plus)

Mindset:

• Ownership, pragmatism, curiosity, entrepreneurial thinking
• Clear communication of technical tradeoffs in business context
• AI-native exposure (prompts/context engineering/RAG) is a plus

Should you apply?

Yes if you like variety, autonomy, and shipping impactful solutions. Maybe not if you need tight specs, predictability, or large-team structure.

Day-to-day (example)

Mon: pod sync & pick top blocker • Tue: prototype • Wed: harden & decide reuse vs custom • Thu: ship + monitor • Fri: share learnings

Logistics

Compensation: Competitive | Joining: ASAP