0% found this document useful (0 votes)
17 views7 pages

Technical Interview Oreintation For Freshers

The document provides a comprehensive guide for freshers preparing for technical interviews, emphasizing the importance of understanding fundamental concepts in computer science, familiarizing oneself with the interview format, and practicing problem-solving skills. It also highlights the significance of behavioral questions and suggests using the STAR method to structure responses. Additionally, it offers tips on showcasing passion for technology and preparing for a potentially lengthy interview process.

Uploaded by

m43829824
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views7 pages

Technical Interview Oreintation For Freshers

The document provides a comprehensive guide for freshers preparing for technical interviews, emphasizing the importance of understanding fundamental concepts in computer science, familiarizing oneself with the interview format, and practicing problem-solving skills. It also highlights the significance of behavioral questions and suggests using the STAR method to structure responses. Additionally, it offers tips on showcasing passion for technology and preparing for a potentially lengthy interview process.

Uploaded by

m43829824
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Technical Interview Orientation for freshers

1.How do you prepare for a technical interview as a fresher?


➔ Prepare for a Software or Technical Interview
➔ Create a PowerPoint presentation on a tech topic.
➔ Write code in real-time and/or do an on-the-spot coding test.
➔ Complete a technical problem in a group and present to a panel.
➔ Work out a tech problem on a whiteboard in front of a group.

2.How to Prepare?
LOCK IN THE FUNDAMENTALS
In addition to more traditional behavioral questions, a technical interview
will cover your knowledge of computer science.
Depending on the job , this could be coding, data structures, algorithms,
systems design, big O notation, etc. Refer to your coursework to refresh
your memory on the basics.

FAMILIARIZE YOURSELF WITH THE FORMAT AND TYPES OF


QUESTIONS
First, if the recruiter has sent you material on preparing for the interview, be
sure to review it closely. Also, check to see if the company has interview
prep information on its website.

Note: If you are not sure of the format, ask the recruiter.

Questions will focus on the types of skills you’ll be using on the job.
They can range from the core fundamentals to higher-level principles.
Many technical questions are based on your own experience during the
training and internship.
Eg:
➔ Did you create a game for a class project and put it on your
resume?
➔ Be ready to talk about your technical tasks, challenges, and
contributions.

Although some companies are entirely removing them from their interview
process, you might receive a brainteaser during technical interviews.
These questions assess your problem-solving abilities, comfort with
ambiguity, and quantitative skills.
Share your thought process and problem-solving approach out loud, and
try to enjoy the challenge.

3. HOW TO PRACTICE ?
Most interviewers want to hear you explain your thought process while
working through a problem.
This gives them insight into your personality, problem-solving skills, and
ability to work under pressure.

There are many ways you can practice doing this:

➔ Ask a friend with a technical background to act as your mock


interviewer.
➔ Practicing and explaining out loud is a great way to prepare and build
confidence.
➔ Get involved in competitive programming and hackathons and make
open-source contributions.
➔ Be prepared to thoroughly explain any technical projects listed on
your resume.
Interview Tips
DON’T DWELL ON MISTAKES
➔ Be comfortable asking questions and asking for clarification.
➔ If you make a mistake, don’t let it affect the rest of the interview.
➔ You’ll have the opportunity to answer many questions and the
interviewer will often forgive a single mistake.
➔ When something goes wrong, move on and focus on the rest of the
interview.
➔ If you don’t know the answer to a particular question, just be honest
about it.
➔ Try to engage the interviewer so you can learn more about the topic
and/or explain where you could find the answer.

USE THE INTERVIEW TO SHOW YOUR PASSION FOR TECH


By demonstrating your passion for coding and creating new programs, you
are also showing why you are the right candidate for the position.
Related extracurricular activities are a great way to show this passion.
“The number one thing I look at on resumes is extra-curricular activities,”
says former Google engineer Paul Tyma in a blog post. He adds, “I want to
hire engineers that I want to work with. And those engineers are passionate
about cool algorithms, slick code, and new ideas. They do that stuff in their
spare time—it’s not just a job, it’s what they do because they love it.”

BE PREPARED FOR A LENGTHY INTERVIEW PROCESS


The tech interview process may take several weeks and involve multiple
interviews.
(Recruiters will often clarify this process in advance.) After the initial phone
screening, you might meet with engineers and managers in the days or
weeks to come.

DON’T FORGET TO PREPARE FOR TRADITIONAL/BEHAVIORAL


QUESTIONS
Employers often say that students are so concerned about the technical
interview that they haven’t thought through answers to common questions
like “Tell me about yourself?” or “Why are you interested in this job?”
What’s a Behavioral Interview Question?
➔ Behavioral interview questions are questions based on how you
acted in a specific situation.
➔ They’re meant to gauge how you react to stress, what’s your
skill-level, and how you conduct yourself in a professional
environment.

➔ They also allow the interviewer to get a much better understanding of


you as a candidate.

➔ Just about anyone can answer a question like “what’s your greatest
strength?”

➔ Not everyone, however, can answer a question like:


“Can you tell us of a time when you went above and beyond the line of
duty?”

Here are a few other popular examples of behavioral job interview


questions:

➔ Give us an example of a goal you failed to meet, and how you


handled the situation.
➔ Tell us about a time when you solved a problem at your job that
wasn’t part of your job description.
➔ Tell us of a time when you took a risky decision and it didn’t pay off.

The easiest way to answer behavioral interview questions is to


follow the STAR method.
According to the STAR method, each interview answer should
use the following structure:

S for Situation. Describe the situation where everything


happened.
T for Task. Describe the task you had to complete in order to
solve the problem/issue at hand.
A for Action. Explain what actions you took to complete the
aforementioned task.
R for Results. Talk about the results of your actions and try to be
as detailed as possible. How did your actions lead to the
company or organization to function better?

Now, here’s what a good answer looks like according to the


STAR method:
STAR Method Interview Answer

Q: Give us an example of how you handled a challenge in the


workplace.

Situation: Around the time I started working at Company X, the


team I was working with was just finishing up on a very
important project on a tight deadline. They had to review
everything before submitting the work to the client, and my
manager didn’t have a lot of time to pay attention to me to make
sure I was caught up to speed.

Task: Everyone around me was constantly working, and


because of the timing, they didn’t seem very approachable. So,
to make sure I didn’t get left behind, I had to prove myself and
take initiative.

Action: My plan was simple. I wanted to talk to my manager and


a few of my colleagues whenever they had time (e.g. over lunch,
getting coffee together). Then, I would try to get to know them in
a different environment and also learn about the company better
too. In the meanwhile, I would always go over my onboarding
material and resources to get better at my job.

Results: In the end, I’m glad to say everything worked out and I
actually made a few good friends too. By the time my manager
came around to review my work and talk about the next steps - I
already knew most of it and the company’s main clients in detail.
And I also knew my colleagues who I’d be working with too. If
anything, he was a bit surprised, but ultimately, happy I didn’t
fall behind. This saved him a lot of time, something he was very
grateful for.

Other Basic questions to ask in interviews


Listed below are a few of the most commonly asked questions
you can include in your interview.

➔ Do you have any technical certifications?


➔ How many programming languages do you know?
➔ What are the different types of OS you are comfortable working with?
➔ What is the extent of your technical expertise?
➔ How many development tools have you used?
➔ What do you do to improve your technical skills?
➔ What are the technical websites you follow?
➔ Why is a solution design document important?
➔ Have you used any source code tools? If yes, explain them.
➔ What do you like most about the IT industry? What do you enjoy the
least about it?
➔ Give an example of how you apply your technical knowledge in a
practical way?
➔ If you have to change your career path, what job would you prefer?
➔ Whenever you solve a problem, who do you keep in mind? The
end-user, the business, or yourself, and why?
➔ What is the importance of learning on the job, and how do you learn
new technologies?
➔ Do you reuse code? If yes, how do you do it efficiently?
➔ How do you ensure the quality of your deliverables?
➔ Which technical skill do you wish to possess?
➔ What was the recent technical project you worked on? What were
your key responsibilities?
➔ What is the production deployment process you follow?
➔ How will you use your technical knowledge/expertise to perform this
job if you are selected?

You might also like