NASA interview notes, page 1 of 2

“I went with the public-facing server first because external exposure felt like the most obvious attack surface.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The query part I was fine with, window functions over a timestamp column grouped by IP, flag anything above a threshold.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Knew the basics but fumbled explaining the 'persistent' part clearly.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty standard for any security role.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Ran through the usual signals: sender address mismatches, suspicious links, urgency language, unexpected attachments.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Knew this one cold.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with auth logs and worked outward, endpoint telemetry, network flow data, threat intel feeds, maybe identity provider logs if it's SSO.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I blanked for a second because I had like five answers and couldn't pick one.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew what EDR killers were conceptually but stumbled a bit connecting it to a concrete investigation flow in Sentinel specifically.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with DNS resolution and worked my way through TCP handshake, TLS negotiation, HTTP request and response, rendering.” The rest of the author's notes on Software Engineer interview at NASA, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.