Everybody and welcome to next video we're gonna be going over prepping for the technical interview.
Now in this video I'm not gonna be going over what questions you should be looking at but I'm gonna
show you how to gauge what questions may potentially be asked.
Now the first thing I want to say is everything on your resumé and everything in the job description
is probably going to be talked about in some way shape or form by everybody between now and the onsite
and including the onsite.
Now there's technical screening is normally done by the hiring manager so they normally ask some sort
of behavioral questions which will go over in the next video but just understand that it's going to
be technical and culture type type interview.
And normally they have another engineer on the call as well but sometimes it's just a hiring manager
and most hiring managers at least what I've experienced in this field tend to be very technical as well.
So don't be fooled by the manager title there.
So you don't want to start prepping for this.
Now some companies will use a coding interview or some sort of hands on interview by this point for
this first step.
And the recruiter will tell you this if they don't ask.
The last thing you want to do is be sitting there waiting for somebody to pop onto a video chat and
they pop on a video chat and now they're asking you to code and you have no idea what language they're
going to ask you to code because they recruiter didn't ask you in that case the recruiter kind of failed
on their part but you always want to double check.
And if a recruiter asks you what language you prefer to use give them the language you are most proficient
with one that you could go and start writing something off the top of your head and make sure that you're
able to do that such as Python.
Don't try to do assembly or anything like that.
They're going to ask you more complicated stuff that you might not be able to do in assembly go with
the language that you're more familiar with.
That's easy to work with and stick with it because that's going to be the language that they're going
to tell the hiring team about.
So when they ask you anything related to code it's probably going to be done in whatever language you
specify.
Now with that in place you should by this point have looked up the salary requirements you've looked
up stuff in the company of ask the recruiter about questions about the team.
Now it's time to prep questions around the more questions around the team specifically because you're
going to be talking with the team this time the hiring manager is going to be your manager in the future.
In most cases unless there's somebody else had to step in.
But she's probably going to be your manager.
So ask about the team.
Ask about the responsibilities that they expect about the job.
What expectations do they have for for you as an individual.
What are the hours that they team typically works.
What are their opinions on the company are kind of about the team teams as its own and in some cases
the recruiter will tell you the name of the person you're talking going to be talking to look them up
on LinkedIn and look at their history their their history that they have on their profile.
Ask them questions about why they left X and Y maybe or what kind of a little bit more about try to
figure out more about them because it's important to know that you are interviewing them as much as
you are they are you.
So now you've kind of got all that stuff up you got your questions lined up the next thing women want
to do is look at potential interview questions.
Now what I want to say before we go into Glassdoor a little bit more is that looking at these interview
questions you're not guaranteed to get the same question as in it's highly unlikely to get the same
question but you may get variations of of the similar question you might get new questions entirely
which is probably going to be the case.
But it gives you a general ballpark of what you should expect.
So the first thing I really want to do is go to Glassdoor security engineer interview questions.
This is very vague and I'm doing that on purpose.
But you can see Amazon Google Facebook security engineer you can specify this down to a company and
look at just those individual people.
But what you can see here is describe the descent plain symmetric and asymmetric encryption what scenario
is the more appropriate what anomalies are you looking for to identify a compromised system.
What about what is sequin Jackson cross scripting what tools we have to use function that determines
turn determines and input power input is the number of a power of two which is a coding question.
So keep that in mind for security engineer at Google you might be asked a coding question.
I tend to find that Google and Facebook are very code heavy when it comes to that.
I believe this I believe somebody told me that they everybody in the company that is an engineer should
be able to write code at a highlight a pretty good level.
So will explain trace route in detail so you can see that you start building up generic answers that
people are going to be asking.
So just keep going down a little bit in this in this case it tells you different companies which is
a good way to kind of gauge everything it was CSR f.
How's the SSL handshake work.
If you're a company works with oh awful lot you're going to want to know how that works.
Let's see here.
Question What port does LDA app.
So knowing some common ports that that specific services on like DNS HDP knowing those off the top of
your head is a good way to just kind of get that out of the way so keep going here.
VIP concepts.
It's good to know how that works.
What's volatile what's static.
It's good to know how that how that would kind of work.
So well what's basic threat modeling so you see here you can start building up a really big list of
questions that you could potentially be asked and as long as you're able to go through the chunk of
these and be able to have an answer to most of them you should relatively be ready for what they're
going to ask you.
But when you start getting into specific companies that's when you start realizing what so are questions
that they engage.
And that's kind of the important part is you want to look at it from the broad stroke for your path
or your title.
In this case security in your offensive security engineer.
Actually I don't even know if this is going to show up
on authors to many titles.
Yes so it's such a new keyword here that it's not even going to show up with the offensive security
engineer but security engineer tends to be what the back end title is for most of these companies.
So give that a mom take a broad stroke at it look and see what questions are being asked if you don't
know the answer to one look for the answer.
Read it.
So if you don't know it's volatile and static is read it.
Let's see here.
How would it affect a static keyboard used for a big array inside of function.
So you can probably google that exact question and get your answer and make sure you understand why
the answer is the way it is.
It's not just the answer because a lot of questions especially on the technical side or specifically
on the offensive side of security you're going to have more open ended questions rather than specific
answers like what is Port X what is Port y that's when you find those type of questions with normal
one word answers or maybe a paragraph answer on standard security engineer titles.
But when you start getting specialized such as you know if you're on an infrastructure team you're going
to start specializing and you're going to get more scenario based questions.
So it's not just offensive.
But anybody that specialized in this area of security that their job is so focused on one particular
type of area you're going to find more and more detailed questions on on open ended versions of those
questions such as like what would you do in this situation.
It's going to be more of a question and answer type thing which will go over in the next video.
But there's one last tip that I want to leave you guys with is to make sure that anything on your resumé
you can speak to it in as much detail as you possibly can.
Don't put something on your resume to fluff it up if you can't talk to it.
So don't put that you know ARP at the packet level and somebody starts asking you what the offset is
inside of the packet.
And you can't answer the question you don't want to be in that situation.
So make sure anything on your resume.
You can speak to in complete detail because you never know how far somebody is going to dig down the
rabbit hole when they ask you a specific question.
I've had interviews where somebody asked me one question about something specific or I think it was
exploit development on my resume I went down to buffer overflows and it went into restricted show code
jump outs and then we moved into SCA exploits and then he sprang.
So you can go really deep really really quickly when you start going through the interview process and
there's times where somebody will just talk about that one topic all the way down as deep as you can
and then not even ask you any more questions they might have had 30 lined up but every interview can
be slightly different.
Make sure whatever you can you speak to what you can as much as you can if it's on your resume specifically.