Skip to content

Latest commit

 

History

History
34 lines (24 loc) · 1.17 KB

interview-star.md

File metadata and controls

34 lines (24 loc) · 1.17 KB

Explaining Your Work — the S.T.A.R Method

A lot of people struggle in interviews not because they lack skills, but because they can't explain their work clearly. S.T.A.R helps with that.

Use this structure to talk about any project — your capstone included.

S — Situation

What was the problem or context?

"Application logs were growing daily and manually checking them was slow."

T — Task

What were you responsible for?

"I needed to automate log analysis in Python so errors could be found quickly."

A — Action

What did you actually do? Be specific about the tech.

"I wrote a Python parser to count error levels, refactored it into a class, added a CLI with argparse, and exposed it via a FastAPI endpoint."

R — Result

What was the outcome? Quantify if you can.

"It cut manual log review time and gave the team quick visibility into issues."


Tips

  • Keep it to ~60–90 seconds spoken.
  • Lead with the result if the interviewer is impatient.
  • Have one flagship project you can go deep on — depth beats breadth.
  • Be honest about what you'd improve; it signals maturity.

See ../capstone/STAR.md to write your own.