Start Here

codetalenthub / start here

New here? Start with one of these three paths.

Code Talent Hub covers a lot of ground. Rather than making you dig through categories, here’s the order we’d actually read things in — based on what you’re trying to get out of coding right now.

01
Get your first freelance client
You want paid client work, soon
02
Build passive income
You want income that outlasts your hours
03
Land a dev job
You want a portfolio that gets interviews

Path 1 — Freelancing

~2–3 weeks to first pitch

For developers who want paid client work without waiting on a full-time job search.

  1. Check which skills actually get hired
    Start by matching what you already know against what clients pay for — not the other way around.
  2. Pick your platform strategy
    General marketplaces vs. niche gig platforms — the Freelancing category breaks down where beginners actually win first jobs.
  3. Prepare your first pitch
    Outreach templates and pricing guidance for landing a client with zero platform reviews yet.
    ✓ Use the Freelance Rate Calculator
  4. Explore niche platforms once you have proof of work
    Less competition per listing, but usually requires at least one delivered project first.
Want to see if this path actually pays? Read verified freelancing case studies.

Path 2 — Passive Income

~1–3 months to first dollar

For developers who’d rather build something once and maintain it, than trade hours for client invoices.

  1. Get realistic about what “passive” means
    Ranked by what actually holds up after the initial build — not the idea that sounds best on paper.
  2. Pick a project sized to your available time
    Ten project types ranked by realistic time investment, so you don’t start something you’ll abandon in week two.
    ✓ Use the Portfolio Project Idea Randomizer
  3. Decide: tool, app, or SaaS
    The build and maintenance load is very different between a one-time-sale dev tool and a subscription SaaS product.
  4. Ship and price your first version
    A step-by-step walkthrough for getting a developer tool from “built” to “actually selling.”
See the full list of live projects in the Passive Income category.

Path 3 — Portfolio & Job Prep

~3–6 weeks to interview-ready

For developers whose goal is a job offer, not a client or a product.

  1. Build a portfolio that survives a 6-second scan
    What recruiters and hiring managers actually look at first — and what makes them close the tab.
    ✓ Run the Dev Skill Check Quiz
  2. Turn your GitHub into proof, not clutter
    Which repos to pin, how to write a README that gets read, and what to archive.
    ✓ Use the README Generator
  3. Get your résumé past the ATS
    Keyword-matching, formatting pitfalls, and what actually gets a human to open it.
    ✓ Use the Resume Keyword Match Scanner
  4. Practice the interview itself
    Mock interview formats and technical-round tactics, from the Interview Tactics and Mock Interview Hacks categories.
    ✓ Try the Tech Interview Question Box