The Skills Map and Your Route In

The idea in one minute#

The role needs four kinds of skill: AI (what models can and cannot do), systems (how software and cloud fit together), business (value, cost, how organisations decide) and communication (writing, drawing, running a room). Nobody arrives with all four. Everybody arrives with one or two.

The route in is therefore the same for everyone and different for everyone: find your strong side, fill the weakest side to “good enough”, and prove it with artefacts — a design document, a cost model, a working prototype — not with a list of courses watched.

Architects are described as T-shaped: broad across all four, deep in one. This lesson gives you the map, a way to score yourself, and a study plan that fits around a job.

A picture#

flowchart TB
  subgraph AI["AI"]
    direction TB
    A1[":i-brain: How models behave<br/><small>tokens, context, limits</small>"]
    A2[":i-search: Patterns<br/><small>retrieval, agents, tuning</small>"]
    A3[":i-flask-conical: Evaluation<br/><small>does it work, as a rate</small>"]
  end
  subgraph SYS["Systems"]
    direction TB
    S1[":i-cloud: Cloud basics<br/><small>compute, network, identity</small>"]
    S2[":i-database: Data<br/><small>where it lives, who may see it</small>"]
    S3[":i-shield-check: Security and reliability"]
  end
  subgraph BIZ["Business"]
    direction TB
    B1[":i-coins: Cost and value<br/><small>unit cost, ROI, TCO</small>"]
    B2[":i-scale: Risk and regulation"]
    B3[":i-building-2: How enterprises buy and decide"]
  end
  subgraph COM["Communication"]
    direction TB
    C1[":i-message-square: Discovery<br/><small>asking, listening</small>"]
    C2[":i-file-text: Writing and diagrams"]
    C3[":i-users: Running a room<br/><small>workshops, reviews</small>"]
  end
  AI --> T[":i-layers: <b>The architect</b><br/><small>broad in all four, deep in one</small>"]
  SYS --> T
  BIZ --> T
  COM --> T
  class A1,A2,A3 compute
  class S1,S2,S3 memory
  class B1,B2,B3 queue
  class C1,C2,C3 io
  class T neutral

How it really works#

The twelve skills, and what “good enough” means#

“Good enough” is the bar for the skills that are not your deep one. It is lower than people fear.

Score yourself#

Give yourself 0–3 on each of the twelve.

0  I could not explain it to a friend
1  I could explain it, but I have never done it
2  I have done it once, with help
3  I have done it more than once and could teach it

Add each area’s three scores (maximum 9). Your highest area is your spike. Any area under 3 is a gap that will embarrass you in a meeting and should be closed first.

Five common starting points#

A 24-week plan that fits around a job#

About six to eight hours a week. Each phase ends with something you can show.

The “Do” column is not optional. Reading produces vocabulary; only doing produces judgement, and judgement is what the role is hired for.

The habits that separate architects from senior engineers#

• Write before you draw. A paragraph that states the problem exposes gaps a diagram hides.
• Ask “compared with what?” Every benefit is measured against today’s process, not against nothing.
• Carry three numbers. Volume per day, cost per task, and the accuracy the business can live with. If you do not know them, your next meeting is to find them.
• Prefer the reversible choice. When two options look equal, take the one that is cheaper to undo.
• Keep a decision log. One line per decision, with the date and the reason. In six months it is the only memory the project has.

What you do not need#

• A degree in machine learning. You need to predict how models behave, not derive them.
• To train a model from scratch. Useful once, for intuition; not part of the job.
• Every cloud. Learn one properly; the other two then take a week each.
• Every framework. Frameworks last a year. Patterns last a decade.

Remember this#

• Four areas: AI, systems, business, communication. Broad in all, deep in one.
• Close any area that scores under 3 out of 9 before deepening your spike.
• Artefacts prove skill: a design document, a cost model, an evaluation plan, a demo.
• Judgement comes from doing the exercise, not from reading the lesson.

Try it#

1. Score yourself on the twelve skills. Write down your spike and your lowest area.
2. Pick your row in the starting-points table and schedule the first of its three actions this week.
3. Start a decision log today, in any tool. Enter your first decision: which cloud you will learn properly, and why.

Check yourself#

1. What does T-shaped mean for an architect?
2. Why does the plan insist on an artefact at the end of every phase?
3. A strong ML engineer wants this role. Which area is most likely to be their gap, and what is the fastest way to close it?