Frontend Developer job description
A Frontend Developer builds the parts of a website or web app that people see and use. A business needs one so that customers find the product quick to load, easy to use and reliable on any device.
Why the role exists
The Frontend Developer turns designs into working screens. In an Indian product or services company, this person sits between the designer and the backend team. Many users here browse on mid-range Android phones and patchy networks, so speed and layout on small screens matter as much as looks.
What the person does
- Convert designer mockups from Figma into responsive pages and reusable components.
- Connect screens to backend APIs and handle loading, empty and error states properly.
- Test layouts on real phones and common browsers, and fix issues on low-end devices.
- Improve page speed by trimming bundle size, optimising images and delaying heavy scripts.
- Write component and end-to-end tests for the main user journeys such as sign-up and checkout.
- Check accessibility basics, including keyboard use, colour contrast and labels for screen readers.
- Raise gaps in designs or API responses with the designer or backend developer before building around them.
- Maintain a shared component library so new pages follow the same look and behaviour.
Skills and tools
- HTML, CSS and modern JavaScript or TypeScript
- A major framework such as React, Next.js, Vue or Angular
- State handling and data fetching, for example Redux, React Query or similar
- Responsive design with Flexbox, Grid and CSS frameworks such as Tailwind
- Browser developer tools and Lighthouse for performance checks
- Reading Figma files and spacing, type and colour specifications
- Testing with Jest, Cypress or Playwright
- Working with REST and GraphQL responses and handling failed requests
Education and experience
Preferred, never a bar: equivalent experience counts.
- Preferred: a degree or diploma in computer science, IT or design technology, or equivalent experience.
- Preferred: a portfolio or live links showing pages the candidate built, with notes on their own part.
- Self-taught and bootcamp candidates are welcome when their work shows sound fundamentals.
- Preferred: experience with at least one production web app used by real customers.
How the work is judged
- How closely finished screens match the approved design and work across the agreed devices and browsers.
- Page speed and stability as measured by the team's own performance tools over time.
- Number of visual and functional defects found by QA or customers after release.
- Reuse of components and the tidiness of the code other developers must work with.
- Responsiveness to feedback from design, product and backend teammates during a sprint.
Where the role can lead
- Senior Frontend Developer, owning the architecture of a web app and its component library.
- Frontend Lead, setting standards and reviewing the work of a small team.
- Full-Stack Developer or UX Engineer, moving closer to the backend or to design systems.
Interview questions to ask
Ask every candidate the same questions in the same order and score them against written anchors, so the decision rests on the work and not the impression.
- A page loads slowly on a budget phone. What steps do you take to find out why and fix it?
- Explain how you would build a form with validation, error messages and a retry after a network failure.
- Show us a screen you built. What did you change from the design, and why?
- How do you decide between keeping state in a component, in a shared store or on the server?
- A bug appears only in one browser. How do you reproduce it and decide how to fix it?
- How do you make a page usable for someone who cannot use a mouse?
Hiring tips for this role
- Ask the candidate to build or fix a small screen live, including a slow network case. Watch how they handle errors, not just the happy path.
- Open a site the candidate built on a phone. Pages that look fine on a laptop but break on a small screen reveal weak fundamentals.
- Separate framework knowledge from JavaScript knowledge. Some candidates copy patterns well but struggle when a problem falls outside the tutorial.
- Do not hire only for visual polish. A slower, careful developer who tests and cares about speed usually serves customers better.
Questions about hiring a frontend developer
No. A designer decides how a product looks and flows. A Frontend Developer writes the code that makes that design work in a browser. The two roles work closely, and some people have skills in both.
Ask for the framework your product already uses. Most skilled frontend developers move between React, Vue and Angular with some practice. Insisting on an exact tool can shrink your candidate pool without improving quality.
If your product is only a website that works well on phones, a Frontend Developer may be enough. A native or cross-platform app, with push alerts and device features, usually needs a mobile developer.
Yes. GullyHR supports permanent hiring. We agree the job description with you, find and screen candidates against it, and support the offer stage. Your team decides who joins.
Hiring a frontend developer?
GullyHR runs talent acquisition for permanent roles. We agree the job description with you, find and screen candidates against it, and support the offer through to joining. We recruit permanent employees. We do not supply contract or temporary staff.