Start preparing for an interview in advance in order to be successful.
Your resume should reflect the position you are applying to. For example, If you're applying to a Software Engineering role and you worked as a “developer” for one of your projects, change the language to reflect “Software Engineer” instead. The words pop out faster to people who are looking at resumes and profiles all day long.
List your education, work experience, personal projects, awards (if applicable to the job). Be aware, if a technology is listed on your resume, make sure you know it because they might ask about it!
Resume should not be longer than 1 page. Specially as a recent grad, at this point in your career, there is no need for your resume to be longer than 1 page.
Create LinkedIn & Github profiles and keep them up to date. This is a big part of how recruiters find talent, if you do not have these profiles, you are likely taking yourself out of the running for various roles. Bonus points if you have a HackerRank profile and list number of challenges completed.
Studying & Preparation
Time yourself. In most interviews you should be prepared to answer 2 coding questions in 45 minutes - 1 hour. When you're preparing, shoot for completing 2 questions in 45 minutes.
Build your confidence by simulating your interview environment. Use a blank notepad or buy a whiteboard. Practice solving coding questions yourself, without using a text editor. I know this might be difficult to do but if you know your interviews will be on a whiteboard, try to buy one. In addition, get a friend to mock interview you, then swap roles to return the favor. Know the process, know the material: ask your Recruiter questions about the process if they haven't given you information by the time the interview is scheduled.
Practice, Practice, Practice. You can't ever do too many practice problems. There are many things you cannot control in the interview process. The most controllable variable in the interview process is how much you prepare. Participate in or practice old questions from coding competitions, like Hacker Cup, Code Jam.
It's okay if you don't get a ton of interviews at first. There's nothing more difficult on your confidence than applying to 20 positions and hearing back from zero. But I know that if you keep at it, keep applying, keep building out your resume, keep studying, keep learning, keep meeting people, the interviews will come!
Secondly, ask clarifying questions before you start solving the problem in the interview. Some people get the question wrong, not because they're not answering it properly, but because they didn't understand the initial question. Make sure you understand exactly what the interviewer is looking for and what is important to them when solving the problem.
Communication. Talk through your approach as you're solving the problem. Remember: your interviewer wants you to succeed. Help them help you succeed, by continuously talking and letting them know what you’re thinking. Additionally, practice speaking about your impact on a project. Learn how to show your impact, it's okay to mention mistakes you've made as long as you talk about what you learned and what your role within the team is/was.
Do your research on the company and have questions prepared. Have a few questions prepared for your interviewer. They will ask you if you have any questions for them, and you should.
Some cool companies
We have crafted a list of companies that typically offer internships apart from Google, Amazon, Facebook, Apple, Samsung and Microsoft. Now you only have to get your resume ready and start applying!
- Flatiron Health
- J.P. Morgan
- Capital One
- Jane Street
By Gabriella Petralia