Explain a Past Security Project
Part of the Cybersecurity Roadmap
In short
"Tell me about a project you are proud of" is your chance to steer the interview. A clear story with your role, decisions and results beats a vague list of tools.
Walking an interviewer through a real project (from your portfolio or work) — the problem, your approach, what you found, and its impact — one of the most predictable interview questions.
Think of it like this
Telling the college fest story
When someone asks how you ran the college fest, you do not list every tent and speaker. You say what the challenge was, what you decided, what went wrong, and how many people came. A project story works the same way: focused, honest and with an ending.
Watch it happen
Answer structure
1/5One line on the problem: "My lab had no way to spot brute force logins."
The big ideas
What you need to know
Two to three minutes
Prepare a short version and a longer one. Let the interviewer pull you into details.
Numbers help
Time saved, rules written, findings fixed. Use honest numbers from your own work only.
Keep it ethical
Only describe authorised work: your lab, CTFs, or approved work tasks. Never share confidential client details.
Show the proof
Point to a GitHub repo, writeup or report they can look at later.
Save yourself the pain
Common mistakes
Oops
Saying "we did" for everything so your role is unclear.
Do this instead
Say "I built" or "I decided" for your parts, and credit the team for theirs.
Oops
Listing tools without explaining decisions.
Do this instead
Explain why you picked each approach and what trade off you accepted.
Your mission
Write your project story
Quick check
Which part of a project story most clearly shows your growth as an engineer?
Go deeper
- 1Prepare a tight 2-3 minute walkthrough of your strongest Phase 14 portfolio project.
- 2Structure it as: problem, approach, findings, impact — in that order.
- 3Practice fielding a technical follow-up question about your methodology.
More behavioral at this stop
Handling a Real or Simulated Incident
Communicating Risk to Non-Technical Stakeholders
Staying Current With Threats & CVEs
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.
