A Lead GraphQL Developer role has come open in Whitefield, Bangalore, on-site and full-time, paying INR 155,500 a month. This sits at the senior end of the software development ladder, and the company is hiring someone who can own API-layer architecture decisions, not just implement what someone else has already designed.
Experience and education expected
The team is asking for twelve years of hands-on software development experience, and at that level, actual project history tends to matter more than the diploma behind it. Even so, a four-year undergraduate degree remains the formal minimum the company lists, and they won't waive it regardless of experience.
What they actually care about, though, is a track record of shipping and maintaining GraphQL APIs at scale, including the messier parts: schema versioning across multiple consuming teams, resolver performance under real production load, and the tradeoffs between a single unified schema versus a federated one as an organization grows.
Core responsibilities
- Designing and maintaining GraphQL schemas that serve multiple frontend and mobile teams without becoming a bottleneck as new features get added
- Owning backend architecture decisions for the API layer, including how the Node.js (or equivalent) services underneath the schema are structured
- Collaborating directly with frontend, mobile, and product teams on new features, translating what they need into schema and resolver changes that actually hold up
- Reviewing code and mentoring mid-level engineers on the team, particularly around GraphQL-specific patterns that aren't always intuitive coming from a REST background
- Fixing bugs that surface during testing or production, especially the ones that trace back to resolver performance or over-fetching issues
A recent situation on this team involved a mobile app's home screen query pulling in far more nested data than it rendered, quietly adding almost two seconds to load time on slower connections. The fix wasn't a backend change. It came from restructuring the query itself and adding field-level cost limits so a similar problem couldn't sneak back in later. That kind of cross-team diagnosis, where the real fix sits outside your own code, comes up more often at the lead level than junior engineers usually expect.
Required skills
Deep, practical GraphQL experience is the anchor requirement here, not just familiarity from a side project. Alongside that, strong backend development in Node.js or a comparable server-side language is expected, along with real API design judgment (knowing when a field belongs in a schema versus when it's scope creep). Solid Git workflow experience, including managing branching strategies across a larger team, rounds out the core list.
Good to have
Experience with a federated GraphQL setup, using something like Apollo Federation, is a genuine advantage given how the platform is likely to grow. Some exposure to performance profiling tools for identifying slow resolvers helps too, since that's a recurring theme at this scale. Prior experience leading a small team, even informally, also translates well to the mentoring side of this role.
Compensation and benefits
Base salary is INR 155,500 per month. The role includes health insurance, paid time off, and performance-linked bonuses, standard for lead-level software development positions at this company. Naukri Mitra notes that, since the position is based on-site, employees also get access to the office cafeteria and either a cab facility or a commute allowance, depending on where they're coming from.
Team and growth
Whitefield has become one of Bangalore's more established tech corridors, and this team is part of a company that's been expanding its GraphQL-based platform steadily rather than in sudden bursts, which tends to make the architecture decisions here feel more deliberate than reactive. Someone who does well in this role over a couple of years often moves toward a principal engineer or engineering manager track, depending on which direction genuinely interests them.
Applicants should be ready to walk through a real GraphQL schema decision they made and what tradeoffs it involved, since that says more than a list of frameworks touched. Experienced professionals already working in GraphQL-heavy roles in Bangalore, or comparable senior backend engineers open to specializing further, are both a good fit. The team is reviewing applications on a rolling basis.
