Stage 3: Marathon Warrior

Train learners to endure and perform in long interview sessions, handling diverse technical and behavioral questions back‑to‑back. Build confidence, stamina, and adaptability for real multi‑round interviews.

Hackbook Overview

• Marathon Simulation: Extended Q&A across multiple domains.
• Stamina Building: Practice answering 15–20 questions in one sitting.
• Balance: Switch seamlessly between technical depth and behavioral clarity.
• Time Discipline: Technical answers (60–90 sec), behavioral answers (90–120 sec).
• Why It Matters: Real interviews often last hours — this prepares learners to stay sharp throughout.

Hands‑On Practice

• Attempt a mock marathon: 10 technical + 10 behavioral questions in sequence.
• Record the session and review pacing, clarity, and confidence.
• Identify weak areas (technical gaps or vague behavioral answers) and refine.
• Practice recovery: if stuck, pause, reframe, and continue confidently.

Interview Question Bank

Technical (Linux Focus)

• Q1. How do you check CPU usage in Linux?
  A1. top, htop, or mpstat.
• Q2. How do you find and kill a process?
  A2. ps aux | grep <process> then kill -9 <PID>.
• Q3. How do you check disk usage?
  A3. df -h for overall usage, du -sh for directory size.
• Q4. How do you check memory usage?
  A4. free -h or top.
• Q5. How do you check system logs?
  A5. journalctl -u <service> or /var/log/syslog.
• Q6. How do you schedule recurring tasks?
  A6. Use crontab -e.
• Q7. How do you check which process is using a port?
  A7. lsof -i :<port> or ss -tulnp.
• Q8. How do you restart and enable a service?
  A8. systemctl restart <service> and systemctl enable <service>.
• Q9. How do you check failed login attempts?
  A9. Review /var/log/auth.log.
• Q10. How do you check which services start at boot?
  A10. systemctl list-unit-files --type=service.

Behavioral (Marathon Focus)

• Q11. Tell me about a time you solved a problem under pressure.
  A11. STAR example: Production outage → fixed config → restored service in 10 minutes.
• Q12. Describe a time you worked with a difficult teammate.
  A12. “I listened to their concerns, clarified misunderstandings, and focused on shared goals.”
• Q13. Give an example of when you showed leadership.
  A13. “I led a small team to automate deployments, assigning tasks clearly and ensuring everyone contributed.”
• Q14. Tell me about a time you improved a process.
  A14. “I implemented log rotation, reducing manual cleanup and preventing recurring disk space issues.”
• Q15. Describe a time you learned from failure.
  A15. “I misconfigured a firewall rule, documented the mistake, corrected it, and improved my checklist.”
• Q16. Tell me about a time you adapted quickly to change.
  A16. “When our team switched to Docker, I learned it hands‑on and helped teammates adapt.”
• Q17. How do you handle conflicts in a team?
  A17. “I listen actively, clarify misunderstandings, and focus on shared goals.”
• Q18. Tell me about a time you balanced multiple responsibilities.
  A18. “I managed coursework and freelance projects by scheduling tasks and communicating progress clearly.”
• Q19. Tell me about a time you mentored someone.
  A19. “I guided a junior teammate by simplifying Linux concepts and sharing cheatsheets, boosting their confidence.”
• Q20. Tell me about a time you explained a technical concept clearly.
  A20. “I explained Linux permissions using a house analogy — owner, family, and guests — which made it easy to understand.”

Cheatsheet (Quick Notes)

• Technical Prep: top, ps, df, du, systemctl, journalctl, crontab, lsof.
• Behavioral Prep: STAR stories for teamwork, leadership, adaptability, problem‑solving, failure.
• Time Discipline: Technical answers: 60–90 sec; Behavioral answers: 90–120 sec.
• Mindset: Treat marathon practice as real interview simulation.