How many portfolio projects is actually 'enough' before you start applying?
I keep telling myself 'one more project and then I'll apply,' and it's quietly turning into a stalling tactic. I've got two decent full-stack apps and one smaller tool.
Is that enough to start applying, or do I look unserious with only three? I'd rather not spend another two months polishing when I could be interviewing (and failing, and learning). For those who got hired — how many projects did you actually have, and did quantity or depth matter more?
2 comments
- 0
AnonymousAnon Honest take after helping screen juniors: it's not the count, it's whether you can talk about one project for 20 minutes — why you made each decision, what broke, what you'd redo. Two projects you deeply understand beat six tutorial clones every time. Start applying once you have one thing you're genuinely not bored explaining.
- 0
AnonymousAnon Three is plenty — you're stalling, and I say that with love because I did the identical thing. Depth over quantity: one project you can talk about for 20 minutes beats five you barely remember building. Start applying now; the interviews will teach you more than project #4 ever would.