Interview scorecard
Security Engineer
Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.
Threat modeling
Identifies how a system could be attacked and ranks which threats deserve attention first.
Questions
- Tell me about a system you threat modeled. How did you start?
- Tell me about a threat you ranked low. Why did you accept it?
- Describe a time a threat model missed something. What did you change afterward?
1: Below the bar
Lists generic threats without mapping the actual system. Cannot explain why one threat matters more than another.
3: Meets the bar
Maps the system, names realistic attackers and entry points, and ranks threats with some reasoning. Follow-through after the model is thin.
5: Above the bar
Maps data flows and trust boundaries first, ties threats to specific attackers, explains rankings clearly, and revisits the model as the system changes.
Secure code review
Reads code to find security flaws and explains clearly how to fix them.
Questions
- Tell me about a vulnerability you found during a code review. How did you spot it?
- Walk me through how you review a change that handles user input or logins.
- Tell me about a time a developer disagreed with your review finding. What happened?
1: Below the bar
Relies only on automated scans or a generic checklist. Misses flaws in the code and gives vague fixes.
3: Meets the bar
Checks inputs, access control, and secrets by habit. Finds common flaws and suggests fixes developers can use.
5: Above the bar
Traces data through the code to find subtle flaws. Shows the impact, gives a specific fix, and wins over the developer.
Incident response
Contains and investigates security incidents calmly, preserving evidence and keeping the right people informed.
Questions
- Tell me about a security incident you handled. What did you do in the first hour?
- Tell me about a time you had to contain a problem with incomplete information.
- Tell me about what you changed after an incident so it wouldn't happen again.
1: Below the bar
Describes reacting without a plan. Skips evidence, logs or notes, and can't say what was learned afterward.
3: Meets the bar
Follows a clear sequence of detect, contain and fix. Keeps notes and informs others, but follow-up changes are modest.
5: Above the bar
Contains quickly while preserving evidence, decides with partial facts, updates others at set times, and drives lasting fixes afterward.
Security tooling
Selects, configures, and tunes security tools so they find real problems without drowning the team in noise.
Questions
- Tell me about a security tool you rolled out. How did you choose it?
- Tell me about a time a tool gave too many false alarms. What did you do?
- How did you check that a tool was actually catching what it should?
1: Below the bar
Names tools but not why they were chosen. Leaves default settings alone and ignores noisy alerts or missed findings.
3: Meets the bar
Chooses a tool for a clear need and adjusts settings to cut noise. Checks results mostly after complaints.
5: Above the bar
Compares options against specific needs, tunes alerts with data, and tests that the tool catches known issues. Tracks results over time.
Risk communication
Explains security risks to non-security people so they can make informed decisions and act.
Questions
- Tell me about a time you explained a security risk to a non-technical audience.
- Describe a time someone disagreed with your risk assessment. What did you do?
- Tell me about a time you recommended accepting or delaying a fix. How did you present it?
1: Below the bar
Uses technical terms the audience can't follow. Describes the risk as scary or minor without impact or options.
3: Meets the bar
Explains the risk in plain words with likely impact. Offers a recommendation but gives little context on cost or alternatives.
5: Above the bar
Frames risk in business terms with likelihood, impact and options. Adapts to the listener and gets a clear decision.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.