I wonder how much "side projects" would help in the job hunt. Build things, put them on github, write 500 words about it, add to resume, repeat.
Maybe I succeeded despite working like this, but I tend to think I succeeded because I worked like this.
Maybe I succeeded despite working like this, but I tend to think I succeeded because I worked like this.
There's a night and day difference between asking a newbie engineer about their ideas in an interview vs talking about something they've built before.
I made a bad chess game in JS before applying for jobs after college, and ended up talking about it in half my interviews - either describing it, or, in a few cases, finding that the interviewer had played it before I showed up (in one case he found some bugs! I brushed it off, saying that I had quit the project after getting basic functionality down and hadn't thoroughly tested pawn promotion...).