I've interviewed tens of people this year for #infosec jobs. Some tips for the technical side if things: 🧵
1. Your resume matters. If you write you have malware reversing experience, you will probably be asked to explain a short assembly blurb or TTPs that malware might use.
2. Don't write things in your resume that you don't really know. If you have 5 yoe in binary reversing, I'm expecting you to know certain things like the difference between cdecl and stdcall.
3. If you get a question you don't know, it's okay to say you don't know. In that case I will either move to a different subject or ask you to make educated guesses and explain yoyr reasoning.
4. I usually don't care about the bits and bytes (things you can Google). For example, it's okay to not remember exactly how TLS works, but explaining how authentication is achieved is key.
5. Knowing the bits and bytes does show me you have experience (e.g. what's gs[0x60] on Windows userland).
6. For coding, I will usually let you choose the language! But you are expected to know how to translate a simple idea to code, in many cases without relying on external libraries to do heavyweight lifting for you.
7. Communication is important. Try to be clear, verbose and avoid vague terms. Ask questions if something is not clear.
8. I usually looks for a good combination of experience and liquid intelligence. This simulates the mindset of an infosec professional in my opinion. Come prepared, well-rested and open minded.
9. One bad interview does not mean you will not be hired... But try to learn from that bad experience. Even if you weren't hired, you can always try again in the future. Don't give up.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
