This Lead MySQL Database Administrator position is on-site at Ranjit Avenue, Amritsar, and pays up to ₹150,000 per month, reflecting the seniority the role demands. It falls under Database Administration and reports to a team responsible for production systems that can't afford extended downtime.
Eight years of hands-on experience administering production database environments is the baseline expectation here. That number isn't a soft guideline. The employer has structured the role around someone who has already made the mistakes that come with running MySQL at scale and learned from them, someone who has already sat through a 3 a.m. replication failure and knows within minutes whether it's serious enough to page the rest of the team.
Day-to-day responsibilities
The work splits between keeping existing systems healthy and shaping how new ones get built. Core duties include:
- Designing and maintaining database structures across multiple production MySQL instances
- Optimizing slow-running queries and identifying indexing gaps before they become performance complaints
- Managing backup schedules, recovery testing, and overall data security posture
- Monitoring systems continuously for reliability, catching drift before it turns into an outage
- Setting up and maintaining replication topologies across primary and standby servers
- Mentoring junior database administrators and reviewing their schema and query changes before deployment
A production database outage doesn't wait for business hours. When one hits at 2 a.m., the lead is expected to diagnose it calmly and start working the problem without needing to wake someone more senior first. That's a big part of what the title actually means day-to-day.
Skills
Required, hands-on: MySQL administration at a deep level, strong SQL, replication setup and troubleshooting, backup and recovery procedures, and query performance tuning across large datasets. These aren't areas where surface familiarity is enough; the role assumes someone who has already debugged a replication lag issue under pressure and knows what actually causes one.
A few things beyond the core list would strengthen an application without being mandatory. Exposure to managed cloud database services such as Amazon RDS or Aurora for MySQL is increasingly important as more Amritsar-based companies shift their infrastructure off self-hosted servers. Familiarity with monitoring tools like Percona Monitoring and Management or Prometheus helps someone get productive faster. Scripting ability in Python or Bash for automating recurring maintenance tasks is the kind of thing that separates a good candidate from a great one. None of these three are gatekeeping requirements on their own, but a candidate who has all three tends to move through the interview process faster.
Education
A bachelor's degree, generally in computer science or information technology, is on the requirements list, though it serves more as a baseline checkbox than a deciding factor. Eight years running production MySQL systems weighs far more heavily in the actual hiring decision than which university name appears on a transcript.
Compensation and benefits
Pay tops out at ₹150,000 per month for this position, which is on the higher end for MySQL database administrator roles in Amritsar, given the lead-level scope. Alongside salary, the role brings health insurance coverage, paid time off, and performance-linked bonuses tied to system uptime and project delivery.
- Relocation assistance for candidates moving to Amritsar
- Accommodation support during the initial transition period
Naukri Mitra has posted this role on behalf of a Ranjit Avenue employer that is actively expanding its database operations team, and the relocation package reflects a genuine effort to attract experienced administrators from outside Punjab rather than limit the search to local talent alone.
Where the role is based
The position is on-site at Ranjit Avenue, Amritsar, Punjab, pincode 143001. This is not a remote or hybrid arrangement, and candidates evaluating MySQL database administrator jobs near Ranjit Avenue specifically should plan around a daily on-site presence rather than occasional office visits. For experienced professionals in Amritsar considering a move up to a lead-level position, the local market for roles at this seniority and pay band is fairly thin, which is part of why relocation support is built into the offer.
Amritsar's IT sector has grown steadily over the past few years, but most openings so far have clustered around mid-level development and support roles rather than senior database roles. That gap is exactly why this particular listing tends to draw interest from candidates currently working in Chandigarh, Ludhiana, or further afield in the NCR, several of whom end up relocating once they see the pay band matches what they'd expect from a larger city.
What the team looks like
The database team currently runs a mix of legacy MySQL instances that predate most of the current staff and newer systems built with replication and failover in mind from day one. Reconciling those two worlds, keeping the old systems stable while modernizing the new ones without breaking anything in between, is an ongoing part of the job rather than a project with a fixed end date.
Junior administrators on the team currently handle routine maintenance and smaller schema changes, which frees up this lead role to focus on architectural decisions, capacity planning, and the handful of genuinely difficult problems that arise when a database starts behaving in ways nobody quite expected.
How the role is measured
Performance here isn't judged purely on uptime numbers, though those matter. The team also looks at how quickly root causes are identified after an incident, how much query optimization work is done proactively rather than reactively, and whether the junior staff being mentored are actually improving over time. A lead who fixes every problem personally without building the team's capability underneath them isn't doing the full job, even if the servers stay up.
Capacity planning gets reviewed quarterly, with growth projections based on current transaction volume and the pace at which the company has been adding new product lines. Getting those projections wrong in either direction- under-provisioning and causing performance problems, or over-provisioning and wasting budget- falls squarely on this role.
Applying
Candidates should apply through the standard process listed in this posting, including a resume that specifically highlights production MySQL experience rather than general database exposure. Interviews typically involve a technical discussion around a real performance or replication scenario, since the hiring team is more interested in how someone reasons through a problem than in memorized syntax.
