Portfolio ↗

Quiz

2988 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2988 Architecture Fundamentals91 Distributed Systems111 Data Architecture100 Cloud Architecture97 Networking96 API & Integration Architecture97 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98
Difficulty Any beginner intermediate advanced

5 questions in Presenting to Engineers.

  1. Presenting to Engineers intermediate

    A platform team's documentation is comprehensive and its users still ask questions it answers. What is wrong with the writing?

    2 min answer dbt-labsdocumentationdeveloper-experiencestructure
  2. Presenting to Engineers intermediate

    An architect's design is technically sound and the engineering team resists implementing it. What is usually the communication failure?

    2 min answer communicationbuy-inrationaleengineers
  3. Presenting to Engineers advanced

    At 22:52 UTC on 21 October 2018 GitHub lost connectivity between its US East Coast network hub and its primary East Coast data centre for 43 seconds while failing optical equipment was replaced. The cascade produced 24 hours and 11 minutes of degraded service in which repository data was intact but webhooks were not delivered and Pages sites were not built. What does an incident shaped like that demand of a status report and what does a single overall indicator make impossible?

    3 min answer githubstatus-pageincident-communicationcomponents
  4. Presenting to Engineers advanced

    How do you get a team to adopt an approach they initially disagree with?

    2 min answer influencecredibilityreasoningcollaboration
  5. Presenting to Engineers intermediate

    Six weeks after a design was agreed, three of its four key decisions are implemented differently and nobody raised it. The document has 18 comments with 16 of them from two people, 11 of 14 engineers opened it once, and the decision record was merged with two approvals in under four minutes. What do you conclude, which signal is misleading, and what would have caught this in week one?

    3 min answer design documentsreviewapprovalsdivergence