Ask HN: Where do seasoned devs look for short-term work?

Hacker News Discussion ↗

Market conditions and demand

  • Several commenters say the current market for short-term dev work is weak outside AI/ML; money is tight and many businesses are hurting.
  • Short-term gigs are seen as more plentiful in “boom” times (dotcom, mobile, now AI), but even AI work can be patchy or hype-driven.

Networks, relationships, and referrals

  • The dominant advice is: most good short-term work comes via people you’ve already worked with (ex-managers, colleagues, former employers, indie recruiters).
  • Some emphasize reaching out directly to decision-makers (CTOs, founders, small-agency owners) rather than mid-level engineers.
  • Others push back that “use your network” is vague and unhelpful for people who feel they don’t have one; suggestion is to treat every job and community as future-network building.
  • Tension around “friends vs business”: some argue to make friends through work but avoid hiring close friends to protect relationships.

Trust, leverage, and the worker–employer dynamic

  • Some hiring-side voices say short-term devs who “don’t need the money” are risky because there’s little leverage and they might leave or create systems only they fully understand.
  • Others reply that this contradicts the ideal of free-market “free agents,” and note the asymmetry when employers lay off at will.
  • Broader philosophical debate appears about capitalism’s “natural order,” worker vs employer power, and responsibility to family vs society.

Self‑promotion, shame, and “selling yourself”

  • Many describe strong discomfort or shame about advertising themselves (especially on LinkedIn), rooted in humility norms and fear of being judged as “unsuccessful” or slimy.
  • Others insist there’s no shame if you’re honest and actually solving problems; jobs are framed as value exchange, and sales is portrayed as at least half the battle.
  • Suggestions include: forthright LinkedIn “I’m available” posts, mass outreach to contacts, frequent posting on social platforms, and content that quietly signals availability.

Practical channels and platforms

  • Mentioned sources: HN “Seeking Freelancer” threads, Upwork/Toptal (with mixed reviews and rate compression), Codementor, temp agencies, local/indie recruiters, fractional-role boards, moonlightwork, bounty platforms (Opire, Algora), and general contract job boards.
  • Some find fractional/contract sites saturated or low-paid; others report decent rates but emphasize high effective downtime.
  • Non-tech companies via temp/creative agencies are cited as overlooked sources of short-term dev work.

Portfolios, content, and specialization

  • Several recommend investing slack time into: side projects, open-source, articles, blogging, and niche books to demonstrate expertise and stay “top of mind.”
  • Mixed experiences: some say content brings inbound leads; others say interviewers ignore repos and prefer ad-hoc coding tests.
  • Strong emphasis that clients care less about raw skills and more about solving concrete business problems; scoping and project-management skills are highlighted as crucial, especially for “surgical” short engagements.

Alternatives, ethics, and regional constraints

  • One avenue: take a regular job and leave after a short period; critics say this burns bridges and is unethical unless circumstances are dire, while others prioritize family survival.
  • In Germany, rules against “pseudo self-employment” are said to discourage direct freelancing and push work through body-leasing agencies, limiting the usefulness of personal networks.