Skills that make the work valuable
- Component architecture
- Accessible interaction patterns
- Client state management
- Browser performance profiling
Build proof, not just a list
Build an accessible task dashboard with filters, loading indicators, empty states, and recoverable errors. Show keyboard navigation and explain how you measured and reduced unnecessary rendering or downloaded code.
How to price this work as a freelancer
Estimate complete user flows rather than counting screens alone. Confirm whether designs, API contracts, and shared components are ready, then price integration and testing explicitly. Changing response formats and late design revisions can reduce utilization even when the visual layout appears nearly finished.
Start with the income you need to replace
Required hourly rate = (target salary + benefits budget + annual business expenses) ÷ (annual billable hours × share of revenue retained after fees).
For illustration, $100/hour × 25 billable hours/week × 48 working weeks = $120,000 revenue. After $20,000 in business expenses, that leaves $100,000 profit before personal taxes. Replacing a $100,000 salary plus $15,000 in benefits under those assumptions takes $112.50/hour, with no percentage fees.
These are editable planning assumptions, not rates surveyed for frontend developer work. Your personal taxes, location, contract terms, and workload still affect the comparison.
Employee or freelancer?
Working as an employee
Working inside a product team supports shared components and regular collaboration with designers. You may spend substantial time coordinating releases and adapting interfaces to backend or product constraints.
Running a freelance business
A focused interface specialty can make project boundaries clear. Your delivery still depends on client designs and APIs, so waiting time and integration ownership belong in the agreement.
Where this career could take you
- 01Junior Frontend Developer
- 02Frontend Developer
- 03Frontend Lead
An example path, with room for lateral moves or specialization. Progression depends on opportunities and demonstrated work; these steps do not imply a timetable or salary increase.
Try one small next step
Implement one dashboard interaction with realistic loading and failure states. Have a keyboard user try it, then write down the fixes and your component decisions.