Staff Product Engineer

<h2><strong>About Parloa</strong></h2> <p>Parloa’s mission is to make every customer conversation feel effortless for both customers and the companies serving them. As agentic AI accelerates, Parloans are shaping the foundation of a new era in customer experience, one where customer support is no longer transactions, but meaningful exchanges. It is not just a vision; Parloa has powered over ONE BILLION interactions between global enterprise brands and their customers, with companies like <a href=&quot;http://booking.com&quot;>Booking.com</a>, HealthEquity, Allianz, SAP, BarmeniaGothaer, and TUI already deploying Parloa at scale.</p> <h2><strong>About the role:</strong></h2> <p>As a <strong>Staff Product Engineer</strong>, you will work directly inside our most strategic enterprise customers. You will build the software that makes their AI agents work in production, and be measured by the difference it makes for the customer.</p> <p>Our agents are built by business users in Parloa’s platform, AMP. AMP already comes with a broad library of tools and integrations. Your job is the part AMP does not cover yet for a given customer: the last connection into their systems, or a capability the product does not have. Our customers are large enterprises in financial services, telecom, insurance, travel and retail. For them, a working prototype is where an engagement starts, not where it ends.</p> <p>The work comes in two forms. Some engagements run for years. You stay with the account, deepen its integrations and help it grow into new use cases. Others are short experiments. You test a new idea with a real customer and decide quickly whether it is worth building. At Staff level, you take on the hardest cases of both: accounts where a pilot-grade solution would fail in production, and capabilities nobody at Parloa has built before. Staff means harder problems and more ambiguity, not less hands-on work.</p> <p>On many accounts, you work alongside a Deployment Strategist. Think of the two of you as the account’s leadership team. The Deployment Strategist acts as its CPO and defines what success looks like. You act as its CTO and own the architecture and the build. On accounts without a Deployment Strategist, you own the engineering yourself.</p> <h2><strong>Areas of ownership:</strong></h2> <ul> <li><strong>Lead the hardest engagements.</strong> Run complex programmes with several workstreams. Make the architecture decisions that span Parloa’s platform and several parts of the customer’s organization.</li> <li><strong>Build what AMP does not cover yet.</strong> Systems of record, telephony and contact-center integrations, state management, data readiness, multi-agent orchestration and retrieval. When the answer is unclear, build a prototype quickly and decide whether it is worth pursuing before Parloa invests a full quarter in it.</li> <li><strong>Own production quality and security.</strong> Evals, production readiness, observability and incident playbooks for enterprise-scale traffic. Meet the data handling standards a regulated customer expects, including PII, access control and audit trails. Debug live issues, whether they are technical or caused by model behaviour.</li> <li><strong>Grow the account, and share what belongs in the product.</strong> Drive the second use case, the second business unit, the renewal. Set the delivery standard for other engineers on complex accounts. When something you build would help every customer, flag it. That is how Parloa decides what goes into the core product.</li> <li><strong>Mentor other Product Engineers</strong>, and take part in interviewing and hiring.</li> <li><strong>Use AI well, and set the standard for it.</strong> Decide how AI-assisted work is validated before it reaches a customer’s production traffic.</li> <li><strong>Represent Parloa with senior technical stakeholders.</strong> Work directly with the customer’s principal engineers, architects and security leaders. Be the engineer commercial teams bring in when a prospect asks how the solution would work for them.</li> </ul> <h2><strong>What this role is not:</strong></h2> <ul> <li><strong>Not running the Parloa platform itself.</strong> That is a separate engineering role. The platform is your foundation, and you build what a specific customer needs on top of it.</li> <li><strong>Not agent configuration.</strong> Business users design and configure agents in AMP. You build the integrations and capabilities those agents need.</li> <li><strong>Not a people-management role.</strong> You are an individual contributor and write and review code every week.</li> </ul> <h2><strong>OUR TECH STACK:</strong></h2> <p>Go, TypeScript, Node.js, Python, FastAPI, frontier LLMs, MCP, Azure, Kubernetes, Docker, Terraform, MongoDB, Redis, Kafka/NATS</p> <p>You will not use all of these, and most engagements add something new.</p> <h2><strong>Who you are:</strong></h2> <ul> <li><strong>8+ years of professional software development</strong>, delivering production systems end to end. Fluent in TypeScript or Python, or able to get there quickly.</li> <li><strong>5+ years leading the design and architecture of large-scale production systems</strong> in customer-facing or enterprise environments, with a focus on reliability, scale and failure modes.</li> <li><strong>Experience leading agentic, spec-driven development in production.</strong> You know when a coding agent’s output is wrong and what checks it needs before it ships.</li> <li><strong>A track record in long-term accounts or fast experiments.</strong> You have owned a strategic enterprise relationship over several years, through an expansion, a renewal or a leadership change. Or you have tested new ideas at the frontier and decided quickly whether they were worth building.</li> <li><strong>Experience as a mentor or tech lead</strong>, helping engineers become independent.</li> <li><strong>Comfortable with ambiguity and with customers.</strong> You work well in co…