3 ms·
I'm a generalist web dev, I do something similar if I'm confident that it will work. In fact, it's something I learned from someone who calls that the "briefcas
by vinibrito 1y ago
I'm a generalist web dev, I do something similar if I'm confident that it will work.
In fact, it's something I learned from someone who calls that the "briefcase technique". But for most pitches I don't, for the obvious reason of limited effort to apply to all.
P.S: when I'm on the hiring side, if all someone has to offer is free work then it doesn't help the person's pitch. That has happened, didn't help the candidates, they just weren't a good fit and free work wouldn't change that. I didn't engage in the free work offer.
But I say this because for the needs I had I could quickly filter for the skills I needed without lengthy interviews.
- codebytrial 1y agoThat’s a great point — if someone only offers free work without clear signals of fit, it probably won’t help. I see this less as a value flex, and more as a trust accelerant — especially in cases where the work is exploratory, multi-layered, or where cultural fit really matters. Totally agree this wouldn’t change much for “clear-cut” hires where a quick repo scan or question is enough. But when the match is more ambiguous — or when you're competing with a hundred devs on credentials alone — sometimes doing the work is the shortcut. Appreciate your insight. Sounds like you've been on both sides of the table too.