Location: Remote
We are looking for a Product Owner to join one of the teams building these products.
You should know what the next while looks like, because it is unusual and it will shape your first year. We are in the middle of moving an established email product onto our own platform — a large, careful migration of real customers with years of mail, contacts, calendars and filter rules behind them. It is deliberately not a feature-for-feature copy of what came before: someone has to decide what must exist before a customer moves, what is genuinely safe to leave behind, and how to explain the difference to people who did not ask for any of this to change.
That work sits alongside the ordinary business of running a live product — mobile apps, deliverability, the steady stream of things customers ask for.
If migrations sound like maintenance work to you, this probably isn’t the right role. If you find it interesting that the hard part is judgement rather than construction, it might be a very good one.
Your expertise:
3+ years in product ownership or business analysis in a technical product environment
Comfortable in Agile delivery (Kanban) working closely with engineers and QA
Experience owning something customer-facing where reliability mattered more than novelty
Experience working across departments — support, operations, marketing — rather than only inside one team
Able to write for two audiences: a team that needs precision, and customers who need reassurance
Proactive — you chase alignment rather than wait for it
Curious, analytical, structured
Strong English, written and spoken
How you work:
You gather requirements from several sources that disagree with each other, and turn them into something a team can build without coming back to you three times
Your backlog items carry the edge cases, the error states and the acceptance criteria, not only the happy path
You can document a user journey or a system flow clearly enough that someone else can act on it
You’re comfortable with logs, error tracking and ticketing systems as everyday tools
You can distinguish between what customers ask for and what they actually need, without dismissing either
Working with AI (required):
We work AI-first, and this is a real requirement rather than a line we felt obliged to include
We expect AI-assisted workflows to be your default way of working: for research, for drafting, for understanding an existing implementation before you walk into refinement, and for checking your requirements against how the system actually behaves before tickets reach the team. The point isn’t personal speed — it’s that the team downstream gets clearer inputs and spends refinement making decisions instead of explaining code
You stay at the quality gate. AI produces a draft; you remain accountable for what you publish
We’re not looking for familiarity with our particular setup — you’ll learn that here. We’re looking for someone who already has a practice of their own and can talk us through one honest example: something you handed to an AI, what you deliberately kept, what went wrong the first time, and what actually changed as a result
Will definitely be a plus:
Experience with a platform migration or product consolidation — moving customers between systems, deciding feature parity, planning a staged rollout, handling the fallout when something doesn’t transfer cleanly. This is genuinely valuable here and we would like to hear about it
Exposure to email technologies — IMAP / POP3 / SMTP, deliverability, DNS records, anti-spam and anti-abuse
Experience with mobile apps alongside web, and an understanding of how release cycles differ
A background in QA, technical support or incident handling
Familiarity with monitoring and observability tooling
What’s in it for you?
Opportunity to work in a global product company with millions of active users
Build meaningful things in the privacy, security and communication space
Own work with vis
