Atlassian closed out its financial year on August 6 with revenue up 28%, its MCP server past a million monthly active users, and no CTO anywhere in the building. Five months ago that last part read like cost-cutting theatre. It doesn’t any more.

Rewind to March. Atlassian cut 1,600 roles, about 10% of its workforce and nearly 500 of them in Australia, and retired the CTO title outright when Rajeev Rajan stepped down. Two people took the job instead. Taroon Mandhana became CTO of Teamwork, owning AI product engineering and shipping velocity. Vikram Rao became CTO of Enterprise and Chief Trust Officer, owning governance, security, and compliance. Mike Cannon-Brookes said it would be “disingenuous to pretend AI doesn’t change the mix of skills we need or the number of roles required in certain areas.”

At the time you could read the split as a layoff dressed up as org design. The first full quarter under the new structure argues otherwise. Both halves shipped: agentic development tools in Jira on one side, enterprise AI governance features and HIPAA-compliant Rovo on the other, in the same quarter, from the same company. That is what two technical leaders running two different races looks like.

The two halves stopped overlapping

A decade ago velocity and trust were the same discipline at different speeds. Good engineering leadership covered both. AI pulled them apart.

The velocity half now moves at a pace no governance function can match. Atlassian’s MCP server usage more than doubled in a single quarter. If your top technical leader spends their week on audit posture, someone else’s product just lapped yours.

The governance half, meanwhile, acquired a statute book. The EU AI Act’s Article 50 transparency obligations began applying on 2 August, while the high-risk deadlines were pushed to December 2027 and August 2028 in June’s Omnibus. The deadlines have moved twice this year. Tracking which obligations bind your product, in which market, on which date, is now a standing job with legal exposure attached.

These two jobs share a reporting line and almost nothing else. One rewards product taste and comfort with shipping half-finished things. The other rewards paranoia, paperwork, and the ability to say no to the first person. The Humai analysis of the Atlassian move put it flatly: no single person is likely to do both jobs well simultaneously.

Atlassian did this loudly, but the unbundling is everywhere. IBM’s Institute for Business Value found 76% of surveyed organisations now have a chief AI officer, up from 26% a year earlier. Companies keep concluding that the top technical seat, as designed, holds too many jobs.

You are hiring a unicorn and calling it a CTO

Now look at an early-stage CTO or VP Engineering spec. Set the technical vision. Ship fast with a small team. Own security and compliance. Get us SOC 2. Define our AI strategy, and its governance. That spec describes both of Atlassian’s CTOs, compressed into one salary that a seed-stage company can afford.

You will not find that person, and the danger is hiring someone who claims to be them. What you get in practice is someone brilliant at one half quietly deferring the other, and you find out which half they deferred when a customer’s security review stalls a contract, or when a competitor ships three quarters of your roadmap while you were writing policies.

The fix costs nothing but honesty. Decide which half the next eighteen months actually requires. Pre-product-market-fit and selling to startups, it’s velocity, almost every time. Selling AI into banks, health, or government, the trust half may literally be the product, and it deserves the seat. Write the spec for the half you chose.

Then name, in writing, who owns the other half. A fractional advisor, a board member, a founder, an external auditor on retainer. Any of those can work. What fails reliably is the unnamed half, because an unnamed half is owned by nobody until the day it’s owned by an incident.

If you’re already in the seat

Most people holding a CTO title got there through the velocity half, and the governance workload grew underneath them without anyone deciding it should. Naming that is cheap. Rao’s new title pairs CTO with Chief Trust Officer; Atlassian promoted the trust work rather than spinning it off, and a board that has read the same news will take the point. The real career risk is claiming both halves and delivering one.

I don’t think Atlassian’s answer transfers directly to a fifteen-person company, and I’m genuinely unsure where the line sits as you scale from there. My working answer is the one above: pick your half honestly and name the owner of the rest. If you’re writing that spec right now, or sitting in a seat that quietly became two jobs, compare notes with us.

Sources