Last week I asked what had quietly stalled for you. Fewer replies than I hoped, but the pattern was clear.

One reader wrote back with three words: "Stuck- building project." When I asked him to say more, he came back with a line a lot of you will recognise. "I don't know where exactly to start from, the right tools to use and how to approach building project in general." Another reader, a fresher trying to break into cloud, said something almost identical about where to begin. "I lack mentorship for career advancement. Could you please suggest me something?"

Two different asks, same underlying knot: not knowing which piece to pick up first. That answer is exactly what today is about.

If you replied last week and I have not got back to you yet, I will. Keep them coming.

There is a mistake I watch career changers make every single month, and it is not laziness.

It is starting with Solutions Architect Associate.

I understand why. It is the cert every job description mentions. It is the one with the salary studies. If a quiz ever told you that solutions architecture is your path, it feels like the obvious first move.

Here is the thing though. I joined AWS without a single AWS certification.

What I had was four Azure certifications, NHS data experience, and a manager who did something clever in my first week: he wrote down a sequence. Three AWS certs, in a specific order, easiest foundation first. I cleared all three in three months, during onboarding, while learning a new job.

The sequence did most of the work. Before it existed, I had been circling the certification catalogue for weeks, starting study plans and abandoning them.

When someone fails or abandons a cert, hard work is rarely the missing piece. One of three things happened:

They started with an associate-level exam that assumes fundamentals they had not built. Every study session felt like drowning, so the plan quietly died.

They collected certificates without building anything, then froze in interviews when asked to apply the knowledge.

Or they chased whatever cert was trending that month instead of the one their target role actually asks for.

Start with Cloud Practitioner unless you are already working hands-on in cloud. Four to six weeks. It gives you the fundamentals and a first pass under your belt. Momentum is a strategy in its own right.

Then match the cert to your target role. Aiming at solutions architecture? Solutions Architect Associate is now the right move, and it will feel climbable instead of crushing. DevOps? Go Solutions Architect Associate first, then the DevOps Engineer Professional path. Security? Security specialism after your associate. Data? The Data Engineer Associate.

Add the AI layer. Whatever your path, AI Practitioner belongs in your first three. In 2026, "cloud engineer who understands AI workloads" beats "cloud engineer" in nearly every shortlist I see.

One at a time, with a booked exam date. Book the exam when you start studying, not when you feel ready. Eight weeks out, maximum. A date in the calendar is the same checkpoint principle from last week's edition: it makes a quiet slide visible before it becomes a quit.

The free AWS Cert Roadmap lays out every path (SA, DevOps, security, data) with the order, realistic study times, and what to skip early. You are on the list, so this link goes straight to the PDF, no signup page:

→ Download the AWS Cert Roadmap (PDF)

💬 Where are you in the sequence: picking your first cert, stuck mid-study, or deciding what comes after a pass?

Reply with ORDER and your target role. I will tell you which cert I would book first and why. I read every reply.

Know someone circling the certification catalogue? Share your referral link. 1 friend subscribes, you get a free LinkedIn Profile Optimisation Checklist.

{{rp_refer_url}}

Shola

P.S. Last Tuesday I said this newsletter is weekly again. This is week two of the promise. Feel free to keep counting.