Loading...
Please sign in to view your progress
Security engineer interviews, from networks and cryptography to threat modeling and incidents. Train with Coach Vera, then take a mock with Marcus.
| # | Name | ||
|---|---|---|---|
1 | Start here. Twenty minutes with Marcus: explain HTTPS, investigate a suspicious process, rank
two findings and say the call to a VP. No hints on the call; your report scores five security
signals and tells you which modules to do first.
| ||
2 | The Security Loop Document | ||
3 | Learn what every security round scores, on one real-looking case: a key found in a repo. Watch
the attack and the fix move in Vera's 3D lab, then upgrade a CIA triad answer, take a timed
drill and write your own rules.
| ||
4 | A Google security phone screen with Marcus: why security, then "what is a vulnerability?" taken
deep on a real-looking bug report. Explain it underneath, rank it, fix it, defend the fix when
it breaks a partner. Written report after.
| ||
5 | Networks: Follow the Packet Document | ||
6 | Follow one packet from a café laptop to a server and see where trust changes hands. Predict the
weak hop and the backstop in Vera's 3D lab, then stop ARP poisoning your way, take a timed
drill and write your own rules.
| ||
7 | A Google technical round with Marcus: explain denial of service, then handle one live on a
public API. Size it, classify it, contain it at the edge, adapt when the attacker changes
tactics, and decide what to do when your own limit hurts a partner. Written report after.
| ||
8 | Web App Security: Source to Sink Document | ||
9 | Trace untrusted input from source to sink and fix it where it lands. Predict the sink and the
fix in Vera's 3D lab, then stop an SSRF your way, take a timed drill on file uploads and write
your own rules.
| ||
10 | A secure code review with Marcus in a shared editor: find the flaw in a small download helper,
explain it, fix it, test it with hostile names, then secure the same feature when reports move
to a public bucket. Python or Java. Written report after.
| ||
11 | Identity and Access: Who, What, and Which Way Document | ||
12 | See where sign-in and permissions break before an interviewer asks. Watch Vera work one OAuth
example in her 3D lab, then choose an access model for partners, take a timed zero-trust drill
and write your own rules.
| ||
13 | A Zoom technical round with Marcus: how would you attack the OAuth workflow? Walk the flow,
defend every step, rank the fixes, handle a marketplace curveball, then call a trade-off on your
own controls. Written report after.
| ||
14 | Cryptography: What It Guarantees and Where It Fails Document | ||
15 | Explain the handshake one level down and store passwords like a reviewer would. Watch Vera work
the TLS handshake in her 3D lab, then choose how to store passwords, take a timed drill and
write your own rules.
| ||
16 | A coding round with Marcus in a shared editor: group strings that encode to the same value under
a Caesar cipher, run the public tests, then explain why a teammate shouldn't "encrypt" secrets
this way. Written report with a hire band after.
| ||
17 | Threat Modeling: Draw It, Break It, Pick the Defense Document | ||
18 | Draw it, break it, pick the defense. Watch Vera threat model a clinic app in her 3D lab, then
find the cheapest way into a CEO's email and cut it, take a timed drill and write your own rules.
| ||
19 | A Google technical round with Marcus: design a cyber attack on a fictional freight company, at
the level of stages, then flip to the defender and pick the two controls that matter most. A
curveball and a trade-off on your own controls. Written report after.
| ||
20 | Detection Engineering: From Telemetry to Triage Document | ||
21 | Turn what an attacker must do into a signal, a rule and a calm triage. Watch Vera catch
persistence on a Linux server in her 3D lab, then triage a phishing report, take a timed drill
and write your own rules.
| ||
22 | A detection coding round with Marcus: flag logins that succeed after a burst of failures, test
the edge of the window, then adapt when the attacker spreads tries across many addresses.
Written report with a hire band after.
| ||
23 | Cloud and Containers Document | ||
24 | Find the setting, see how far one key reaches, and make the fix stick. Watch Vera work a bucket
that keeps going public in her 3D lab, then segment a cloud network yourself, take a timed drill
and write your own rules.
| ||
25 | A platform security round with Marcus: secure a Kubernetes environment that deploys through
Terraform, taken deep. Trace the path from a pod to the cloud account, layer build, deploy and
run controls, handle a leaked-state curveball, and make a call when your own control slows the
teams. Written report after.
| ||
26 | Supply Chain and Automation Document | ||
27 | Follow a poisoned dependency to where it lands, and give each path its own gate. Watch Vera work
it in her 3D lab, then walk an automation you built, take a timed drill on AI in a SOC and write
your own rules.
| ||
28 | A pipeline security round with Marcus: secure a CI/CD pipeline that deploys to production,
taken deep. Find every way code gets in, put the right gate on each, fix the credentials, handle
a compromised-plugin curveball, then make a call when your own gate slows an urgent fix.
Written report after.
| ||
29 | Vulnerabilities and Incidents Document | ||
30 | Turn a pile of scores into a fix order you can defend, and contain before you cure. Watch Vera
rank a fleet's findings in her 3D lab, then find vulnerable software on work laptops yourself,
take a timed drill and write your own rules.
| ||
31 | An incident response round with Marcus: stop ransomware spreading across a network, taken deep.
Ask for the timeline, contain in the right order, protect the backups, handle a curveball, then
make the call between isolating machines one by one and cutting a site off. Written report
after.
| ||
32 | Security System Design: Scope, Assets, Layers, Trade-offs Document | ||
33 | Scope a design, rank what you protect, and tie every control to a path. Watch Vera work one
system in her 3D lab, then harden a server yourself, take a timed drill and write your rules.
| ||
34 | A security design round with Marcus: a secure file-sharing platform for enterprise clients,
taken deep. Scope it, rank what you protect, trace how a file leaks, layer controls with
detection, handle a bank's "you must never read our files", and make a call when your sharing
rules cost clients. Written report after.
| ||
35 | Security Design: Identity, Data and Detection Document | ||
36 | Design identity, data protection and detection the way a strong candidate does. Watch Vera work
one system in her 3D lab, then place the keys yourself, take a timed drill and write your rules.
| ||
37 | A security design round with Marcus: a secret management service like Vault, taken deep. Solve
the first secret, protect the root key, scope who reads what, plan the leak and the outage, and
make a call when your controls slow every deploy. Written report after.
| ||
38 | The Take-Home Case: Seven Steps and the Readout Document | ||
39 | Work a security take-home the way reviewers score it: assumptions, threats ranked, a plan with
what waits, and a readout that leads with the decision. Watch Vera, rank risks yourself, then
explain a finding to a VP.
| ||
40 | A take-home readout with Marcus: hear a made-up case, structure your readout live, lead with
the decision, defend your order and your mechanisms, re-plan for a six-week deadline, then
convince a VP of Product who doesn't speak security. Written report after.
| ||
41 | Behavioral: Security Stories That Hold Up Document | ||
42 | Tell security stories that survive five follow-ups. Watch Vera rebuild one story in her 3D lab,
then shape your own mistake story, take a two-minute drill and write your rules.
| ||
43 | A behavioral round with Marcus: one real incident you worked, dug several layers deep, a
push-back on the call you made, then two short stories about a disagreement and hard feedback.
Your stories, your decisions. Written report after.
| ||
44 | Company Rooms: What Each Security Round Weighs Document | ||
45 | A two-part round with Marcus, built from questions reported for Microsoft: cut alert fatigue in a
company-wide security operations centre, then write a Python beacon finder over connection logs and
test it. A trade-off built from your own answers closes the round. Written report after.
| ||
46 | A three-question technical round with Marcus, built from questions reported for Google: one common
attack and its defenses, Windows persistence and how you'd find it, then how you categorise risk.
A trade-off built from your own control closes the round. Written report after.
| ||
47 | A network deep dive and one story with Marcus, built from questions reported for Amazon: secure a
made-up company's enterprise network, make the call when your first control hurts the warehouse,
then a decision you made without enough customer data. Written report after.
| ||
48 | A security design round with Marcus, built from a question reported for Meta: design security for a
payments platform like Stripe. Scope it, trace how money leaves, layer and price controls, handle a
curveball, then make the call when your first control costs merchants. Written report after.
| ||
49 | Three quick cards: tap the way in, then say the whole attack path in sixty seconds. Vera scores
it on screen, gives one strength, one gap and the move that fixes it, and you retry. About eight
minutes.
| ||
50 | Three quick cards: tap where a protocol turns, then explain how it works underneath in sixty
seconds. Vera scores it on screen, gives one strength, one gap and the move that fixes it, and
you retry. About eight minutes.
| ||
51 | Three quick cards: pick the one fix that stops an attack, then layer prevent, detect and respond
with their costs in sixty seconds. Vera scores it on screen and you retry the gap. About eight
minutes.
| ||
52 | Three quick boards: tap what you fix first, then give the order, the reasons and what waits in
forty-five seconds. Vera scores it on screen and you retry the gap. About eight minutes.
| ||
53 | Three quick cards: pick the first line that lands with a VP, then say the rest in forty-five
seconds. Vera scores it on screen, gives one strength, one gap and the move that fixes it, and
you retry. About eight minutes.
| ||
54 | The Full Loop: Four Rounds in Forty-Five Minutes Document | ||
55 | The whole loop in one sitting: a firewall question, a sign-in design for millions of members, a
story, and a VP who wants your own control rolled back. Forty-five minutes with Marcus, one report
with a hire band after.
| ||
56 | Take this at the end of the course. Twenty minutes with Marcus, new questions in the same shape
as your first diagnostic: TCP/IP, a suspicious Windows process, two findings to rank and explain
to a VP. Your report compares your five signals with the first time.
| ||