Preparation

Two Major Takeaways:

  1. Know what to expect!
  2. Practice!11. Specifically, you need authentic practice. Not just “solve problems a few times” but “somebody gives you questions and you properly work out the problem with them”.

For Interview Questions:

For Data Structures and Algorithms Reference:

For Effective Programming Reference:

Researching the Position

This is the first step of any application, it seeks to answer:

  1. Do I want this job? (Is this a good fit22. Whether your strengths and interests align with your job.?)
  2. How can I get this job? (How do you apply and prepare?)
Example: On Shoehorning (e.g., “Can I get this job?”)

Many people ask, “how can I phrase my background to try to get this position?” and similar questions.

A better question is, “could this job be the right fit for me?”.

Determining Fit

  1. Do the job qualifications and job description match your background?
  2. Does the company background match?

As you research, note down your questions and save them for the interview.33. And if you ALREADY know somebody at the company, reach out and ask them these questions before applying.

Company Background

If you get the interview, research the company background44. You need to have critical knowledge if THEY ask (don’t overreach!); e.g.,

Resume Tips

Tip: Focus on Accomplishments (not assigned tasks)

Example: Fixing a bad bullet-point
TechSocial
Software Engineering Intern
- Software Engineering Team, C++

This is slightly redundant.


TechSocial
Software Engineering Intern
- Member of Backend Optimization Team, C++

Better, but still just passive and task-oriented. We now know your assigned position, but not what you actually did.


TechSocial
Software Engineering Intern
- Optimized backend to reduce query time by 20%, C++

This is accomplishment oriented. Hip hip hooray.

Pitfalls

Out-of-Date

Update your skills and proficiencies. Don’t list a language if you haven’t used it in several years.

Lengthiness and Formatting

Resume screeners spend less than 30 seconds on your resume.

Overreaching on Skills

Do not list every language you ever touched.

If you list a “proficient” language or technology, it is fair game for the interview.

Not Tailored to the Position

Highlight the items most relevant to the position.

If you did hardware engineering and web design, and the position is for web design; it is extremely wasteful to talk at length about hardware engineering.

Online Presence

Keep your website up to date and social media/digital footprint99. D-did somebody s-say f-f-f-feet??? clean.


  1. Specifically, you need authentic practice. Not just “solve problems a few times” but “somebody gives you questions and you properly work out the problem with them”.↩︎

  2. Whether your strengths and interests align with your job.↩︎

  3. And if you ALREADY know somebody at the company, reach out and ask them these questions before applying.↩︎

  4. You need to have critical knowledge if THEY ask (don’t overreach!)↩︎

  5. e.g., when was it founded? What was it founded for? What was its first product?↩︎

  6. e.g., who’s the CEO? CTO? CFO? What about historical players?↩︎

  7. e.g., what are their products? What’s their niche? Who are their competitors?↩︎

  8. Which is why you must tailor the resume to the position you are applying for!↩︎

  9. D-did somebody s-say f-f-f-feet??? ↩︎