Use what you have built
Begin with one familiar system: an approval workflow, an editor, a notification service, a capture pipeline, or a mobile shell.
Architecture practice means making constraints, alternatives, consequences, and verification visible; adding a new framework is only useful when it addresses a real constraint.
This is a public learning guide, not a personal performance assessment or a universal promotion rubric.
The role and the evidence
Staff and Principal titles vary between organizations; assess the scope of decisions, collaboration, and outcomes rather than assuming a title has a fixed meaning.[1]
Will Larson describes four recurring archetypes: Tech Lead, Architect, Solver, and Right Hand; use them to discuss the work a team needs rather than as a mandatory career sequence.[1]
| Competency | Evidence to look for | Practice next |
|---|---|---|
| Quality attributes | A measurable reliability or latency constraint | Write a stimulus, environment, response, and measurement |
| Trade-off analysis | A decision with a defensible rejected alternative | Compare options against the same constraints |
| Decision writing | A reviewed ADR | Record consequences and a revisit trigger |
| Domain modeling | Explicit business invariants and ownership | Map bounded contexts and transaction boundaries |
| Distributed data | An explanation of retries and consistency | Trace a duplicate event through the system |
API design | An explicit contract and compatibility policy | Specify errors, pagination, and idempotency |
| Frontend platform | A shared component with owners and consumers | Write contribution and deprecation rules |
| Security | A threat model with trust boundaries | Test authorization and failure paths |
| Operations | A measured SLI and a response runbook | Exercise one dependency outage |
| Infrastructure | An IaC change and a recovery procedure | Review drift, restore, and rollback |
AI systems | A versioned evaluation dataset | Compare quality, latency, and cost |
| Influence | A design changed through peer feedback | Document reviewers, disagreement, and adoption |
A design document helps communicate a decision, but evidence of influence also includes adoption, feedback, and the operational outcome after rollout.
Build a usable knowledge base
Start with Fundamentals of Software Architecture for vocabulary, MADR for decision records, C4 for system boundaries, and The Staff Engineer’s Path for technical leadership.[4][2][3][5]
Use Designing Data-Intensive Applications as a reference for replication, partitioning, transactions, and streams when your current design raises those questions.[6]
Frontend is an architecture domain
| Surface | Decision | Verification |
|---|---|---|
| Editor | Separate document state from the DOM; compare contenteditable, ProseMirror, and Lexical | Selection, composition input, undo, and audio synchronization |
| Checkout | Model pending, confirmed, failed, and unknown outcomes | Duplicate submits, timeouts, reconciliation, and retry with the same intent |
| Mobile shell | Compare WebView, native UI, and bridge permissions | Origin checks, identity handoff, and bridge input validation |
| Capture pipeline | Compare Tauri and Electron using platform access and workload constraints | Repeatable throughput, frame loss, CPU use, and backpressure |
| Shared platform | Define ownership, versioning, and compatibility before orchestration | Consumer upgrade path, accessibility, and rollback |
For payment-like actions, a disabled button improves the interface but server-side idempotency and reconciliation determine correctness when the result is uncertain.
Separate server state, shared client state, and local interaction state before choosing a library; neither a state library nor micro-frontends is a universal default.
SSE can deliver server updates while ordinary HTTP requests send commands; choose WebSocket when the interaction and connection requirements justify a bidirectional channel.[11]
Make failure part of the design
For a MySQL-backed notification service, write the business change and an outbox row in the same transaction, then let a worker publish committed rows.[7]
A relay can publish twice if it crashes after delivery but before recording completion, so track event identity and make the consumer idempotent.[7]
A direct polling worker does not require another queue; pg-boss requires PostgreSQL, while the Redis backend of BullMQ adds Redis, so choose those dependencies deliberately.[9][8][17]
Compare choreography with orchestration when a workflow spans services, and include compensation, partial failure, and operational ownership in the comparison.
Use expand-contract migrations with a backfill and a compatibility window, and combine dependency timeouts with a circuit breaker when repeated failures would otherwise cascade.
Security and operations are design inputs
Draw a threat model with assets, trust boundaries, actor permissions, and abuse cases before selecting security controls.
For payment pages, consult PCI DSS script authorization, integrity, and inventory requirements; nonce-based CSP is one control, not a universal substitute for compliance assessment.[12]
Define an SLI population and measurement window before setting an SLO; a proposed latency threshold is a target until real measurements support it.[10]
In this repository, Amplify/CDK infrastructure, limited reader Web Vitals collection, and chat evaluation tooling already exist; their presence alone does not establish deployment coverage or improved production outcomes.
AI systems need evidence too
Begin with the simplest workflow that meets the task, then add routing, parallelization, or agent autonomy only when evaluations justify the additional cost and failure modes.[14]
Compare RAG, long context, and fine-tuning against knowledge freshness, traceability, behavior, latency, and cost instead of treating them as interchangeable upgrades.
| Exercise | Artifact | Acceptance evidence |
|---|---|---|
Domain-document RAG | Retrieval, chunking, and source-access decisions | A labeled dataset with answerability, citation accuracy, and retrieval failures |
Read-only MCP tool | Tool contract, identity scope, and audit design | Authorization tests, adversarial output tests, and bounded calls |
| Chat evaluation loop | Immutable prompt and dataset versions | A quality, cost, and latency comparison against the baseline |
Use synthetic or explicitly shareable data, enforce permissions in the tool and data layers, and treat retrieved text as untrusted input rather than authority to execute instructions.
Make the reasoning reviewable
A useful design document covers context, goals and non-goals, proposed interfaces and data, alternatives, risks, testing, rollout, rollback, and success criteria.
Use MADR for a focused decision record and C4 context or container diagrams for boundaries, then add a sequence or state diagram only where behavior needs explanation.[2][3]
| System | Trade-off to explain | Evidence to include |
|---|---|---|
| Approval workflow | Explicit routing vs. a general rules engine | State transitions, invariants, permission boundaries |
| Notifications | Synchronous dispatch vs. durable asynchronous delivery | Failure sequence, duplicates, replay, operating cost |
| Transcript editor | Document model vs. implicit DOM state | Composition input, selection, synchronization tests |
| Screen capture | Native access, portability, and processing cost | Measurement method, workload, frame loss, bottleneck |
| Mobile shell | Native capability vs. shared web delivery | Bridge trust boundaries, authentication, recovery |
Use public or synthetic examples and describe the method without publishing employer schemas, client identifiers, credentials, or private traffic data; a public app does not make its implementation public.
Practice the explanation
Use RADIO for frontend design: Requirements, Architecture, Data model, Interface, and Optimizations; agree on the interview's scope before selecting the depth of each step.[15]
For backend or full-stack practice, cover requirements, entities, interfaces, data flow, high-level design, and failure analysis without imposing a fixed time budget on every interview.
| Session | System | Deep dive |
|---|---|---|
| 1–2 | Notifications | Delivery guarantees and dead-letter replay |
| 3–4 | Collaborative transcript editor | Conflict resolution, selection, and latency |
| 5–6 | Checkout | Idempotency and uncertain outcomes |
| 7–8 | Notification growth | Capacity estimates, ordering, and operating cost |
| 9–10 | Streaming transcription | Backpressure, disconnects, and vendor failure |
| 11–12 | Shared frontend migration | Ownership, compatibility, rollout, and rollback |
An illustrative workload of 1 million daily users receiving 10 notifications each produces about 116 notifications per second on average; a 10× peak assumption gives about 1,160 per second and must be checked against observed traffic.
A sustainable growth roadmap
Use one shared budget of 6 hours per week: 2 hours for writing, 2 hours for targeted reading, 1 hour for implementation, and 1 hour for practice.
The milestones below are suggestions, not delivery promises; narrow or extend a phase when review, access, or real work consumes the available time.
| Phase | Focus | Reviewable output |
|---|---|---|
| Weeks 1–2 | Document a familiar decision | One ADR and one system context diagram |
| Months 1–3 | Publish, review, and revise | One case study, a risk review, and peer feedback |
| Months 4–6 | Deepen one failure-prone path | An outbox experiment or reliability exercise with measurements |
| Months 7–12 | Choose one infrastructure or AI gap | A recovery drill or an evaluation-backed demo |
| Months 13–18 | Lead a decision with other people | A reviewed proposal, adoption evidence, and rollout results |
| Months 19–24 | Consolidate and teach | Revisited decisions, a retrospective, and a talk or article |
Choose a certification only when its skills match your work or a verified role requirement; check the provider for current exam names, availability, and fees.
Sources and verification boundaries
The references below support specific concepts; the exercises, sequence, and completion criteria are editorial recommendations rather than requirements imposed by those sources.
This edition removes personal scoring, application strategy, salary comparisons, speculative release forecasts, and unverified claims about company interview expectations.
Read foundational books alongside practical documentation, and consult the AWS Well-Architected Framework to review operational excellence, security, reliability, performance, cost, and sustainability.[13]
Recheck mutable documentation when implementing a technique, and validate privacy, contracts, and applicable regulation for the actual system rather than treating this guide as a compliance opinion.
- Will Larson · Staff archetypes
- MADR · Markdown Architectural Decision Records
- Simon Brown · C4 model
- Richards & Ford · Fundamentals of Software Architecture, 2nd edition
- Tanya Reilly · The Staff Engineer’s Path
- Kleppmann & Riccomini · Designing Data-Intensive Applications, 2nd edition
- AWS · Transactional outbox pattern
- MySQL · BINARY and VARBINARY
- pg-boss · Introduction
- Google SRE Workbook · Implementing SLOs
- MDN · Using server-sent events
- PCI SSC · Payment Page Security and Preventing E-Skimming
- AWS · Well-Architected Framework
- Anthropic · Building effective agents
- GreatFrontEnd · The RADIO Framework
- Neal Ford · Architectural Katas
- BullMQ · Introduction and storage backends