Database Administrator, Guindy — Chennai
A company in Guindy is hiring a full-time Database Administrator to work on-site, keeping production databases running and performing well for a growing set of internal and customer-facing applications. It's a hands-on role rather than a purely advisory one; whoever takes this job will be the person actually logging in when a query starts crawling or a backup job silently stops running.
Databases here support a handful of applications that the company's operations team relies on daily, so a slow query or a missed backup window doesn't stay invisible for long. The administrator in this role gets pulled in whenever performance dips, and part of the job is noticing those dips before someone else does, through routine monitoring rather than waiting for a complaint to land.
Responsibilities for this role cover:
- Designing and maintaining database structures for new and existing applications
- Optimizing queries and indexes to keep performance acceptable as data volumes grow
- Managing backup schedules, recovery procedures, and data security controls
- Monitoring database systems on an ongoing basis to catch reliability issues early
One recurring headache at growing companies is a table that was fine at ten thousand rows and starts timing out at ten million, usually right when nobody's watching. Catching that shift early, before it turns into a Monday-morning incident, is a big part of what separates a decent DBA from a great one, and it's exactly the kind of problem this role is built around. Query plans that looked fine in testing sometimes fall apart under real production load, and knowing why usually takes more than running EXPLAIN once and calling it done.
SQL fluency is required, along with hands-on database design experience, real comfort with backup and recovery procedures, and a working understanding of performance tuning. Candidates who can talk through an actual slow-query problem they've fixed, not just the theory behind indexing, tend to stand out here. A few additional skills would help but aren't required to apply: exposure to a cloud-hosted database service such as AWS RDS or Azure SQL, some scripting ability for automating routine maintenance tasks, and familiarity with a monitoring tool like Zabbix or Nagios.
Education-wise, the company wants a four-year undergraduate degree, generally in a computing-related field given the technical nature of the work, though the specific major matters less than demonstrating the database skills listed above. Experience-wise, they're asking for 30 months in a similar role, which usually means someone who's already handled a production database on their own rather than only assisting a more senior administrator.
Pay for the role goes up to ₹71,500 a month, on-site, full-time, in line with what database administrator jobs in Chennai tend to offer at this experience level. A handful of benefits come with the position:
- Health insurance
- Paid time off
- Provident fund contributions
- On-site cafeteria access and cab or commute support
Guindy sits in one of Chennai's more established IT corridors, close enough to the rest of the city that commuting usually isn't a major complaint for people already working in the area. Naukri Mitra tends to see a steady flow of database and backend roles posted from this part of Chennai, and this one leans toward someone early-to-mid career rather than a brand-new graduate or a ten-year veteran.
Nights and weekends aren't the norm here, but backup verification and occasional maintenance windows do sometimes fall outside standard hours, particularly around planned upgrades. That's treated as a normal part of the job rather than something flagged separately, and it tends to even out once a maintenance cycle wraps up.
Interviews typically start with a practical SQL and schema-design exercise before moving to a conversation about how the candidate has handled backup failures or performance problems in past roles. Someone who's actually restored a database from backup under pressure, rather than only reading about how the process works, usually has an easier time in that second conversation. The exercise itself runs about forty-five minutes and covers a realistic schema rather than an abstract puzzle, since the company would rather see how someone thinks through a real design tradeoff than watch them recall syntax from memory.
Applications are reviewed as they come in rather than in a single batch, so there isn't a fixed deadline attached to this posting. Anyone currently working nearby in Guindy or elsewhere in Chennai should have an easier logistical path into this one, though it's worth applying regardless of current location if the experience lines up.
The database environment is mostly relational, running on standard enterprise tooling rather than anything exotic, so someone with a typical SQL background should find the transition straightforward. A small amount of NoSQL work has crept in over the past year as one of the newer applications needed something more flexible for unstructured data, and the team would rather this person pick that up on the job than require it upfront.
Data security sits alongside performance and backup work as a real part of the role, not a side note. Access controls, encryption settings on sensitive tables, and audit logging all fall under this position's responsibility, particularly for the customer data the operations team handles. Getting those settings wrong doesn't usually cause an immediate outage the way a bad query might, but it creates risk that surfaces much later and is harder to walk back.
There's currently one other database administrator on staff, so this role isn't a solo function, though the two don't work identical shifts or cover identical systems. Coordination between them mostly happens through a shared ticket queue and a weekly sync rather than constant back-and-forth, which suits people who'd rather own their part of the system than co-manage every decision.
Growth from this position tends to go in one of two directions inside the company: toward a senior DBA role handling larger, more complex systems, or sideways into a broader infrastructure or backend engineering position for someone who wants exposure beyond the database layer. Neither path is guaranteed, but both have happened for people who started in a role shaped much like this one.
