Blog - Inside The Tech Interview

Technical Interview Questions: What to know?

You just passed your school exams with Computer Science or a Bachelors Degree in Technology and deeply waiting for the results and thinking of what’s next? Shall you head towards further advanced studies or a job that you have been dreaming about? Your dream job might not come easy given your technical qualifications or even with higher grades they don’t come easy but you have to plan hard, plan perfect and plan strategically. Facing the technical interview questions round after round needs some very good homework and aptitudes.

The following things are a must in order to crack the interview rounds as gathered from experience.

What are the technical questions that you think you are weak on? Is it the Algorithmic Structure or any specific programming language ( Java, Php, ASP, C#, Python DataScience etc.) or the Database Concepts with its normalizations?
Once sorted you can work on them by gathering different study materials and concepts or the internet for those specifics.
Basic Programming Logic related questions- A very common thing on the technical interview rounds are based on the questions related to loops, logical structures, switch cases etc. So, you must learn them by heart and practice basic programming logic related questions.
Server Side or Client Side- If you are applying for the role of a developer you need to know both about the Client and Server Side mechanisms. If you are more of the graphics or design person then you need to master markup languages and client-side mechanisms like HTML, CSS, and Javascript. Stay updated with most important questions.
Database Concepts – You need to learn about the database and its key concepts, normalization techniques and procedures, their dimensions and compatibility.You already know about SQL and genuinely prepare yourself to it so no more suggestions here. Nowadays MySql is quite famous and mostly used. But side by side you can learn Oracle, Microsoft SQL Server, SQLite, MongoDB etc. If you are applying for an administrator role you need to be more concrete with questions.
Operating Systems – You will be confronted with basic OS related concepts like kernel, thread and its operations, process. procedures, pipelines, user permissions, etc etc.Generally Linux and Windows are the benchmarks here. Also, you should have an idea of computing a few programs here.Furthermore, mobile applications have presented the world with Android, iOS Operating system ideas as well. So, a basic idea on those will help you a lot.
Data Structures & Algorithms – The final frontier, is a MUST have for all the exams on technical grounds. Concepts of Sorting, Binary Trees, Search, List, Array etc. This is the most feared section of all the technical interview questions faced during the technical interview rounds.
Mathematical Concepts – Core to the core you can’t leave it out. This stands as the root of all the things explained above.Must learn Math related functions and its usage ( which is almost similar to all of the programs ).
What do you know about the company or the role which you are applying for? It is very important that you know about the company you are applying for and the role in which you are interested in unless you have been directly recruited by your college/school.
Why are you interested in that very role and why they are going to take you in their company? These are not technical but very common aptitude related questions that you are going to confront.

Finally, you should consider some good books to learn from, some guides which will help you to strategize your career building. Following are some references for some in order to boost up your mindset-

Data Structures and Algorithms- http://amzn.to/2uspL0t

Operating System Concepts – http://amzn.to/2tiYK0K

Fundamentals of Database Systems – http://amzn.to/2us3U9p

Inside The Tech Interview – http://amzn.to/2nFhQMs

7 Ways To Prepare The Day Before The Tech Interview

Before anything else you should equip yourself before the day of the Tech Interview:

Take time to Read The Company/Employer’s website Back to Front, Upside Down, In All the Niches and Crevices

You should devote as much time on it as you do on Facebook in 1 week. Follow all the links of the company, who are they relating with, what are they speaking about, what ventures are they functioning on?

If you find out that they have a blog, read it, what are they talking about? What are they involved with? What are their ideas?

You may stalk their Tweets, Facebook updates, Linkedin status – probably what are they saying on social media?

Add them, Follow them, and like their posts.

Look for five things that interest you. So when the day of the interview is in, and when you find out that it’s appropriate, you may share about what you found out on their website. And Say you stumble on it. Can the information you knew be turned into questions? See tip #2!

You Should Prepare Questions

Get to make 5 of them at the minimum. Remember not about the salary one or the holidays.

Ready the job description, personal requirement or any other material you have and look if you can discover something in those to write extremely, awesome questions.

Also, think like you are the interviewer. What would you be asked about the tech interview?

Now go back to the job description or personal requirement and ask yourself, what difficulties are they trying to resolve with this position?

Make an Ocular Inspection Where the Interview Is Being Held (if you can)

Without looking like a creepy stalker, get a feel for the building (if you can get in). Check out the ambience.

Where the employees are going for lunch break and coffee? Get a real sense of the place.

Try this: make pals with the reception department. You may tell them you are coming for an interview and want to get a feel for the place. You can ask what their interview was like, they’ll tell you.

Envision The Initial, Middle and End of the Interview

Contemplate of all the things that may put you of your step: a handshake, a not so friendly smile, stares from the interview panel?

See them as they are occuring and then make yourself ‘mentally’ prepared of how you will successfully manage and respond. Then, see yourself after the interview, get a picture and feeling of how you are going to leave. Play it over and over again.

Prepare Answers for Your Awkward Questions Ahead

Some of may say ‘what if they ask me about that’, usually they’re referring to a gap, perhaps a role that didn’t last because they hated it, or a personal time in their life that they aren’t comfortable talking about.

You need to be prepared. If you have any nervousness over what you might be asked, you can get ready for it.

Contemplate on questions you don’t want to be asked and ready your answers. Play them in your mind. Make sure your reply is honest, yet still would have no reflection on the role you are applying for. It won’t will it? There is no question that you cannot answer!

Most probably you have a few ‘personal’ toughies that aren’t covered anywhere online! Ask someone to listen to your response to your awkward question, and ask to give you feedback on your response.

Get A Mock Interview

If you can afford it hire a career coach to run through a mock interview with you, then do it. If you’re low paid or not working at the moment, do a little research and look for organizations in your local area who provide that offer services (start with your local volunteer group).

Mock interviews are a great opportunity to iron out any sticky points, plus get feedback on presentation skills, how you came across, what did an answer sound like, was it good enough, did you say enough etc. A decent ‘mock interview’ will feel like the real deal.

Imagine that You’re Nearly There

About those anxieties, you’ve earned the right to be there, please remember that.

The company want to meet you, think on that for a subsequently. They already think that you might be suitable for the role, they came to this conclusion through your CV or Application Form (however you got in the door). So you’re half way there.

If you believe what you wrote, then you know that you only have to live up to what you said.

Yes, you’ll probably have rivalry. And that’s good, right? If you were interviewing you want to have a choice, wouldn’t you?

Write a list of your key strengths before your interview. When they ask you ‘do you have any questions’ (which they will), it’s perfectly fine to say ‘I just wanted to leave you with a few of my strengths and where you could use them‘ and tell them.

The first impression is mega necessary, the lasting impression is the one that sticks.

Guidance and preparation is key, so grab a copy of Mike Reinhardt’s book, “Inside the Tech Interview“.

5 Ways To Crack Any Tech Interview

emotional man listening his inner voice over grey background

5 ways to crack any tech interview

There are a number of articles in the web which tells about how to crack administrative, cultural & HR interviews. Hence, we know very well about how to answer the questions like

Where do you want to be after 5 years?
What is your greatest weakness?
and many other common questions.

As a technical person you will come across different questions as a measurement of how technically sound you are. Even if you are well prepared, it is still difficult to move ahead in technical interviews.

During the technical interview many programmers make basic mistakes that hurt their chances of getting hired. Some of those mistakes are listed here:

Using incorrect jargon or terminology. Correct nomenclature shows you know the topic.
Bullshitting when you don’t know the answer to a technical question.
Not knowing programming languages you put on your resume.
Not being able to convey the design aspects of complex problems.

In a software interview, you may respond when you don’t know something with: “I don’t know the answer, but I am ready to learn provided the opportunity.” Be honest in your interviews and accept where you don’t have knowledge. It will show you are honest and are willing to learn from other team members when your experience is lacking.

Ways to crack technical interview:

Regardless of your technical role, be very strong in the basics of the programming languages you list on your resume. Know them in detail if you claim expertise.
Be prepared to say when you don’t know something. Interviewers are not measuring you with the correct answers that you provided alone, they are also measuring you based on how open you are to learn new opportunities.
Be definite on your answers. Do not embellish when a simple answer will suffice.
Do not beat around the bush. Responding with immaterial answers or asking question that do not make sense will make the interviewer assume you don’t know what you are talking about. If you don’t know just say so, and ask questions showing you are willing to learn.
Take your time giving answers. Your initial response may not be appropriate or may be wrong. If you take your time you may recollect the correct answer.

Being like a salesman is acceptable during technical interviews but these interviews are not always about the syntax of a function or whether your answers are correct. It is always about what you know and how open are you about learning new technologies and concepts and how you can contribute to the organization.

This will help you to crack the technical interviews, for more ideas and information, Get Michael Reinhardt’s book, “Inside the Tech Interview”.

10 Tech Interview Mistakes

Know the mistakes during tech interview and avoid it.

As an interview you went to the company on time, the job description is a seamless match and one stare at the workplace tells you this is the right job for you. So what can go wrong?

Many!

Everyone makes inaccuracies. Hence conferring to those who do the interview, job hunters for tech positions are inclined to to a number of common interview gaffes. Know how to avoid those, it helps to distinguish what they are. These are 10 of the most common.

Presence

Tech people oftentimes dress “from the waist up”. They’ve got “wrinkled khakis and rubber-soled shoes” — not exactly the image they should be projecting.
Remember this, the days when you would not be considered because you [were] dressed too conservatively are over.

Overconfidence

A quite number of tech people come transversely as arrogant in interview. True enough that techies are very talented, but what comes out is arrogance.

Confidence is desired, not arrogance. Arrogance proposes “they can’t be a team player.”

Not Collaborating or Communicating

There are times when interviewers often indulge to open-ended questions, but techies sometimes reply with too-brief answers, failing to elaborate or deliver their communication skills.

Tech professionals should think of each question as an initial way to a conversation. A simple “yes,” is never an appropriate answer to the question. Candidates must see questions as an chance to discuss the worth they will bring to a company.

A person who is unwilling to communicate and collaborate will have a hard time working in a team environment.

Exaggerating Skills

It is noted that certifications and other credentials matter, plus your technical know-how, but take note: You’re around to function an organization’s necessities, not to emphasize on Cisco or J2EE just for the sake of the technology itself. You need to come across as more than an mixture of your expertise.

Sometimes tech people exaggerate their skills.

Unprepared

Now that we have a vast technology and with all the information available, there is no excuse for someone not being equipped for an interview.

Being ready and prepared does not mean passing knowledge about a company, but rather in-depth research about the firm and its industry.

Lack of Interest

Tech people sometimes show a lack of interest by not asking about the company’s industry, competitors or “the larger business problems” facing the firm.

Quite often, this comes through when candidates are asked if they have any questions. Never say no. It just shows that candidates are not interested, or they’re not prepared.

Too Casual

Interviews can be formal matters. The interviewer, not the candidate, should set the tone. Tech pros tend to be a little casual in the interview. This may come through as a lack of significance, or even a lack of interest in the job.

Too Impatient for Perks

Queries about parking spaces, sick days, free coffee or soft drinks, and other benefits and perks should be reserved for a human resources department, preferably after a job offer. Remember this techies: Stay away from what’s-in-it-for-me questions.

Too Negative

Several tech professionals smarting from rough times — failed startups, corporate layoffs and the like — may mistake an interviewer’s friendly bearing as an invitation to confide. This focus on “the highest highs to the lowest lows” is not proper during an interview. Candidates use interviews as therapy sessions and it is not appropriate.

Failure to Close

Tech candidates every so often fail to close the interview. Rather than emphasizing how much they would love to join the company or asking what the next step in the process will be, techies may let the interview “fade out”. They’re not closing or they’re not selling themselves.

Consider getting the book, “Inside the Tech Interview” today and be guided. Available on Amazon in paperback and Kindle.

7 (Really Hard) Tech Interview Questions You Must Answer Appropriately

Human Resources Interview Recruitment Job Concept

Getting into the tech interview is hard enough. Don’t blow your chances by saying the wrong thing.

Going for an interview isn’t easy. The employer is the consumer and you’re the business-of-one trying to show you’re the best service provider for the job they are offering. Studies reveal that it costs a company as much as 130-140 percent of your wage to hire you which includes things like benefits, taxes, training, etc. The pressure of choosing the right candidate worries hiring managers. A series of intense interview questions designed to let them “kick the tires and look under the hood” before they invest.

Behavioral questions = Get them inside your brain.

Hiring managers often use behavioral questions in a tech interview with an attempt to have you reveal your genuine professional self. Mostly these are open-ended questions designed to make you give lengthier answers. Your replies will validate your personality, aptitude, and experience level. Which of course these 3 things matter greatly to employers who choose a candidate grounded on his or her ability to fit in with the company’s philosophy.

Below are 7 intense tech interview questions you should always be ready to answer appropriately.

What’s wrong with your past/current employer?

This seeks to understand what’s driving you to leave your former job. Contented employees don’t go on interviews for new jobs. The recruiter or hiring manager is trying to see if you have improbable expectations of employers.

Tell me about the worst manager you ever had?

Once more, seeking to comprehend your expectations, the recruiter or hiring manager may want to identify what kind of administration style you don’t work well with–especially if it’s a style the hiring company presently is using

What’s the worst job you ever had?

The recruiter or hiring manager wants to know what type of work separates you. He or she also wants to recognize what (if any) efforts you made to resolve a problem. When unhappy, are you proactive and try to resolve the circumstance in a certain situation, or do you sit around and get discontented?

Why are you better than anyone else for this job?

This may be a test to see if you can balance self-confidence with meekness, this is intended to see if you have an understanding of reality and can communicate how you are different from the struggle without resorting to “throw them under the bus” schemes.

Why were you fired?

These are for those that have been obligatorily terminated, you need to factually share what happened and be responsible for your actions. If you resort to imputing and explaining your way out of any wrongdoing, you’ll be dismissed as in denial.

What are your weaknesses?

Nobody is perfect. You should discuss your areas in need of improvement, then you aren’t self-aware enough to grow on the job. If you can not clarify how you are already trying to decrease these weaknesses, then you are showing a deficiency of understanding about the necessity to always be cultivating as a professional.

Tell me about a time when you had to work with a difficult person?

This question may get to the core of what you are like to work with. The hiring manager wishes to know what type of co-worker you struggle to cooperate with and whether you know how to find a way to work together successfully with that type. You will be paid to do a job, and that means getting along with all types of people, even ones who don’t work like you do.

Hiring managers hear what they see.

A mere reason why hiring manager asks intense tech interview questions is not to calculate your answers, but to evaluate your non-verbal communication skills which your body language, facial expressions, hand gestures, eye contact, etc.

Hiring managers are trained well and can convey when someone is acting nervous or deceitfully. So it is important why every candidate should work on their interview answers as much as they can before they go to the interview day. It will help you relax and communicate with more confidence.

For more tech interview techniques get the book, Ïnside the Tech interview”, on Amazon.

Top 10 Tips for Acing Your Next Tech Interview

Young man in casual sitting on floor and looking at media photos

Here’s what you need to know about nailing your tech interview so you can get through it stress-free. Following are the top 10 tips for acing your next interview:

Get the Interview

You have to actually get the interview which means having a purposeful resumé and making sure it gets to the company. Once you’re done, don’t just send it in with the rest, you may use your networking and a bit of creativity to beat that computerized system and get your resumé into the right people. If you don’t get the interview, find out why and use that to help you the next time around

Be Prepared Ahead of Time

Now that you’ve got the interview, you still have a lot of work to do before you walk into the door. Note that the main reason most people fail at interviews is a lack of preparation. So, research as much as you can about the company, know the job description, and it’s good to have a way to stand out in that interview among all the other applicants. Creating a good cheat sheet together and studying it can support you out, too.

First Impression: Get to It

Your tech interview starts the second you walk in the door, so be set. You may also need to rehearse your walking stance into a room if you have to. More than anything, absorb how first impressions work and do everything you can to make a good one: Don’t late, be on time, dress and groom yourself soundly, and be mindful of your body language. Put in mind, just giving a damn will go a long way in your first impression—if you don’t want to be there, they’ll know.

Challenge the Tough Questions

Once you’re there at the interview, it’s time for the hard part: responding to the interview questions. It is good to know the questions you’ll be expected to answer backwards and forwards, and do some extra inquiry on answering the really rough ones, like “what is your main weakness,” “have you been fired,” “tell me about an encounter you faced with a colleague,” or even just the ever-vague “tell me about yourself, your experience.” Your answers will probably follow a specific pattern, so when you fall uncertain, fall back on the STAR technique. But most of all: know the reason why they’re asking you each question and style your responses to their hidden reasons. Do not be afraid to hop around questions you’d rather not answer, too.

You May Ask Questions too

Your interviewer shouldn’t only be the only one asking questions. It is your chance to not only make a good impression but learn a bit more about the job you’re applying for. Ask a few questions that will make you look virtuous, as well as some questions that’ll show you whether this is the precise job for you. With the right questions arranged, you’ll be one step ahead of the competition.

Let Your Good Qualities Be Emphasized

You will feel the need to be modest but don’t. Be confident, by shy away from blatant self-promotion. Showing your skill is one of the best ways to prove your worth. If you don’t have the experience to flaunt, remember that potential is actually more valuable than experience: if you can show why you’re a talented hire, you’re in.

Avoid the Common Drawbacks

Know that you are prepared with your tech interview techniques, but it’s also vital to know what to avoid. Even something as simple as undesirable body language can disrupt your chances, so make sure you aren’t hurting yourself without knowing it. Do an inquiry of the subjects you should avoid and make sure you don’t overshare, particularly when it comes to your personal background. As long as you don’t raise any red flags, you should be decent to go.

Remember to Recover When Things Go South

Optimistically, with the right preparation, your tech interview will go efficiently. But, if you end up answering a question terribly or hit a common brick wall (like claims of “overqualification”), learn how to turn the current quickly so you can get back on a good basis. When you leave the interview thinking the whole thing was a tragedy, you may always turn it into a learning experience for the next interview.

Follow Up After the Tech Interview

Never let your interview be the last they hear from you. When you follow up afterward, you’ll help them recall who you are, and make sure your resume doesn’t fall into the abyss of the disremembered. You can send a thank you note or card after your interview, and a short email, later on, to check in if you haven’t received back. Take into account how you’ve been collaborative with them so far, though, as different modes of communication may be more helpful. If you have a follow-up interview, be sure to nail that too.

If Are Not Hired, Find Out Why

Not every tech interview will be a winner, sadly, even if you do everything precise. If you don’t get hired, the best thing you can do is find out why and apply that information to your next round of interviews. Look back on your interview and think about what you could have done better, whether it’s avoiding the “overqualification” snare or just simply use good grammar. There could be a number of reasons someone might not hire you, and all you can do is use this round as practice for your next tech interview.
For more knowledge on how to ace your Tech Interview get the book “Inside the Tech Interview” . Available on Amazon on Kindle and Paperback.

Breaking into the Tech Industry

So your interview is coming up soon.

If you are unclear about anything in particular, you can ask your recruiter or point of contact at the company you are having the tech interview with. You may as things like: What sort of complications will there be on the interview? Anything specific you should prepare for the interview? Will there be any pair programming? Should you bring your laptop for coding? Will you be able to Google documentation during the interview?

Remember these are fine questions. It is not going to be a big deal if you ask. Just ask

Some basics:

At a tech startup you may dress pleasantly, but casual. A sweater or button-up and jeans works fine. In some conservative companies, you may wear a dress shirt and slacks to pair. You may ask your recruiter if you are uncertain. This is not a taboo question at all.

The recruiter often offers something to drink. You may take it of you want it. And you may use their bathroom. Make yourself relaxed.

When the time comes you meet your interviewer, greet politely, and acquaint yourself with him. Relax. Try to remember their name, because if you do, blurting out their name is something good to hear. Remember that there’s always ritual to beginning an interview and it’s not complicated.

When your interviewer will walk in the room, give your best smile. Tell your name. Shake hands confidently with him/her. Look her in the eye.

Do adopt a relaxed body language. You may lean back in your seat. Try not to fiddle—just clasp your hands together if you can’t help being nervous. You will be completely fine. Don’t over analyze too much. You may ask your interviewer what side she’s on the company, this will get the conversation rolling.If you feel so nervous, it’s acceptable to tell them that.

Talking About Yourself

When you start telling the interview about yourself, most tech interviews are incredibly systematic.

Almost every question you’ll be asked will be a variation of one of these four:

What’s your background? / walk me through your resume / why did you leave your last job?
Why do you choose to apply for us?
Tell me about a challenging incident you faced and how were you able to solve it.
Tell me about an interesting project you worked on.

The initial question is mainly significant. Basically, they want to hear your personal history. Your answer will strongly influence their insight of you.

It is basically storytelling. Reflect yourself as acharacter in a story, and structure that with a beginning, middle, and end. There should be modulation of facts, representation, and easy to understand motivations. Remember to keep it as short as possible, while stabilizing color and what makes you interesting. Try not to be destructive. Do frame your story around seeking challenge and wanting to better yourself, rather than refusing or abhorring things.

If you interview enough, eventually it will solidify into a script. The greatest way to improve at it is to literally practice it out loud and do a recording. You may also try to get advice from someone whose judgment you trust, and ask them to be as ruthlessly honest as possible.

For the other three questions, you should have have pre-crafted answers. If you’re at a loss for stories, it may help to sit down and just brainstorm every relevant story you can remember and then narrow it down from a larger list.

It’s hard to practice this effectively in a vacuum, so this is a good thing to work with someone else on.

Once you’ve answered all your interviewer’s soft questions, they may ask you if you have questions for them. Tell them you’ll save your questions until the end of the interview. This will give you more time to for the actual programming part, which is the majority of where you’ll be evaluated.

Most likely you will be interviewing at different companies, but you should always talk about what makes this company unique and captivating. At the same time, you don’t want to appear desperate. I liked using the phrase “looking for good mutual fit.” You want to be discriminating, but you also want to seem winnable if they make you the right offer. If you seem outright disinterested in the company, then they probably won’t want to make you an offer even if you pass their technical bar.

Companies do vary significantly in culture. But a lot of “culture fit” really just comes down to a simple question: would your interviewers actually want to be your colleague?

For more tips about this you may buy my book “Ïnside the Tech Interview”, Available in paperback and kindle!