A niche is the specific slice of your skill that you're known for — not "I do web development" but "I build WordPress websites for local restaurants and clinics." Counterintuitively, narrower usually gets hired faster than broader.
A client searching for help rarely wants a generalist — they want someone who has clearly solved their exact problem before. "Full-stack developer" competes with thousands of identical profiles; "React dashboards for logistics companies" competes with almost no one, and reads as expertise rather than a guess.
| Approach | Example |
|---|---|
| By skill + deliverable | "Responsive landing pages in HTML/CSS," "Excel dashboards for small business owners" |
| By skill + industry | "WordPress sites for medical clinics," "Social media graphics for restaurants" |
Nobody picks the perfect niche on day one. Taking varied early jobs to learn what's actually enjoyable and in demand is normal and useful. The mistake is staying general a year in, once there's enough completed work to see a real pattern in what clients keep hiring for and what actually pays well.
List every piece of work completed so far (course projects count) and mark which ones felt easiest and which paid or would've paid best. The overlap between "easiest for me" and "clients pay well for this" is usually the honest starting niche — not the most interesting-sounding one, the one at that actual intersection.
It can change
A niche isn't permanent. It's fine to narrow, widen, or pivot entirely as real client work reveals what the market actually wants from you.