0% completed
Course Introduction
On This Page
Who the Course Is For
What a Solutions Architect Does
The Running Example
How the Course Is Organized
How the Practice Formats Work
Using the Course in 2, 4, or 8 Weeks
Key Takeaways
This course does four things:
- It prepares you for solutions architect interviews by teaching the job through the rounds that test it.
- It explains each design decision with numbers, including the option that was rejected and the reason.
- It shows customer conversations as real exchanges, often with a weak version and a strong version side by side.
- It shows what a mid-level answer contains and what a senior answer adds.
It also leaves three things out. It is not a tour of cloud services, and it does not prepare you for a certification exam. It also gives no pay figures, because they change too often to state reliably.
The sections below explain who the course serves, how its chapters fit together, and how to use it in the time you have.
Who the Course Is For
The course is written for engineers who are moving into solutions architect roles, and for working solutions architects who are changing companies. Most readers have about 3 to 10 years of experience as software, cloud, or infrastructure engineers. Many of them already pass system design interviews, but they have never been asked to run a conversation with a customer or present a recommendation to an executive.
You are expected to know what a server, a database, and a cloud account are. The course explains the rest, including the cloud services that each design uses and the arithmetic behind each estimate.
What a Solutions Architect Does
A solutions architect (SA) helps a customer turn a business problem into a technical design on a vendor's platform, and then helps the customer put that design into production. The vendor is the company that sells the platform, such as a cloud provider. The customer is the organization that pays for it. The SA works for the vendor, but the work succeeds only when the design is right for the customer.
The work starts with discovery, a set of conversations that find the customer's goals, limits, and current systems before anyone proposes a design. It continues with a proposal, a cost estimate, a small working test of the riskiest assumption, and reviews while the customer's engineers build. Companies test this work in an interview loop, a sequence of interviews in which each interview, or round, tests part of the job.
The Running Example
Many lessons return to one home furniture retailer, so that each new topic builds on numbers you already know. The retailer has 140 stores and an online store that brings in 30 percent of its sales. It runs about 220 servers in a rented data center whose lease ends in 18 months.
In a normal busiest hour, the online store receives about 400 orders. During the holiday sale week, that rises to about 2,400 orders an hour, 6 times normal. At the last sale, the store was unavailable for 3 hours on the first morning. The retailer's 12 infrastructure engineers have no production cloud experience.
The lessons on the job, cloud foundations, cost, generative AI, discovery, and the presentation all use this retailer. Case studies and practice interviews use short examples of their own, so that you practice on problems you have not seen before.
How the Course Is Organized
The chapters move from the job, to the design skills it needs, to the customer skills it needs, and then to screens and full practice. The diagram shows every chapter in reading order.
- The job and its foundations. What a Solutions Architect Does explains the role, the roles next to it, one customer engagement from the first call to production, and how interview loops test the job. Cloud Foundations for Architects covers compute, storage, networking, security, availability, and the Well-Architected Framework.
- Design. The Architecture Design Round gives a method for design answers, cost estimation, and changing requirements. Architecture Case Studies applies the method to ten interview questions. Generative AI Solution Architecture covers model services, retrieval, guardrails, and model cost.
- Customers and communication. Customer Discovery and Objections, The Presentation Round, and Behavioral Answers for Solutions Architects cover the rounds that software engineering interviews rarely prepare you for.
- Screens and practice. The Technical Screen covers short breadth questions and a coding exercise. Company Interview Guides describes reported loops at AWS, Microsoft, Google Cloud, Databricks, Snowflake, and AI companies. Full Practice Interviews ends the course with a preparation plan and three practice interviews: a mid-level loop, a senior loop, and a generative AI specialist round.
Most lessons teach the subject first and keep interview advice in one section near the end, called Using This in an Interview. Lessons whose subject is a round, a case study, or a practice interview treat the whole lesson as interview practice.
How the Practice Formats Work
Five formats give you practice inside the course, in addition to the practice questions that end each lesson.
Case studies. Each case study begins with the interviewer's question. It then follows the same order every time: questions to ask first, with the interviewer's answers, then requirements with the arithmetic shown, the design, failure, security, cost, and the rollout plan. Each one ends with a mid-level answer next to a senior answer, and with follow-up questions. Before you read the design, write your own answer, and then compare the two.
Role-play transcripts. The discovery chapter shows conversations between an SA and a customer turn by turn. A weak exchange often comes first, followed by a strong one, so that you can see which sentence changed the result. The chapter ends with a full role-play round, in which the interviewer plays a doubtful customer, followed by a debrief.
The presentation chapter. It explains what the round judges, plans a 20-minute talk minute by minute, and covers the questions that follow it. Its last lesson is a complete presentation with the interviewer's notes. The course also notes where reported formats differ, so that you can prepare for more than one length.
Practice interviews. Each practice interview gives the rounds as condensed exchanges between the interviewer and the candidate. The interviewer's notes come next, and a debrief names what earned points and what lost them. At least one answer contains a mistake and its recovery, because real candidates make mistakes too.
Assessments. Every chapter from Cloud Foundations for Architects through Company Interview Guides ends with an assessment. Each attempt draws 10 questions from a larger bank, so a second attempt covers different material. Most questions give you a situation and ask for a decision, a number, or the next question to ask. A final assessment of 25 questions, drawn from a bank of 60, follows the practice interviews.
Using the Course in 2, 4, or 8 Weeks
Choose the plan that fits the time before your interviews. The course has 55 lessons after this one.
| Time | Plan |
|---|---|
| 2 weeks | About 2 hours a day. Days 1 and 2: the role chapter and your two weakest cloud foundations lessons. Days 3 to 5: the design method, cost estimation, and two case studies. Days 6 to 8: discovery, objections, and the role-play. Days 9 and 10: the presentation. Days 11 and 12: behavioral stories and the technical screen. Days 13 and 14: one mock loop, then fix your weakest answer. |
| 4 weeks | About 14 lessons a week. Week 1: What a Solutions Architect Does, Cloud Foundations for Architects, and The Architecture Design Round. Week 2: Architecture Case Studies and Generative AI Solution Architecture. Week 3: discovery, the presentation, and behavioral answers. Week 4: the technical screen, the company guide for your target, and the practice interviews. |
| 8 weeks | About 7 lessons a week in reading order, with every chapter assessment. Add one mock interview each week from week 4. |
A 30-Day Preparation Plan, in the last chapter, divides the 4-week version by day. In every plan, say your answers aloud. An answer that reads well on the page can still become unclear when you must speak it and then answer a follow-up question.
Key Takeaways
- The course teaches the SA job through the rounds that test it, with numbers, rejected options, and level differences.
- One furniture retailer appears in many lessons, so its numbers build from lesson to lesson.
- Case studies, role-play transcripts, a presentation chapter, practice interviews, and assessments give practice inside the course.
- Choose the 2, 4, or 8 week plan that fits the time before your interviews, and practice aloud.
The first lesson, What a Solutions Architect Does, follows the retailer's SA from the first message of its chief technology officer (CTO) to the last server switched off, and shows how the result was measured.
Reading Progress
0%
On This Page
Who the Course Is For
What a Solutions Architect Does
The Running Example
How the Course Is Organized
How the Practice Formats Work
Using the Course in 2, 4, or 8 Weeks
Key Takeaways