Skip to content
Rabat, Morocco
Posts

I’m an Experienced Backend Engineer. Here’s Why I Stumbled on “Junior” Interview Questions

December 15, 2025
I’m an Experienced Backend Engineer. Here’s Why I Stumbled on “Junior” Interview Questions
“The heart of the discerning acquires knowledge, for the ears of the wise seek it out.”
I’ve been a backend engineer for over six years, building systems and working with cloud infrastructure to solve real business problems. And yet, recently, during a technical interview, I froze. It wasn’t a question about designing distributed systems, explaining CAP theorem, or choosing between eventual and strong consistency. It was a question about the building blocks:
console.log(3 && 4);
console.log(3 || 4);
…and a SQL question: fetch the 7th row of a database table. And I stumbled. It was humbling, but also enlightening. It forced me to confront a reality many senior engineers face: the higher you go in architecture, the easier it is to lose touch with the fundamentals. Here’s what went wrong, why, and what I learned about staying sharp as a senior engineer. The Question:
console.log(3 && 4); // ?
console.log(3 || 4); // ?
  • I correctly answered 3 || 4 → 3.
  • I missed 3 && 4 → 4.
Why I Missed It: My brain has been wired for modern usage of &&, mainly in React or conditional checks:
const showButton = isLoggedIn && <Button />;
I rarely use && for raw integer values. Over time, I had abstracted the operator into a pattern, forgetting the low level behavior that it returns the last truthy operand. Lesson: Abstractions are powerful, but they can make us intellectually lazy. Knowing how to use a tool is different from understanding how the tool works. Extra Context: Revisiting MDN’s Logical AND (&&) reminded me that JavaScript’s behavior is precise, and sometimes surprising. The Question: Write a SQL query to return only the 7th row of a table.
SELECT *
FROM table_name
ORDER BY id
OFFSET 6 ROWS FETCH NEXT 1 ROW ONLY;
  • I hesitated. I knew LIMIT and OFFSET existed, but I couldn’t remember the exact syntax.
  • In senior roles, we often rely on ORMs or cursor-based pagination for performance:
# Example in Django
User.objects.all()[6]
  • Deep OFFSET pagination is a performance killer in production, so I’ve spent years avoiding raw queries like this. That’s why my brain blocked on the “simple” solution.
Lesson: Architectural purity is great—but interviews test fluency in the fundamentals. A senior engineer needs to be bilingual: high-level architecture and low-level syntax. Extra Context: See "Why You Should Avoid Offset Pagination" for production concerns. The Question: Discuss sorting complexities and Big O notation.
  • I blanked. While I could solve the problem practically, I couldn’t articulate the exact complexity on the spot.
  • In real-world senior backend work, “optimization” usually involves caching, indexing, or background processing, not implementing QuickSort manually.
Lesson: Algorithms are the grammar of computer science. Skipping formal practice erodes the ability to discuss trade-offs precisely. Even senior engineers benefit from occasional algorithm drills. It’s tempting to defend yourself: But that’s not the point. This interview reminded me that knowledge maintenance is required, not just code maintenance.
  • Failure is data. It shows where rust accumulates.
  • Fundamentals matter. You can’t mentor juniors effectively if you forget language mechanics.
  • Transparency is strength. Admitting gaps and then revisiting them demonstrates real seniority.
I’m now maintaining a “Story Backlog”: a collection of tricky questions, edge cases, and foundational concepts that I review weekly. Not just for interviews—but to keep my foundation solid.
“The prudent see danger and take refuge, but the simple keep going and pay the penalty.” - Proverbs 27:12
Keep building, but don’t forget to inspect the foundation.

Enjoyed this blog?

Seriously, thank you for spending your time here. If you made it to the end, you’re the kind of person who cares about craft, not just quick fixes.If you’d like to support my work, pick one (no pressure). It genuinely helps me keep writing and improving these blogs.
Subscribe to get a heads-up when I publish the next one. I keep it low-volume, and I only send what I’d personally want to read.

Subscribe to Josias's Newsletter

I occasionally write about software engineering, technology, and share thoughts on innovation and engineering.
One last thing: if you know someone who’d benefit from this, sharing it with them is one of the best compliments you can give. I appreciate you.