-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What are some good tips for interviewing? #9
Comments
Good one! Want to own it? |
Yes please!!! |
Assigned! |
Hey tweedge - I'm not really sure how to do this. I typed up the content in a document, but not sure where to put it. I clicked the Fork button, but don't know where to paste my content. |
In your repository here, click the top right button "Add file" (next to the green button 'code'). That'll open a dropdown. Then 'create new file' - paste your content in there, set the file name, and click the green 'commit' at the bottom. Should work great - let me know if you get stuck! |
Hey @eric16lee - changed the contribution guide, just post your content here please and I'll review. No need for git anything :P |
Oh thank goodness!! I've never used GIT before. I was going to sit down
today and look into your directions, but this makes it much easier. Below
is the content that I wrote up for this tip:
What are some good interview tips?
First things first…… Everyone is really bad at interviewing at first. Don't
focus on that. Being comfortable while interviewing takes practice. The
most important thing you can do is be yourself. You don’t want to sell
yourself as one person and then be a completely different person once you
join the company.
The main thing that helped me throughout my career was to write up a
summary of your experience and what you are looking to do. Refine it and
get it just right. Share it with someone and get feedback to improve it.
It doesn't need to be fancy, but it does have to be comfortable for you to
say. Once you have it where you want it, practice it. Over and over, and
over again. Get to the point where you say it so naturally that you wind
up saying it a little differently each time. You can change it as often as
you like until this becomes second nature for you to say.
Many interviewers will ask you to tell them about yourself. This is the
time to naturally go over what you wrote.
For example:
Interviewer - thanks for coming in eric16lee. We've read your resume, so
why don't you tell us about yourself and why you applied for this role.
eric16lee - “sure, happy to.. After high school, I went to college, but
didn’t know exactly what I wanted to do. I took a bunch of classes and
eventually found out that I really enjoyed IT. I started my career in that
field and really learned a lot about technology and how things work. Over
time, I found myself fixing virus infected PCs and dealing with people
getting phishing E-Mails. This really got me interested and so I decided
that I wanted to change directions and find a job that focused on
preventing these types of things. That is when I found that I had a lot of
passion for cybersecurity. Over the last 5 years, I worked in a few
different roles that taught me a lot about security. I decided that I
wanted to learn more, so I started to self study and was able to pass my
Security+ certification. I did it the old fashioned way by reading the 500
page book and taking practice tests online until I was confident I would
pass the exam..
I really enjoy learning the different areas of cybersecurity. I decided to
apply for this role because it sounds like a great place to apply my
experience while learning some new things along the way.”
Obviously, that's just a snippet of what you could say, but I hope it got
you thinking. Some other content to consider adding to your summary:
- are you planning on taking any other certs? If so, start studying online
so you can say that you are currently studying for Network+, CySA, etc.
- have you done anything else in your life such as military or the Boy
Scouts where you would have grown leadership skills?
Make this a priority. It will be a valuable tool in your career search.
Other than that, think through any of the responsibilities that you had in
previous jobs and how they may have contributed to cybersecurity. Did you
add/remove access (least privilege)? Did you handle any helpdesk calls for
phishing, virus, etc.? These are all points to mention in the interview.
Most of all….. Relax. Be yourself.. And Good Luck!
…--
Eric
On Mon, Jul 26, 2021 at 1:47 AM r-cybersecurity/faq - reply+au46wsz2zzj5swy3dejrcqf7biwxvevbnhhdrbay2a at reply.github.com < ***@***.***> wrote:
Hey @eric16lee <https://github.com/eric16lee> - changed the contribution
guide, just post your content here please and I'll review. No need for git
anything :P
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU46WS7AXFO7RUYMABXUEXLTZTZHVANCNFSM5AU2N2OQ>
.
|
No description provided.
The text was updated successfully, but these errors were encountered: