Chennai has a React Developer opening in Taramani, right by Tidel Park. Full-time, on-site, 70,500 rupees a month, filed under Software Development.
Skills That Get You In the Door
This is a React-first role. If your JavaScript is sharp and you've shipped real component-based UI, you're already most of the way there.
- React, at a level where you're comfortable owning components end-to-end
- JavaScript fundamentals, not just framework syntax copied from tutorials
- Redux for state management across larger apps
- HTML and CSS, including responsive layout work
- Git for version control and collaborative workflows
- Component-based design thinking, so features get built as reusable pieces rather than one-off code
Bonus Points
TypeScript experience will get you noticed faster in the interview. So will exposure to testing libraries like Jest or React Testing Library, familiarity with a design system or component library you didn't build from scratch, and hands-on time with browser performance profiling. None of these are dealbreakers, but candidates who bring one or two tend to move through the interview process quicker.
Server-side rendering experience, whether that's Next.js or something else, is also worth mentioning if you have it. It's not something the current stack leans on heavily today, but it's on the roadmap for a couple of upcoming projects, and having someone on the team who's already comfortable with it saves a learning curve later.
The Day-to-Day
Feature work here doesn't sit in a vacuum. Product hands off requirements, design hands off screens, and the engineer translates both into something that renders correctly across devices.
- Implementing new features straight from project requirements
- Debugging and resolving technical issues as they come up in the codebase
- Documenting your work so the next engineer isn't guessing why a component behaves the way it does
- Sitting in on code reviews, both reviewing others' work and getting your own reviewed
Some weeks lean heavily toward building new screens; other weeks get eaten up chasing a rendering bug that only shows up on one specific browser version. Own both kinds of work, because they come in roughly equal measure here.
Documentation here isn't a formality tacked on at the end of a ticket. It's expected to actually explain the decision behind a component, not just restate what the props do, since the next person touching that file might be someone who joined the team six months after you wrote it.
What You'll Need on Paper
The baseline ask is a bachelor's degree, with computer science or IT being the usual routes in, though nothing rules out an adjacent field if the coding chops are there. On top of that, the team wants four years of hands-on experience building production React applications, not four years split thin across a dozen different stacks.
What actually gets checked in the interview matters more than the degree line on a resume. Expect a live coding round built around a real component, plus a walkthrough of a past project where you'll explain the trade-offs you made, not just describe the finished feature.
Pay and Perks
Salary lands at 70,500 rupees monthly. Health insurance and paid time off come standard, and provident fund contributions are handled the way they should be for a full-time role in India.
- Health insurance
- Paid time off
- Provident fund contributions
- On-site cafeteria access
- Cab or commute support
The cafeteria isn't a token perk either. Lunch is subsidized enough that most of the team eats on-site rather than stepping out, which keeps the midday break short and predictable instead of eating an hour out of the afternoon.
Working Out of Tidel Park
Taramani puts you right in one of Chennai's biggest tech clusters, and Tidel Park itself houses enough companies that the food court gets genuinely crowded by 1 pm. Naukri Mitra lists a good number of React developer job openings in Chennai every quarter, and this one sits comfortably at the higher end of React developer salary in Chennai per month for someone with four years under their belt. The commute support matters more here than it sounds, since OMR traffic heading into Taramani during peak hours can stretch a twenty-minute drive into well over an hour. A fair number of engineers here have worked at more than one company inside the same Tidel Park building over the years, which says something about how tight-knit the local React community is in that particular stretch of the city.
How the Team Runs
Sprints run on a two-week cycle, with a planning session at the start and a demo at the end where anyone on the team can push back on a design decision if something feels off. Code review isn't a rubber stamp here. Expect actual comments, sometimes multiple rounds on a single pull request, especially if a component is going to get reused across the app. That can feel slow in the first month, but it cuts down on the kind of bugs that only surface three sprints later when nobody remembers why a prop was named the way it was.
Pair programming happens occasionally, mostly when someone's stuck on something gnarly like a state management bug that only reproduces under specific network conditions. Nobody's expected to solve everything solo before asking for help.
The team's split roughly between people who've been here two-plus years and a few who joined in the last six months, which keeps institutional knowledge intact without the whole group getting stale on newer approaches. Someone joining now would land somewhere in the middle of that mix.
How to Apply
Meet the experience and skills bar above? Send in your application through the process listed with this posting. Come ready to talk through a real React project you've built, ideally one where you had to make an actual architecture decision rather than just following a tutorial's structure. We review applications as they arrive, so there's no reason to hold off. If you have a GitHub profile or a portfolio site with live projects, link it, since the team will review it before the first call.
