Frontend Engineer

About Uplevyl

Uplevyl builds AI-powered knowledge and community infrastructure for organizations serving women. Our products include UpGenie (our domain-specific AI assistant), WeHub (our community platform), and UpSocial (a social platform for women). We work with mission-driven partners to turn complex, high-stakes information into clear, trustworthy guidance, and to build systems that create lasting impact.  

We hold a simple conviction: in high-stakes domains like rights, law, and financial security, a generic AI is not enough. The answers people stake their lives and livelihoods on need a purpose-built system with verified, native data. That is what we build, and it is why the work is urgent. AI is reshaping how the world learns, works, and earns, and the women we serve cannot afford to be left off that train.  

We have also made a deliberate choice about how we build: a small team of exceptional people, paid well above market, each doing work that would normally take several. We would rather be ten people who move the world than thirty who move paper. That choice sets the bar for every hire, including this one.  

About the role

The Frontend Engineer works with product, design and backend engineers in a small team, with responsibility for reliable delivery and maintainable code.  

This is a full-time, on-site role based in our Noida office.  

What you’ll own

• Build responsive web interfaces

  in React and TypeScript, including loading, empty, error and stale-data states.  

• Own component structure,

  client state, API consumption, forms and navigation. Agree API contracts with backend engineers.  

• Improve keyboard access,

  semantic markup, browser performance and meaningful automated tests.  

• Investigate production UI failures

  and contribute to release checks and monitoring with the team.  

• Write implementation notes

  and review contributions from engineers and coding assistants.  

Backend engineers own server authorization, data storage and API behavior. Frontend engineers implement the client behavior and verify integration. Infrastructure and cross-client compatibility decisions are shared responsibilities.  

Who we’re looking for

• Strong JavaScript and TypeScript fundamentals:

  asynchronous work, closures, event handling, data transformations and type modeling.  

• React components, state and effects,

  with the ability to diagnose stale state, unnecessary rendering and request races.  

• HTML, CSS, responsive layouts,

  keyboard interaction and accessible forms.  

• Experience delivering and debugging working interfaces,

  with evidence through professional work, private walkthroughs or personal projects.  

Implementation candidates should build and explain a dependable feature, with support on the wider architecture. Senior candidates should also diagnose defects, choose maintainable boundaries, weigh alternatives and improve the team’s delivery practices. The level is agreed before assessment.  

Even better if

• You have experience with component libraries.  
• You have experience with browser profiling.  
• You have experience with automated UI tests.  
• You have experience with GraphQL or REST clients.  
• You have experience with configuration-driven interfaces.  

These are useful signals rather than separate mandatory requirements.  

Before you apply

The hiring exercises use fictional, general-purpose data and require no knowledge of the company’s business domain. Our interview process works as follows:  

• An initial conversation covers shipped work, role expectations and the appropriate assessment track.  
• You complete

  one

  take-home: Track A for implementation roles or Track B for senior roles. Track B does not require Track A. The track is agreed before it is sent.  
• This is followed by a 60-minute technical review: 10 minutes of demo, 20 minutes of code walkthrough, 20 minutes on a small changed requirement and 10 minutes of discussion.  
• You explain the submitted code and trade-offs. The reviewer may request a short independent explanation of a core concept; any tool restrictions will be disclosed before that segment.  

The suggested time cap is four hours for Track A and five hours for Track B. Stop at the cap and describe unfinished work. An incomplete submission is assessed on the evidence available. If local setup blocks progress, contact the recruiter for an equivalent supervised exercise.  

How we work at Uplevyl

We clarify requirements, communicate risks early, review changes and verify behavior before shipping. Engineers can use coding assistants and remain accountable for the code, tests and decisions they submit.  

• We finish what we start, and we do it well. We follow through on what we say we’ll do, and we care about the difference our work makes.  
• We listen before we decide. Before we act, we ask who it actually affects: a customer, a partner, a teammate, or the communities we serve. Trust here is built the plain way, by consistently showing up for people.  
• We move with ownership and urgency. We don’t wait for perfect information or for someone else to raise their hand. If something looks like it could go wrong, we say so early. We make the call, we move fast, and we hold a high bar for quality.  
• We are better together than alone. We work across teams, say what we actually think, and go out of our way to help each other succeed. Leadership here is measured by the impact you create.  
• We stay curious and keep learning, including how to use AI well. We hold ourselves to the bar we’re building toward: questioning our own assumptions and using AI to think better and move faster.