| This is what has landed me 3 of my 4 programming jobs. 1. Having a web portfolio which has system designs, images, or gif videos of my apps, and points to my github code which interviewers can view. 2. Then walking interviewers through a project during the interview. Whereas 3 months ago, I had a call w/ a "Director" of Engineering for a small startup (5-10 engineers, about 10-20 other staff). He wanted me to do a take home project. "it's just a 2 hour project: a CLI tool to lookup data via REST API, based on arguments passed in. And expose a gRPC endpoint, writte in Go or your favorite language, but we want to see it ready for production with tests". Everything except the REST API part was new to me: a CLI framework, gRPC, protobuf typing stuff. Three hours in, I realized I crossed my self-imposed timebox and that the project would really take about 8 hours (or perhaps 16 if I wanted to polish it and have a higher rate of getting hired). However, I was on my vacation and the purpose was to spend time away from technology. The whole thing felt a bit silly. Learned a new framework though so that was cool (yargs -- https://www.npmjs.com/package/yargs ). |