Frontend Engineer

ASCENRA TECHNOLOGIES; Varanasi; Hybrid; INR 1,200,000 - 2,400,000; Full time

Job summary

ASCENRA TECHNOLOGIES in India is seeking a Frontend Engineer to build and own enterprise surfaces—the Admin portal, consumer app, and embeddable Web SDK—using React and TypeScript for web and Flutter for mobile.

This hybrid, full-time role is based at Grandthum, Greater Noida, reporting to the Head of Engineering, with 4+ years of frontend experience and a focus on accessibility, testing, and scalable UI.

Qualifications

• 4+ years of professional frontend engineering experience.

Responsibilities

• The Enterprise Console and Admin portal in React and TypeScript — dense, data-heavy screens used by compliance teams daily.

Skills

Deep React & TypeScript

Flutter/Dart mobile experience

React Native / native Android/iOS

Accessibility practice

Testing: Jest & RTL

English language (proficient)

Education

B.E./B.Tech or M.Tech in CS/IT, or equivalent demonstrated experience

Job description

Frontend Engineer

Own every surface a human being touches: the enterprise console organisations administer consent through, the admin portal, the consumer app people manage their own data in, and the SDK that puts a consent flow inside other companies' products.

Location

Greater Noida

Grandthum, Tech Zone IV, Greater Noida West, Gautam Buddha Nagar, Uttar Pradesh

Work type

Hybrid

Contract type

Full-time, permanent

Reports to

Head of Engineering

Experience

4+ years

Why this role

A consent notice a person cannot understand is not consent.

01 Real influence over what these products feel like to use

02 Comprehensibility is a legal standard, not a design preference

03 An embeddable SDK that runs in environments you do not control

04 Console, app and SDK expressing one truth about consent state

The work

What you'll actually do

01 What you'll own

• The Enterprise Console and Admin portal in React and TypeScript — dense, data-heavy screens compliance teams live in daily
• The consumer consent app in Flutter, used by people who did not choose to be there and will not read instructions
• The embeddable Web SDK: consent flows that run inside other organisations' pages without breaking them and without leaking anything
• Platform integration — consuming our APIs and handling JWE-encrypted auth correctly on the client
• Accessibility and language: the interface has to work for people with disabilities and in the languages people actually read

02 The hard part

• Comprehensibility is a legal standard here — a notice must be understandable, in English or any language in the Eighth Schedule
• Up to twenty-two languages, with scripts that break naive layouts, in an interface where a confused user is a compliance failure
• An SDK you do not control the environment of — other people's CSS, CSP and frameworks; it must work, stay isolated, and never break their site
• Two surfaces, one truth: console, app and SDK must express the same consent state without three divergent implementations

03 Minimum qualification

• 4 years of professional frontend engineering, or 3 years with an advanced degree — or equivalent practical experience
• Deep React and TypeScript: deliberate state management, component design you would defend, performance work you have measured
• Production mobile experience — Flutter/Dart preferred; strong React Native or native Android/iOS plus a serious appetite for Flutter also works
• Something you have shipped to the App Store or Play Store and then maintained through releases
• Real accessibility practice: semantic markup, keyboard paths, screen-reader testing. Not an audit you commissioned
• Testing as a habit — Jest and React Testing Library, widget tests, and enough end-to-end coverage to sleep at night

04 Preferred

• Embeddable widgets or a Web SDK that runs inside somebody else's page — isolation, styling, CSP, versioning
• Design-system ownership, particularly the governance rather than the components
• Internationalisation at real scale, especially Indic scripts and the rendering problems that come with them
• Any work where the UI carried a legal or regulatory obligation

How we work

• Hybrid working style with anchor at our Grandthum office in Greater Noida, Tech Zone IV
• Defined core collaboration hours — outside that, flex your day around its natural shape
• Architecture decisions get written down and argued in the open. Small, reviewable changes. Depth is valued over volume
• Company-issued devices and approved tooling for anything touching customer or compliance data. Given what we build, we hold ourselves to the standard we sell

The practical details

• Location: Grandthum, Tech Zone IV, Greater Noida West, Gautam Buddha Nagar, Uttar Pradesh
• Employment type: full-time, permanent
• Reports to: Head of Engineering
• Education: B.E./B.Tech or M.Tech in CS/IT, or equivalent demonstrated experience — we mean the second part
• Offers are subject to standard background verification, which we will explain before we ask for anything

How we'll interview you

• A 30-minute conversation with our Head of Engineering
• A code and architecture discussion on something you have built and can talk about honestly
• A conversation with the founder about the company, the regulation and where this goes
• Four stages. We aim to complete them inside two weeks and to give you a decision either way

Ideal candidate

You’ll thrive here if this sounds like you

You have opinions — the design does not arrive finished here, and we do not have a designer yet

You work directly with the founder and the Head of Engineering and can argue a position

You care about accessibility and language as product requirements, not afterthoughts

You have shipped and maintained software real people use without instructions

You are comfortable early: uneven hours around MVP, and some of what you build you will rebuild

[e-mail]