Product Builder - Conversational AI

Role PurposeThe Product Builder is a hybrid role within Omilia’s Product organisation, combining product ownership with direct, hands-on delivery. The role sits inside the Developer Experience pod and is responsible for taking ideas from concept through to working software on the Omilia Cloud Platform (OCP), using AI-native tooling to accelerate every step of that journey. As Omilia transitions its product teams toward autonomous, pod-based delivery, the Product Builder is expected to operate with a high degree of independence — contributing directly to the codebase where needed, eliminating friction in the builder journey, and ensuring that OCP remains the platform where production-grade conversational AI is built faster and with greater confidence. The role is not primarily client-facing but requires the ability to represent the product credibly to enterprise customers and internal stakeholders when escalations or product reviews demand it.

Accountabilities• Own assigned OCP product areas end-to-end — from problem definition and prototyping through to production delivery. • Drive platform adoption by shipping working, validated solutions rather than specifications alone. • Deliver measurable reduction in friction across the OCP builder journey, using usage data and field feedback as the primary inputs. • Operate autonomously within the Developer Experience pod, minimising delivery dependencies on broader engineering cycles for tasks within scope. • Act as a credible product voice in cross-functional reviews, customer escalations, and internal stakeholder conversations when required. • Align with Product leadership on roadmap priorities and contribute to the iterative shaping of the Developer Experience pod’s direction.

Key Responsibilities• Define user stories, acceptance criteria, and success metrics for assigned Developer Experience areas within OCP. • Ship features autonomously — from idea generation through to production — using AI-coding tools to accelerate exploration and internal tooling. • Validate hypotheses with working software before committing full engineering cycles; favour fast, evidence-based iteration over extensive upfront specification. • Identify and eliminate friction points in the OCP builder journey by synthesising usage data, field feedback, and direct observation of how Omilia teams, partners, and customer configurators interact with the platform. • Prioritise backlog items based on builder impact, platform scalability, and delivery feasibility; manage the trade-offs between speed and quality with sound judgement. • Collaborate actively with engineering squads on features that exceed individual scope; provide clear product direction and unblock delivery without micromanaging execution. • Contribute to the evolution of agentic application design patterns on OCP as the platform’s AI capabilities expand. • Represent the product in customer-facing contexts as needed — including escalation calls and product reviews — articulating decisions and roadmap direction with clarity. • Maintain documentation standards in Confluence and Jira sufficient for engineering partners and the wider Product team to build on your work.