Interview
Interview preparation
Questions of the five kinds interviews actually use: explain a concept, predict what a program prints, find the bug, write the code, and reason through a scenario. Every answer explains why, and every program’s output was produced by running it.
SQL interview questions
25 questions in two guides, plus scenario questions for data analysts
Joins, aggregation, subqueries, window functions and the questions that separate a rehearsed answer from an understood one; every query runs in the SQL playground.
C# interview questions
13 questions · 4 concept, 4 predict the output, 2 debugging, 1 coding, 2 scenario
Thirteen C# questions of the kind asked in .NET developer interviews, from junior to senior: value versus reference semantics, integer arithmetic traps, LINQ deferred execution, exception flow, async ordering and design trade-offs.
Rust interview questions
12 questions · 4 concept, 3 predict the output, 2 coding, 2 debugging, 1 scenario
Twelve questions of the kind asked in Rust interviews at junior, mid and senior level: ownership and borrowing, the String and &str split, iterators, pattern matching, Result and Option, and the trade-off between generics and trait objects.
PHP interview questions
12 questions · 2 concept, 4 predict the output, 2 debugging, 2 coding, 2 scenario
Twelve questions that cover what PHP interviews actually probe: string quoting, the PHP 8 comparison rules, the `===` habit, array functions that keep or drop keys, references in `foreach`, strict types, generators, input validation, immutable objects and migrating legacy code.
How to use these
- Read the question, answer it out loud before opening the answer, then compare. The gap is what to study.
- For output-prediction questions, commit to an answer first; then press Run and see why you were right or wrong.
- For coding questions, write your own version in the language’s practice section before reading the reference.
- Scenario questions have no single answer; the point is the trade-offs you can name.