Microsoft-style coding and testing practice
Turn a requirement into a tested solution. Practice explaining how code behaves on empty input, invalid data and a normal path.
How should I show my testing approach in a Microsoft coding interview?
Microsoft's technical interview guide asks candidates to test their code and discuss boundaries and error cases. State the expected result for an ordinary case, then choose an input that exposes an assumption such as every matrix being square.
Microsoft's technical interview guidancePraxisAI practice drill
Check the last row of a tall matrix
Call a matrix upper triangular when all entries below the main diagonal are zero. Compare [[1, 2], [0, 3], [0, 0]] with [[1, 2], [0, 3], [4, 0]].
Expected result. The first matrix qualifies. The second fails because the 4 lies below the diagonal. A check that only loops over the two-column square misses that row.
Repository exercises
Search and filter this trackFind inputs your code overlooks
Compare the smallest ordinary input with a size or shape the implementation may not expect.
Check how changes affect existing users
Name one pre-existing behavior and test it again after the fix.
Take-home projects
Paid plan required to start. Each workspace stays open for 24 hours.
envcheck: a .env linter and diff tool
A developer tool that lints .env files with line numbers and reports drift against .env.example, never printing secrets.
About 2.5 hourseasyMinesweeper in the browser
The classic game with a pure, seedable rules engine, flood fill, chording, and mouse, touch and keyboard controls.
About 3 hourseasyRate limiter library and HTTP middleware
Token bucket and sliding window behind one interface, pluggable stores, injectable clock, and 429 middleware with Retry-After.
About 4 hoursmedium