The DevOps Job I Almost Didn't Get Because of One Interview Question

Rahul had prepared for weeks for his first DevOps interview — brushing up on Docker, Kubernetes, CI/CD pipelines, all the trending buzzwords companies seemed to want. He walked in feeling confident. Then the interviewer asked something surprisingly basic: "Can you explain what a cron job is and set one up for me on the whiteboard?"

Rahul froze. He knew the concept vaguely, but he had spent so much time on advanced tools that he had skipped over genuinely fundamental Linux basics, assuming they were "too simple" to matter for a DevOps role. He fumbled through the answer and left the interview convinced he had blown it.

He didn't get an offer that day, but he did get honest feedback from the interviewer afterward: strong on tools, weak on fundamentals. That feedback stung, but it was fair, and Rahul decided to actually fix the gap instead of getting defensive about it.

He went back to basics, working through a proper cron job guide for automating tasks, something he had skipped over months earlier because it seemed "too beginner" for someone chasing advanced DevOps roles. He also revisited basic CentOS commands he thought he already knew, only to realise how shaky his actual understanding was.

Three weeks later, Rahul appeared for another interview at a different company. When asked a similar fundamentals-based question, he answered it clearly, confidently, without hesitation. He got the offer.

His advice to anyone prepping for a technical interview: don't skip the "basic" stuff just because it feels beneath your skill level. Interviewers ask fundamentals precisely because so many candidates, chasing trendy tools, quietly forget them. Solid Linux fundamentals aren't old-fashioned — they're the foundation everything else stands on.