5 More Quick Avoidable Mistakes for Full-stack Applicants

Jack Yeh
TeamZeroLabs
Published in
7 min readFeb 2, 2020

--

Take a breathe, fix it and try again! Part 2

tl;dr: Accidentally checking in credentials/Missed responsive look & feel for frontend repos/Not using the configuration service pattern/No README and screenshots/Not having repository reviewed by more experienced people

Disclaimer: I work with U.S. startups in Bay Area and NYC 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. I have received several repositories to review and give feedback on. I appreciate all of the review requests, and will refer and give tips on when applicable.

You can also read Part 1 here.

Background: The Hiring Process for full-stack developers is a mixed bag at the Startup scene in 2020.

Source: crunchbase.

The current process goes something like this:

  1. Founders put together a MVP to get seed fund/first 100 users.
  2. Startup attempts to develop new features and acquire new clients.
  3. Having only 1–2 technical founders on the team, they begin to…

--

--

Jack Yeh
TeamZeroLabs

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