Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
17 results for “Technical Leadership”
Technical Debt
The future cost incurred by choosing an expedient implementation now instead of the better one.
Technical Proposal
A written argument for a course of action, circulated for review before the work starts, structured so that disagreement surfaces early and cheaply.
Application Portfolio Management
Maintaining an inventory of every application with its owner, cost, business value and technical health, and using it to decide what to invest in, replace or retire.
Delivery vs Maintainability
Choosing where to take deliberate shortcuts, based on which kinds of debt are cheap to repay and which compound.
Fencing Token
A monotonically increasing number issued with leadership or a lock, checked by the resource, so writes from a deposed holder are rejected.
Lease
Time-bounded leadership or ownership that must be renewed before it expires, so a leader that becomes unreachable automatically relinquishes its role.
A 15-year-old monolith runs the core of the business. Leadership wants microservices. How do you approach it, and what would make you refuse?
What the interviewer is testing Whether you start from the business problem or from the target architecture, and whether you are willing to say no. First, estab
Leadership asks for multi-region "for resilience". What do you establish before designing anything?
First: is multi region the right answer to the actual problem? Multi region defends against a region wide failure . Most outages are not that — they are bad dep
Your observability bill is now 40% of your compute bill. Leadership wants it cut in half without going blind. What do you cut?
What the interviewer is testing Whether you understand what each telemetry type is for , so you can cut the redundant parts rather than cutting uniformly — whic
Southwest cancelled about 16,700 flights in December 2022 when crew scheduling could not recover from a storm, after years of deferred modernisation. How do you make that argument before the failure rather than after?
The case, as publicly reported A severe winter storm caused widespread cancellations across US carriers. Most recovered within days; Southwest did not. Its crew
The team can ship in six weeks with an approach that will need rework, or five months with one that will not. How do you decide, and what do you do either way?
What the interviewer is testing Whether you can make a debt decision deliberately rather than by default, and whether you know which debts are cheap and which a
Technical Leadership
Setting direction and carrying accountability without a team reporting to you.
Technical Constraints
Existing estate, skills, licences and platforms as inputs rather than obstacles.
Technical Debt
Deliberate, tracked and repaid — as distinct from mess.
Technical Proposals
A written argument circulated before the decision feels made.
Layered Architecture
The default shape, its clarity, and where a technical partition fails.
Service Boundaries
Drawing lines along change patterns rather than technical layers.