"Portfolios" in some form are often necessary. (In my space, writing samples.) If you have those ready to go, easier for everyone! But if you don't have a relevant portfolio, you'll need to either put something together or I'll pass. (I'm not really looking for a specific assignment but just something that's representative of the type of work.)
why would a software dev have a portfolio? The comparison to design or writing doesn't make sense. A graphic designer can point to logos or marketing material that is publicly available. I'm not going to put proprietary code on a portfolio nor am I going to spend multiple years building some open source project when I already have a full time job.
Software engineering must be the only profession where employment history means nothing. And yet... interviewers always want salary history to knock you down. If you don't care about the work I did in the past, then why do you care about how much I was given for that work?
ghaff|2 years ago
deckard1|2 years ago
Software engineering must be the only profession where employment history means nothing. And yet... interviewers always want salary history to knock you down. If you don't care about the work I did in the past, then why do you care about how much I was given for that work?
deprecative|2 years ago
jnwatson|2 years ago