Senior Frontend Engineer (React )

Senior Frontend Engineer

EXL Digital is seeking a Senior Frontend Engineer with 6+ years of experience building web applications that people rely on every day. Your recent work should be in React. If your earlier years were in Angular or something similar, that counts in your favor. This is a hands-on role with real ownership: you will take features from an early idea through design, build, and release, stay with them afterward, and help decide how the team builds.

Description

EXL Digital is looking for an experienced Senior Frontend Engineer to join our team. At EXL, we believe there is always a better way. We look deeper, we find it, and we make it happen. We've built a culture founded on core values of innovation, collaboration, excellence, integrity, and respect.

The screens you build are where complicated systems become usable. Our applications put a lot in front of people at once: tables they need to sort and filter, dashboards, charts, and work running in the background that updates while they watch. Building that well takes judgment about what belongs on the screen, what happens when data is slow or missing, and whether the page still holds up when the numbers get large. You will work closely with product, design, and backend engineers, and you will have a real say in what gets built and when.

Responsibilities

As a Senior Frontend Engineer, you will:

•          Build and ship features in React and TypeScript, and stay with them after release rather than handing them off.

•          Turn designs and half-formed ideas into screens that are clear and quick to use, and speak up when a design will not survive contact with real data.

•          Make dense information easy to move through: large tables, filters, dashboards, charts, and views that update on their own.

•          Build shared components that other engineers reuse, so the product looks and behaves consistently instead of being rebuilt screen by screen.

•          Decide how the code is put together, including how data is fetched and held and how the application is divided up, and explain the reasoning behind those choices.

•          Write code that is tested and easy for the next person to read and change.

•          Keep the application fast with realistic amounts of data, not just with sample data.

•          Make sure the application works for people using a keyboard or a screen reader, and on a phone as well as a desktop.

•          Handle the unglamorous parts properly: what the user sees while something is loading, when there is nothing to show, and when something has failed.

•          Keep releases routine and boring, with enough monitoring that problems surface before users report them.

•          Review other engineers' code, mentor people earlier in their careers, and write down the decisions worth remembering.

•          Work well with colleagues and stakeholders in other locations.

What We Are Looking For

•          At least 6 years building web applications professionally, with the last two to three years spent in React.

•          Earlier experience in Angular, Vue, or another framework is welcome. What matters is that React is what you work in now.

•          Strong JavaScript and TypeScript.

•          Real depth in React rather than familiarity with it. You can tell when an application is doing more work than it needs to, and you know how to find the cause and fix it.

•          Confidence with the different ways an application can fetch and hold its data, and the judgment to explain why you chose one approach over another.

•          Strong CSS. Layouts that hold up at any screen size, and a way of organizing styles that stays tidy as the codebase grows.

•          You write tests as part of building, and you have used a tool that drives the application the way a user would.

•          Comfortable with version control, code review, and automated builds and releases.

•          A good grasp of how the browser and the web work underneath: requests and caching, what actually makes a page feel slow, and the common security mistakes worth avoiding.

•          Experience working against APIs built by other teams, including deciding what the user should see when those APIs are slow or return an error.

•          You build with accessibility in mind, so that someone using a keyboard or a screen reader can do everything anyone else can.

•          A clear communicator who can explain a trade-off to someone who does not write code.

•          Comfortable working in short, iterative delivery cycles alongside a product team.

•          A degree in Computer Science, Engineering, or a related field, or the equivalent practical experience.

Nice to Have

•          Experience with pages rendered on the server as well as in the browser.

•          Charts and data visualization, and keeping very large tables and lists fast.

•          Screens that update live while work runs in the background.

•          Having owned a shared component library or design system used by other teams.

•          Building tools used internally by engineers or analysts rather than by customers.

•          Presenting data science or machine learning output in a way people can act on.

•          A good eye for spacing, type, and visual detail, and comfort working alongside designers in their tools.