Apple's Next CEO Rehired a Scheduler. That's the Signal

John Ternus rehired Laura Legros before he has even started as Apple's CEO, and the choice tells you more about how he plans to run the company than any keynote will. Legros is a former vice president of hardware engineering who retired from Apple in 2022. She is not a chip architect or a designer. She ran schedules.

Juli Clover covered the move at MacRumors, citing Bloomberg. I want to talk about why this specific kind of hire is the one most small teams skip, including mine.

---

🔍 What Ternus actually bought back

Strip out the job title and look at what Legros owned, per the reporting:

What she managed	What that means day to day
Product delivery	Something ships on the date it was promised
Development schedules	Who is blocked, by what, and for how long
Cross-team coordination	The camera team and the silicon team agree on one truth

The reporting adds two things worth noting. She will work across different parts of the company rather than own one product line, and she will report directly to Ternus. Bloomberg describes her as one of his most trusted deputies before she retired.

Key takeaway: A new CEO's first hire is a statement about what he thinks is broken. Ternus did not hire a visionary. He hired the person who makes dates real.

Ternus takes over from Tim Cook on 1 September 2026, with Cook moving to executive chairman. So this is a pre-start hire, made during the handover window while Ternus has been shadowing Cook and meeting leaders about product plans.

---

🛠️ The role nobody puts on their org chart

Every Sri Lankan dev team I have worked with has a version of this person, and almost none of them have the title. It is usually the senior engineer who quietly keeps a spreadsheet, or the founder who does it badly at 11pm on a Sunday.

Here is the uncomfortable part. The work is real, it is full-time at scale, and doing it badly is expensive:

• Silent dependencies. Backend thinks the API contract is settled. Frontend is building against a Figma file from three weeks ago.
• Fake dates. Everyone commits to a Friday nobody believes in, so nobody plans around it.
• Integration debt. Two parts work. Together they do not, and you find out in the last week.
• The bus problem. One person holds the whole schedule in their head and takes leave.

Apple ships hardware, where a slipped date means an empty warehouse and a wasted ad buy. Software has softer edges, so the cost hides longer. It does not go away.

If your team has never named an owner for "does this ship on the promised day," the answer is that nobody owns it.

---

🤝 Why rehiring a known quantity beats a better CV

Legros retired four years ago. Ternus could have hired someone younger, cheaper, and currently in the market. He went back for someone he had already worked with. That is my reading of the trade he made:

	Boomerang hire	Strong outside hire
Time to useful	Weeks	Two to three quarters
Knows where the bodies are buried	Yes	No
Trust with the CEO	Already established	Must be earned under pressure
Fresh outside perspective	Limited	High
Risk of importing old bad habits	Real	Low

When your main constraint is time and trust, the left column wins. When your main constraint is stale thinking, the right column wins. Ternus has roughly four weeks before the job is his and clearly picked time and trust.

This is directly usable if you run a small studio or agency in Colombo or Galle. The engineer who left you eighteen months ago for a remote contract, and left on good terms, is often a better hire than a stranger with a stronger GitHub. You already know how they behave in a bad sprint. That information is worth more than most interview loops produce.

---

📊 Copying this on a two-person budget

You do not need a VP. You need the function. Concretely:

1. Name the owner. One person, by name, owns the ship date. Rotate it quarterly if you want, but never leave it blank.
2. Write dates against real working days. Sri Lanka has a lot of Poya days and public holidays, and a fortnight of calendar time is often eight working days. Our Sri Lanka working days calculator will give you the honest number between two dates. Quote clients from that, not from a calendar month.
3. Keep one written dependency list. Not a tool. A file. "X is blocked by Y, owned by Z, expected date D." Update it weekly.
4. Integrate early and often. If the parts have never been run together, your estimate is a guess.
5. Cost the delay, not the task. If a two-day slip idles a second engineer, the slip cost you four engineer-days. Our freelancer hourly rate calculator is a fast way to put a rupee figure on that if you bill by time.

Point 5 is the one that changes behaviour. Delays feel free until you write down what they cost.

---

💡 The career read for engineers

There is a quieter lesson here for anyone building a career from Sri Lanka. Legros presented the 2018 MacBook Air and the 2020 iPad Air on stage, so she was visible. But the reason she got called back was reportedly the trust, not the stage time.

Two things travel well across a decade:

• A reputation for hitting dates. It is boring, it is rare, and it compounds.
• Leaving well. The people who rehire you are the people you did not burn.

Neither shows up on a CV. Both decide whether you get the call four years after you stop working somewhere.

---

What this means for you

If you are a student or a junior engineer, notice that the delivery and coordination track is a real career, not a consolation prize for people who stopped coding. At Apple it goes to VP.

If you run a small team, the takeaway is narrower and more urgent. Assign the ship date to a person this week. Recalculate your current deadline against actual working days, not calendar weeks. And before you post a job ad, go through the list of people who have already worked with you and left on good terms.

Ternus had one hire to make before day one, and he spent it on the unglamorous function. Given that he is about to run a company that has to land hardware on a date, that is the correct instinct.

Bottom line: Ideas are not the bottleneck on most small teams. Coordination is. Staff it before you staff anything else.