Strategy & Operations, Office CPTO

You will work closely with ai71's Chief Product & Technology Officer. You own strategic initiatives, run the operating rhythm of product and technology, and work with its leads to turn decisions into shipped work. It is a new role for someone with a strong technical foundation, an operator's instincts and an analyst's rigour.

ai71 builds enterprise-grade AI for the organisations that underpin the real economy: governments, banks, and large enterprises. We're rooted in the Middle East and Africa, where the demands on us are at their highest: sovereignty, on-prem, multi-lingual, and real regulatory weight. Those same demands are arriving everywhere, and what holds up here travels. Our work is grounded in a commitment to deploying AI securely, responsibly, and at scale.

We build Ask in squads: a PM, three or four engineers, a TPgM and a designer, each owning a slice of the product end to end. Alongside them, a forward-deployed team works inside the ministries and enterprises we serve. The Office of the CPTO keeps that whole system pointed at the same outcomes.

You work directly with the CPTO, who leads product, engineering and business operations for Ask and previously led product at Deep Mind and Google Brain. Your job is to make the CPTO's priorities land across the organisation.

The remit has three parts:

• initiatives you own end to end
• the cadence the organisation runs on
• and the day-to-day work of the office.

Expect the mix to shift, sometimes week to week. The shape of the org keeps moving as the product does, and part of your job is helping it move well.

The work gets done through preparation, credibility and follow-through, and it is hands-on: you write the memo, build the model and chase the action yourself. This is neither an executive-assistant post nor a strategy-only one.

This is not a role for someone who wants the plan settled first. Ask runs inside air-gapped government networks, for buyers betting real operations on us, in a field that resets every few weeks. Much of the job is working out what is true, then getting the organisation to act on it.

Few seats show you product, engineering, deployments, commercial and the board  see this as a tour that leads into a line role: a squad, a new bet, a forward-deployed team or a market expansion.

• Own two or three CPTO-sponsored initiatives at a time, from problem definition to a dated outcome.
• Turn early ideas into decision-ready proposals: the question, the evidence, the options, the trade-offs and a recommendation.
• Take approved proposals into execution. Set the plan, owners and milestones, then run it until a permanent owner takes over.
• Do your own technical homework. Prototype it, query it, script it, and bring a working artefact to the argument instead of a deck.
• Keep a structured read on the field: what the frontier labs and open-source projects shipped, and what we should build, wrap or adopt as a result.

Typical initiatives: a new market or vertical, a build, wrap or adopt decision on part of the platform, pricing and packaging, the plan for a new squad.

• Run the operating rhythm for product and technology: weekly leadership meeting, monthly business review, quarterly and annual planning.
• Run planning for our cross-squad pushes: what each push delivers for the customer, what each squad contributes, and whether it landed.
• Own agendas, pre-reads and decision records. Every forum ends with decisions, owners and dates, and you track them to closure.
• Keep decisions and their reasoning on shared channels, where the team and the agents we build on top can learn from them.
• Maintain the metrics view the CPTO and leads run the business on: delivery, deployments,…