A strong senior engineer is promoted to architect and struggles. Which skills transfer and which must be learned?

What transfers

Technical depth, systems knowledge, the instinct for what will break, and the credibility that comes from having shipped and operated things. These are the foundation, and an architect without them is advising on subjects they do not understand.

What must be learned

1. Deciding with insufficient information. An engineer can usually investigate until certainty. An architect frequently cannot — the information does not exist yet, and waiting costs more than being partly wrong. The skill is deciding under uncertainty and designing so the decision can be revised.

2. Influence without authority. The architect usually cannot direct anyone. Designs are adopted because teams are persuaded, involved and given the reasoning — not because they were specified. An architect who issues conclusions gets compliance where it is unavoidable and workarounds everywhere else.

3. Communication at multiple altitudes. The same architecture must be explained to executives (cost, risk, decision), engineers (mechanism, interfaces, failure behaviour) and reviewers (trust boundaries, data flows). One artefact for all three serves none.

4. Saying no to good ideas. Much of the role is preventing complexity that is individually justified and collectively unaffordable — which requires being able to explain what a proposal costs, not merely that you dislike it.

5. Working through others. The architect's output is not code but decisions, boundaries and clarity that other people build against. A new architect who keeps doing the implementation is not doing the job.

6. Business fluency. Arguing for architecture in terms of revenue, risk and time to market rather than technical virtue — because technical virtue does not compete against a roadmap.

The failure mode of the transition

Continuing to be the best engineer in the room — reviewing every design, writing the critical code, resolving every technical debate personally. It feels productive, it does not scale, and it prevents the team from developing the judgement the architect is trying to spread.

The measure of the role is what the organisation can do without you, which is an uncomfortable inversion of what made the person successful as an engineer.