Linux mock interview
A four-question Linux screening interview. A senior engineer asks about slow boxes, full disks, dead cron jobs, and least privilege - and never tells you how you did until the debrief.
what this interview covers
- First five minutes on a slow box
- Disk mysteries
- Silent automation failures
- Permissions and least privilege
- Proving the OS was at fault
How the interview works
4 questions, 1-2 follow-ups each. The interviewer will not confirm or correct anything until the debrief. You can say you do not know and move on - that beats bluffing. End early if you must; fewer than 3 answered means no verdict, but you still get per-question feedback.
about this track
About
This screen covers the Linux work that actually pages people: a production box gone slow, a disk that is full when du swears it is not, a cron job that died in silence, and the judgment calls around handing out privilege. Four questions per session, drawn from a bank of five, so a retake will surface one you have not seen. Expect one or two follow-ups per question - the interviewer pushes on whatever you leave vague, the same way a real screen does.
The interviewer never reacts. No "good answer", no "not quite", no hints - the same flat acknowledgment whether you nailed it or missed entirely, because leaking the verdict mid-interview would make the practice worthless. If you do not know something, say so and move on; that grades as uncovered ground, never as a strike against you, and it beats bluffing in this room exactly as it does in a real one.
The debrief is where you get paid. Each question comes back with what your answer covered, what a senior answer would also have hit, any flags an interviewer would quietly note, and a written model answer to measure yourself against - plus links into the Linux guides that cover the ground you missed. Retake the track later and the debrief shows the delta against your previous attempt.