Loading…
The same question bank, ordered for the loop you are actually in. A cloud architect interview and a site reliability interview share a lot of material and weight it completely differently — these paths reflect that weighting, and each one links into the bank filtered to that role.
Software engineering interviews weight coding heavily, with a system design round from mid-level upward and a behavioral round that decides more than candidates expect.
A role path lists what the loop contains. A study plan puts it in order, easiest first, with the first week free.
Because loops are weighted very differently. A cloud architect interview spends most of its time on service selection, migration and cost, with comparatively little capacity arithmetic; a site reliability loop expects the arithmetic to be the centrepiece; a backend loop weights coding above both. Preparing for one as though it were another is the most common way strong candidates underperform.
Each role selects questions from the bank by question type and canonical topic, so a path reflects what that loop actually emphasises rather than a hand-picked list that goes stale. Every role page shows its full matching set and links into the question bank filtered to that role.
Most titles are variants of the roles here — cloud engineer, DevOps engineer, production engineer, MLOps engineer, solutions acceleration architect and applied solutions architect all map onto one of these loops. Each role page lists the titles it covers.
SRE interviews combine coding, systems design with real capacity numbers, and troubleshooting — plus how you measure and defend reliability.