The first 30 days with a freelance software engineer

Freelance should feel calmer than hiring theater

A freelance software engineer is useful when you need senior ownership without a six-month recruiting cycle. The first 30 days are where that promise is proven—or not.

If week two is still “alignment workshops,” you hired a coordinator. If week two is a URL you can click, you hired an engineer.

Week 1: the brief and the slice

1. Users, the first workflow, and what “done” means in 90 days.
2. The smallest vertical slice: auth + one job-to-be-done + a deploy.
3. Access: repos, cloud, analytics, the domain you already pay for.

I write this down. You should be able to forward it to a cofounder without a translation layer. See also how to hire a software engineer online.

Weeks 2–4: production, not theater

• A staging URL and a path to production with rollback.
• The core workflow usable by a real person, even if ugly.
• A thin admin or ops note so you are not trapped in my laptop.

Measure: can a user complete the job without you on a call?

How remote work stays visible

A remote software engineer should live in your GitHub, Slack, and deploy logs. Async by default; live sessions for architecture. Timezone overlap is a constraint we name in week one—not a surprise in week three.

When freelance is the wrong shape

If you need a dozen parallel workstreams, or daily same-city pairing, an agency or an in-house team may fit better. I will tell you that before we start. Otherwise, send the outcome to faizan.codes.