We're hiring a Lead Technical Architect for our office at IT City, Sector 82, in Mohali. This is a full-time, on-site role paying ₹221,000 a month, and it sits at the top of our solution architecture group, responsible for how systems are designed across several product teams rather than just one. The scope here spans both new system design and the ongoing evolution of platforms already carrying real production traffic.
Responsibilities
- Design scalable technical solutions for new initiatives, working from business requirements down to actual system architecture
- Set and maintain coding standards and architectural patterns that implementation teams follow across projects, adjusting them as the technology landscape shifts
- Guide engineering teams on best practices during implementation, stepping in directly when a design decision starts drifting from the agreed architecture
- Evaluate new technologies for adoption, weighing what a new tool or framework actually solves against the cost of introducing it into an already-running system
- Align architecture decisions with business goals, which sometimes means pushing back on a technically elegant solution that doesn't actually serve what the business needs right now
- Lead architecture reviews for major system changes, flagging risk before a project is too far along to change course cheaply
Mentoring is part of the role too, mostly with senior engineers who are close to architect-level themselves. That usually looks like working through a specific design problem together rather than a formal training session, and it tends to be one of the more rewarding parts of the job. Watching someone move from needing a design reviewed line by line to owning a whole system independently is a slower process than most people expect, but it's a real part of what this role is supposed to build over time.
Background required
A bachelor's degree is the baseline for this role. At the lead level, we're also looking for an advanced certification tied to whatever platform or domain someone's built their career around, whether that's a cloud provider certification or something more specialized depending on the systems they've worked with. We're less concerned about which specific credential someone holds than whether it actually reflects depth in an area we need on the team right now.
Eight years of experience is what we're asking for here. That's generally enough time for someone to have owned architecture decisions on at least one system that actually scaled past its original design, and to have lived with the consequences of an early decision that looked right at the time but caused problems two years later. That kind of hindsight is hard to fake in an interview. We tend to learn more from hearing someone describe a decision they'd now make differently than from a polished list of successful projects with no rough edges mentioned anywhere.
Skills
Core requirements are strong system design ability, a track record of setting coding standards that teams actually follow, real technical leadership experience, and hands-on familiarity with at least one major cloud platform. These four tend to show up together in candidates who've genuinely operated at this level before.
Beyond that, a specific cloud certification, AWS, Azure, or GCP depending on which platform we're discussing, would strengthen an application meaningfully. Experience with microservices or other distributed system patterns is a plus, and some working knowledge of security architecture helps too, since more design reviews these days include security considerations. Cost optimization experience, actually reducing infrastructure spend on a live system rather than just architecting for it in theory, tends to be underrepresented among applicants and stands out when it's there. If you've made a case to leadership to re-architect something purely on cost grounds and had it approved, that's worth mentioning specifically.
How the role works day to day
Naukri Mitra has seen a noticeable rise in architecture-level hiring out of Mohali's IT City corridor this year, and this particular role reports directly into engineering leadership rather than sitting under a single product manager. That structure gives the role real cross-team influence, but it also means decisions here carry more weight than they would at a more junior architecture position, and getting a call wrong affects more than one team's roadmap. Most weeks are split between design work, reviewing proposals from other teams, and conversations with leadership about where the technology roadmap needs to shift next. There's rarely a fully quiet week at this level, but there's also rarely a week that's entirely consumed by firefighting, which tends to be the balance most people at this stage are actually looking for.
Compensation and benefits
Along with base salary, this role includes:
- Health insurance
- Paid time off
- Performance-linked bonuses
- Relocation assistance for anyone moving to Mohali
- Accommodation support during the transition
Given the compensation level and seniority, the relocation package is designed to cover an actual move rather than a partial contribution, and performance bonuses are tied to concrete architecture outcomes rather than a generic annual review score. Health coverage extends to family members as well, which matters more at this career stage than it might earlier on.
Location and pay
This role is based on-site at IT City, Sector 82, Mohali, without a remote or hybrid arrangement. For experienced professionals evaluating technical architect jobs in Mohali specifically, this role sits near the top of what the local market currently pays for this level. IT City has become one of the region's more established tech corridors, with a growing concentration of established companies nearby. That density has also improved the area's overall infrastructure over the past few years, which helps anyone relocating from outside Punjab.
Applying
Send your application along with a description of the largest system you've architected from the ground up, including how it held up once real usage patterns emerged. The process includes a technical architecture discussion based on a real scenario, followed by a conversation with the engineering leadership team you'd be working alongside regularly. We'd rather spend that time on a real design problem than a series of abstract questions with no system attached.
