“Confident, well-rounded .NET engineer with solid API design skills. Mid+ today and on a clear path to Senior.”
Gurgen Hakobyan · Senior Software Engineer at Highway CJSC
Assessed
Oct 3, 2026
Verification
Backend Engineering Verification (.NET)
Verdict: passed
Ruben performed well across the interview, showing broad and confident knowledge of the .NET backend topics covered and a solid understanding of API design.
2 of 2 skills demonstrated
His one notable gap is async programming in C#, which sits at a mid level and is the main technical area to strengthen. Beyond that, his progression to Senior depends mainly on gaining more experience solving complex problems independently. Assessment: Mid+, with strong potential to reach Senior in the near term.
Ruben answered confidently across all .NET topics covered, including dependency injection, IEnumerable vs IQueryable, FinTech-related questions, design patterns, and CQRS, showing a consistent and well-rounded command of the platform. The one area below this standard is async programming: his understanding of async/await and CancellationToken is functional at a mid level but lacks depth on how the underlying mechanics work. Overall: strong, broad .NET knowledge with a single, clearly defined area for growth.
API Design
Demonstrated
Ruben spoke confidently about REST API design, correctly applying HTTP method semantics and status codes and clearly explaining how middleware operates within the ASP.NET Core request pipeline. His answers were accurate and well structured, reflecting practical experience building and maintaining APIs. Overall: solid command of API design fundamentals, at or above the level expected for his grade.
Evidence
What happened in the session
Recommended that Ruben deepen his understanding of async programming in C#, specifically how async/await and cancellation work under the hood rather than only how to apply them, and that he strengthen his grasp of CQRS, including when and why to use it. To reach Senior, he needs more experience independently owning and solving complex problems end-to-end.
Action plan
What to do next
1
Async programming in depth. Study the compiler-generated state machine, thread-pool behaviour, sync-over-async pitfalls, and CancellationToken propagation. Confirm understanding through a short write-up or a team knowledge-share.
2
CQRS rationale. Go beyond the concept to the trade-offs: when separating read and write models pays off, when it is overkill, and how eventual consistency affects design. Apply or evaluate it on a real feature.
3
Independent problem ownership. Take on at least one complex, loosely specified task per quarter and drive it from problem definition through design and delivery, bringing options to the team rather than a single pre-decided solution.
4
Review at 3 months. Assess against point 3 specifically. Independent ownership is the deciding factor for Senior; points 1 and 2 are supporting.
