Frontend Engineer

Primary responsibilities

• Build and maintain the candidate-facing surfaces — job search, the application flow, the dashboard people track their applications from
• Own features from the API contract through to the rendered page, including the loading and error states that get skipped when a feature is rushed
• Keep the application form working on a mid-range Android phone on a slow connection, because that is what a large share of applicants are using
• Work to WCAG 2.2 AA: keyboard paths, focus management, form labelling and error announcement, verified with a screen reader rather than assumed
• Hold Core Web Vitals for the pages that get indexed — the search results page and the job page carry the traffic and the ranking
• Extend the shared component library rather than forking a variant into a feature, and take the review conversation when a new pattern is genuinely needed
• Write component and integration tests at the level that catches real regressions, not coverage for its own sake
• Review other engineers' pull requests with the expectation that a review teaches something

Skills required

Day to day this role works with React, TypeScript, Next.js and CSS.

• Three or more years building production React, with real opinions about component boundaries
• Comfortable with TypeScript as a design tool rather than a formality
• Have shipped something where performance and accessibility mattered, and can say what you changed
• Three or more years building production React applications
• TypeScript used as a design tool — types that describe the domain rather than satisfy the compiler
• Strong CSS: layout, the cascade, and why a component breaks at 320px
• Practical accessibility — semantic HTML, focus management, and having used a screen reader on your own work
• Understanding of browser rendering and where the time actually goes on a slow device
• Experience with a modern framework's data-fetching and rendering model, server components included
• Testing at the component and integration level, and judgement about what is worth testing
• Able to work from a design file and raise the case where the design will not hold up in build

Preferred

None of these are required. They are the things that would help, and a strong application is regularly missing all of them.

• Next.js App Router in production
• Experience with internationalisation and right-to-left layouts
• Having owned Core Web Vitals on a page that mattered commercially
• Design systems work, in Figma as well as in code

Working in Engineering / IT / Software

Small teams that own a surface end to end, from the migration to what a candidate sees on a slow connection. Code review is expected to teach, not just approve. On-call exists and is compensated, and the rotation is built so nobody is woken twice in a week.

The individual contributor ladder runs to Principal and Distinguished without requiring anyone to become a manager. Moving into management is a lateral choice made deliberately, not a promotion you fall into.

About Bengaluru

Bengaluru is our largest site and where most of engineering, product, design, data and AI sit. The office is in the eastern corridor, and the majority of these roles are remote-friendly with the team meeting in person a few days a week.

The city has the deepest technology labour market in India, which cuts both ways: the work is here, and so is everyone else commuting to it. Teams are deliberate about core hours because a cross-city commute in the evening peak can take longer than the meeting it was for.