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

4 questions in Profiling.

  1. Profiling advanced

    A data platform has good tracing and still cannot explain why a specific job is slow. What does tracing not tell you, and what does?

    2 min answer databricksprofilingtracingcpu
  2. Profiling advanced Multiple choice

    A developer-tools company needs to find a performance regression that only appears under real production workloads. What are the options for profiling in production, and what are their costs?

    2 min answer profilingcontinuous-profilingsamplingoverhead
  3. Profiling advanced

    A service is slow and CPU utilisation is 4%. What do you profile and what do you expect to find?

    2 min answer profilingwall-clockblockingio
  4. Profiling advanced

    Discord's 2020 post on rewriting its Read States service from Go to Rust described latency spikes on a roughly two-minute cadence, matching Go's forced garbage-collection interval, in a service that allocated very little. An engineer brings you a similar graph today and asks you to fund always-on profiling across 12000 containers. Walk me through what you would fund and what you would refuse.

    3 min answer discordprofilinggarbage-collectiontail-latency