A standard report from our evaluations.
Example
technical report
Candidate:
Jane Doe
Role:
Software Architect
Duration:
48 minutes
Date:
22 Nov 2025
Interviewer:
Dan Radu Dragomir
Primary Scenario Used:
Distributed Event-Driven Architecture for Real-Time Analytics
Recommendation:
Strong hire
High-level summary
Brief, 4–6 lines describing the overall impression and context.
Jane demonstrated architect-level thinking across system design, distributed data flows, and fault-tolerant event processing. She showed strong command of scalability models (horizontal partitioning, CQRS, event sourcing), reasoning clearly about trade-offs, consistency boundaries, and cost implications. Her approach remained stable even under heavy complexity escalation, and she handled system degradation with calm, structured risk-management strategies.
Overall, she operated at a high architectural maturity level, demonstrating the ability to design and guide complex distributed systems.
Scoring Rubric
Problem Understanding &
Clarification (PUC)
5/5
Solution Reasoning &
Decomposition (SRP)
5/5
Technical Depth &
Correctness (TDC)
5/5
Adaptability Under
Complexity (AUC)
5/5
Error Detection &
Correction (EDC)
4/5
Communication &
Expression (CTE)
5/5
Engagement &
Attitude (EPA)
5/5
Weighted
Final Score
4.93/5
Scenario Performance Summary
Short narrative describing: candidate’s approach, quality of reasoning, adaptability, trade-offs, and structure
The scenario required designing a real-time analytics platform processing millions of events per minute across multiple global regions. Jane demonstrated a deep understanding of event-driven architecture, partitioning strategies, regional isolation, multi-cluster Kafka configurations, and real-time aggregation pipelines.

Her initial high-level design addressed throughput, latency, operational safety, and multi-region failover. When asked to account for regulatory restrictions, she re-balanced the architecture with region-specific data retention boundaries and cross-region asynchronous replication. She also proposed a staged rollout plan, capacity modeling estimates, and observability standards appropriate for an enterprise-level system.

This level of sophistication reflects a senior architect who can guide large-scale system evolution.
Error Injection Response
How they behaved when faced with an error.
We introduced a hidden flaw: one region’s message broker cluster experiences intermittent network partitioning under high load. Jane immediately recognized the risk of dual-write hazards and suggested a write-redirect strategy using leader election and fenced tokens, preventing split-brain conditions. She also proposed compensating patterns to ensure downstream consistency once connectivity is restored. This response shows strong distributed-systems intuition, though she could have explored deeper into conflict resolution (CRDTs, vector clocks).
Strengths
Strong reasoning around distributed systems
Excellent response to complexity and error conditions
Clear, structured communication
Good understanding of async processing models
Mature approach to trade-offs and scalability
Risks / Gaps
Limited exposure to container orchestration details (Kubernetes specifics)
Could improve depth in observability patterns (tracing vs logging)
Some hesitation around optimizing DB write-path under extreme load
Final Recommendation
Each report ends with a hiring recommendation and a brief explanation of why.
Recommendation: Strong Hire
Jane operates at a true architect level with strong distributed-systems intuition, advanced scenario reasoning, and excellent communication. She demonstrates the ability not only to design large-scale systems but also to guide teams, assess risk, and maintain clarity under pressure. She would be a valuable asset in architecting distributed, high-throughput, or enterprise-critical platforms.