Preparing for a Job Switch – How Much Portfolio Is Enough?
I'm a backend developer with 4 years of experience. This is my first time preparing for a job switch, so I don't really have a sense of what's expected. How many projects should I include in my portfolio? Also, I'm wondering whether it's okay to just drop a GitHub link, or if I should put together a separate document instead.
I'd also love to hear more experienced developers' opinions on whether I should spend more time on coding test prep rather than building out a portfolio.
7 answers
Agreed, for experienced hires, coding tests are a given.
I'm a backend developer with 4 years of experience, and I submitted 3 portfolio pieces. But just linking my GitHub didn't mean anything to HR. It's better to write up a document for each project covering at least the problem definition and the overall structure. Also, don't let the spec doc go over 10 pages. As for the coding test — after you get past the resume screening, I'd say the time split should be around 60% portfolio, 40% coding test?
Well, that's a bit... I mean, a coding test is over once you pass, but a portfolio just keeps getting picked apart.
I'm also preparing for a job change and was curious about this too. Thanks for the comment.
Coding test difficulty has been insane lately, so I think it's right to spend more time on algorithms than on a portfolio.
For an experienced hire changing jobs, explaining 'why you designed it this way' matters more than the volume of your portfolio. I made a 15-page portfolio focused on two projects and improvement cases, and in interviews, most questions were based on that.
Disagree. The whole 'coding tests over portfolios' thing is for newbies. If you're four years in, organizing your experience comes first.