How solo engineers landed their first gigs: lessons from an Ask HN thread

The quick take

Ask HN asked: how did you land your first projects as a solo engineer or consultant? The replies were a mix of pragmatic tactics and humble hustle. It has been reported that the most common answers boiled down to three simple things: warm outreach (former coworkers and employers), small paid experiments or pro bono pilots to build trust, and leveraging online marketplaces or communities. Cold DMs worked sometimes. So did a short blog post or a single open-source contribution that caught someone’s eye.

Stories and tactics

Readers shared anecdotal routes — from turning a side project into a paid project overnight to answering a comment on a forum and getting hired the next week. Some allegedly scored work through Upwork or similar platforms; others landed gigs by asking past managers if they needed short-term help. The emotional moments stand out: relief at the first invoice, the awkwardness of setting a rate, the pride in a referral that came from a tiny unpaid favor. Networking wasn’t glamorous, but it worked — meetups, alumni groups, and old Slack channels came up again and again.

What to steal from the thread

Practical takeaways: start visible (write, speak, show your code), make the first ask small and low-risk, and treat early clients like gold — referrals matter more than hourly rates at the start. Contracts, scope clarity, and saying “no” to scope creep were also recommended. Want a shortcut? Warm introductions beat cold outreach. Want resilience? Diversify lead sources so one dry spell doesn’t sink you.

A handful of respondents highlighted long-term positioning: niche down, become the obvious choice for a specific problem, and keep a simple portfolio that proves you solved that problem. It’s not rocket science. But it does take grit, patience, and a few humble first gigs to get the ball rolling.

Sources: Hacker News