A Senior React Developer position is open in Amritsar, on Ranjit Avenue, full-time and on-site, paying up to ₹124,000 a month. Six years of hands-on React development experience is the baseline for this one. The role sits in the Software Development category, working on a product already in production rather than building from a blank slate, so a good part of the job involves working within existing architectural decisions rather than making all of them from scratch.
Day to day
Most weeks split between building new features and keeping existing ones stable.
- Implement new features based on requirements coming out of product and design
- Debug and resolve technical issues, including ones that only show up in production
- Document the reasoning behind non-obvious decisions so the next person doesn't have to reverse-engineer it
- Review other engineers' code and have your own reviewed in turn
A fair amount of debugging here traces back to state management gone slightly wrong, a component re-rendering more than it should, or a Redux slice holding stale data by the time three other components try to read it. Untangling that kind of thing without breaking something else nearby is a big part of what separates a senior developer from someone earlier in their career. Code review works the same way in both directions: a senior developer here is expected to catch subtle issues in someone else's pull request, and to take feedback on their own code without treating it as a personal critique. Documentation matters more here than at a smaller startup, mainly because the codebase already has enough history that undocumented decisions from a year ago tend to resurface as confusing bugs today.
What's expected coming in
The degree requirement here is a bachelor's, typically in a computing-related discipline. Alongside it, six years of practical project experience building with React is expected, not six years of general software work with React touched occasionally on the side. Candidates coming from a slightly different but closely adjacent background, a strong Vue or Angular developer who's spent the last year or two deep in React, for instance, are still worth a look if the underlying engineering judgment is there.
The required skills for this role:
- React, at a depth that includes hooks, context, and performance considerations, not just component basics
- JavaScript fundamentals strong enough to debug without leaning on a framework's abstractions to hide what's actually happening
- Redux for state management in larger applications
- HTML and CSS, including responsive layout work
- Git, comfortable enough to manage branches and resolve merge conflicts independently
- Component-based design thinking, building pieces that are genuinely reusable rather than reusable in name only
TypeScript experience, familiarity with a testing library such as Jest or React Testing Library, and any exposure to Next.js or server-side rendering would be useful additions, though none are required to apply. A developer who's spent time optimizing bundle size or diagnosing a slow initial page load will likely find that experience directly relevant here, even without any overlap in specific tools.
Pay and benefits
This role pays up to ₹124,000 per month, reflecting the seniority and the expected six years of React-specific experience. It's a competitive figure for a React developer job in Amritsar at this level, and it's set with the assumption that a candidate this experienced has other offers to weigh.
Along with salary, this role includes:
- Health insurance
- Paid time off
- Performance-linked bonuses
- Relocation assistance for candidates moving to Amritsar
- Accommodation support during the initial move
Performance bonuses here are tied to both individual delivery and broader team outcomes, so the exact payout varies year to year rather than being a fixed add-on to base pay.
Working out of Ranjit Avenue
The office is located on Ranjit Avenue, a well-established commercial stretch of Amritsar with good access from most parts of the city. Naukri Mitra has been listing a growing number of software development roles outside this area in recent postings, reflecting a broader shift in IT hiring away from the traditional metro cities and into tier-two centers like Amritsar. For a senior engineer weighing offers, that shift matters: it usually means more room to influence how a smaller, less established team does things, compared to joining an already large engineering org where processes are mostly set. It also tends to mean a shorter distance between writing code and seeing it actually used, since the team is small enough that a senior engineer's decisions are rarely buried under several layers of review before shipping.
This is an on-site role without a remote or hybrid option, so day-to-day collaboration happens in person rather than over a video call.
Who this suits
This opening is aimed at experienced React professionals in Amritsar, not entry-level candidates looking to break into frontend development. Someone with six years split across two or three companies, having owned features end-to-end rather than just implementing tickets assigned by someone else, is a stronger fit than someone with the same number of years spent mostly maintaining legacy code with little ownership. Six years is the stated minimum, but a candidate at exactly that mark with strong, demonstrable ownership of past projects will be considered ahead of someone with more years and a thinner track record.
Applying
Candidates should apply with a resume and, where possible, a link to production work they've contributed to, whether that's an open-source project, a portfolio site, or a case study describing a feature they built and the trade-offs involved. The interview process includes a technical discussion around React and JavaScript fundamentals, a practical coding exercise, and a conversation with the engineering lead about the kind of features this team ships. Candidates can expect a decision within roughly two weeks of the final interview. Anyone currently employed and needing extra flexibility with the notice period should mention it early in the process rather than after an offer is already on the table, since it's easier for the team to plan around a known timeline than a surprise one.
