Skip to main content

Stage 1: Curious Runner

Warm learners up for full mock interviews by practicing short, timed Q&A sessions. Build stamina, confidence, and adaptability to handle both technical and behavioral questions under pressure.


Hackbook Notebook

  • Mock Interview Basics: Simulate real interview conditions with mixed questions.
  • Time Management: Keep answers concise (60–120 seconds).
  • Balance: Switch smoothly between technical and behavioral answers.
  • Mindset: Treat practice like the real thing — focus, clarity, confidence.

Hands‑On Practice

  • Answer 5 technical Linux questions in sequence, timed at 90 seconds each.
  • Answer 5 behavioral questions back‑to‑back, focusing on STAR structure.
  • Practice switching between technical and behavioral answers without hesitation.
  • Record and review for clarity, pacing, and confidence.

Interview Question Bank

Technical (Quick Fire)

  • Q1. How do you check disk usage in Linux?
    A1. df -h for overall usage, du -sh for directory size.
  • Q2. How do you restart and enable a service?
    A2. systemctl restart <service> and systemctl enable <service>.
  • Q3. How do you find which process is using a port?
    A3. lsof -i :<port> or netstat -tulnp.
  • Q4. How do you check memory usage?
    A4. free -h or top/htop.
  • Q5. How do you search for a string inside files?
    A5. grep -r "string" /path.
  • Q6. How do you check system logs?
    A6. journalctl -u <service> or /var/log/syslog.
  • Q7. How do you schedule a job in Linux?
    A7. Use crontab -e with proper syntax.
  • Q8. How do you check running processes?
    A8. ps aux or top.

Behavioral (Quick Fire)

  • Q9. Tell me about a time you solved a problem under pressure.
    A9. STAR example: Production outage → fixed config → restored service in 10 minutes.
  • Q10. Describe a time you worked with a difficult teammate.
    A10. “I listened to their concerns, clarified misunderstandings, and focused on shared goals.”
  • Q11. Give an example of when you showed leadership.
    A11. “I led a small team to automate deployments, assigning tasks clearly and ensuring everyone contributed.”
  • Q12. Tell me about a time you improved a process.
    A12. “I implemented log rotation, reducing manual cleanup and preventing recurring disk space issues.”
  • Q13. Describe a time you learned from failure.
    A13. “I misconfigured a firewall rule, documented the mistake, corrected it, and improved my checklist.”
  • Q14. Tell me about a time you adapted quickly to change.
    A14. “When our team switched to Docker, I learned it hands‑on and helped teammates adapt.”
  • Q15. How do you handle conflicts in a team?
    A15. “I listen actively, clarify misunderstandings, and focus on shared goals.”
  • Q16. Tell me about a time you balanced multiple responsibilities.
    A16. “I managed coursework and freelance projects by scheduling tasks and communicating progress clearly.”

Cheatsheet (Quick Notes)

  • Technical: df, du, systemctl, lsof, grep, crontab, journalctl.
  • Behavioral: STAR method, concise answers, focus on results.
  • Time Management: 60–120 seconds per answer.
  • Mindset: Treat practice as real interview simulation.

Tips, Tricks, Roadmaps, Resources, Networking, Motivation, Guidance, and Cool Stuff ♥

Updated on Dec 21, 2025