Applying for a full-stack position? Make sure you don’t make these 5 technical mistakes

Jack Yeh
TeamZeroLabs
Published in
5 min readJan 14, 2020

--

Take a breathe, fix it and try again!

tl;dr: Get a Github account/watch what you check in/learn BASH if time permits

Disclaimer: I work with U.S. startups and vet their candidates from time to time. Below are some tips I figure would be useful to new comers (Bootcamp or college grads). Most of them are Node.JS related.

Update: Is your portfolio ready? Here is part 2!

Staffing full-stack engineers at early startups is a full-time job

You might have read about people who applied themselves and became a software engineer in less than a year. It is true, jobs are in high demand, and you miss 100% of the shots you don’t take.

So, you embark on the journey to become a full stack engineer, work on example projects, update your resumes, and starting sending out applications. On the other side of the table, the Tech lead/Engineering managers are busy creating the product that will take the company to their series A. They would appreciated if you double check the following mistakes before applying.

Read on to increase your chance of getting to the phone interview and round 2!

Mistake 1: No projects on Github

--

--

Jack Yeh
TeamZeroLabs

I monitor your full stack deployment in production, so you can sleep at night. Docker | Kubernetes | AWS | Prometheus | Grafana