Hey, we're looking for a Database Administrator to join us fully remote and full-time at $100,000 a year. If you're the kind of person who feels a little uneasy when a backup job hasn't been checked in a while, you'll probably fit right in here.
You'd be the one keeping our databases healthy day-to-day and stepping in quickly when something isn't. A lot of the job is quiet and preventive. Some of it shows up at inconvenient hours, which we'll get into further down.
This sits on the data side of engineering, working closely with application developers and the analytics team, but you'd own the database layer specifically rather than sharing that responsibility across the wider engineering group. It's a small team, so decisions about tooling and process land with you more than they would at a larger company with a dedicated DBA group.
What you'd own
- Maintain, secure, and optimize the company's production databases across their full lifecycle.
- Manage backup schedules and recovery procedures, and actually test that recovery works, not just assume it does.
- Troubleshoot performance issues before they lead to downtime by tracing slow queries or resource bottlenecks back to their causes.
- Keep availability high enough that other teams rarely have to think about the database layer at all.
A few months back, a client's nightly ETL job started silently failing partway through, and nobody noticed for almost a week because the job still reported success. That's the kind of failure mode this role is built to catch early, monitoring that actually questions whether a job did what it claimed, not just whether it exited without an error code.
Routine work fills most weeks, too: reviewing slow query logs, applying patches during a maintenance window, and adjusting indexes as tables grow beyond the size they were originally designed for. None of it is glamorous, but skipping it is usually how the dramatic failures start. A database that's been quietly neglected for a year tends to announce itself all at once, at the worst possible time.
Skills we need
- Strong SQL, well beyond basic querying
- Hands-on experience with at least one major database management system, MySQL, PostgreSQL, or Oracle
- Backup and recovery, including actual restore testing, not just backup configuration
- Performance tuning, from indexing strategy to query plan analysis
- Database security practices, covering access control and encryption at rest
A relevant certification- an Oracle credential, a PostgreSQL certification, or something similar- isn't required but does carry weight here. It's one of the clearer signals that someone has put in structured time with the fundamentals rather than picking things up entirely on the job. We'd rather see three years of solid production work without a certification than a certification with no production experience behind it.
Background
The minimum ask for education is a bachelor's degree, with a background in computer science or information systems being the most common fit for this kind of work. Beyond the degree, we're looking for three years of hands-on experience administering production databases, not a lab environment or a personal project, but systems that real users and real business processes depended on.
Naukri Mitra hears from many candidates who are strong on the SQL side, but light on production experience, and that gap tends to matter more here than people expect. Production work carries a different weight than work in a sandbox, since a mistake affects people beyond you.
If most of your background is in one specific database system, that's not a problem. The core skills, indexing logic, transaction handling, and backup strategy transfer well between MySQL, PostgreSQL, and Oracle, even if the exact syntax differs.
Pay and what's included
The salary is $100,000 a year, paid in USD. A remote database administrator salary at this experience level typically falls within a comparable range, so this is in line with what a three-year DBA should expect. Occasional team-building events happen too, usually a couple of times a year, though nothing mandatory beyond that.
- Health coverage
- Paid time off
- 401(k) matching
- Certification support, covering exam costs or study materials for relevant credentials
- Paid holidays
Certification support is worth calling out twice. If there's a specific credential you've been meaning to get around to, this is a reasonable place to actually do it, with the company covering part of the cost.
A note on the schedule
Most days are calm. You're monitoring dashboards, handling scheduled maintenance, working through a queue of performance requests from other teams. It's not a role where you're constantly firefighting.
That said, databases don't fail on a convenient timeline, and this role includes rotating on-call coverage. When something breaks at 2 a.m., you're one of the people who might get paged, though the rotation spreads that load across the team rather than landing on one person every week.
On-call weeks are noticeably different from regular ones. You're expected to be reachable and near a laptop, and the pace shifts from proactive maintenance to reactive troubleshooting for that stretch. Most weeks won't involve an actual page, but the expectation to be ready is part of the job either way.
Work-from-home database administrator jobs like this one tend to suit people who don't mind the trade-off: quiet stretches most of the time, occasional urgency when it counts, and full remote flexibility the rest of the time.
Getting started here
If this sounds like your kind of work, whether you came up through a formal CS degree or found your way into database administration through operations or systems work, we'd like to hear from you. The path from an adjacent IT role into remote database administration usually runs through production experience specifically, more so than the exact job title sitting on a resume, and that's roughly how to become a remote database administrator without a traditional DBA title along the way.
Send a resume, and mention which database systems you've worked with most. This role is open to database administrator jobs worldwide, with no location restrictions beyond a reasonable overlap for on-call rotation. Applications are reviewed as they arrive, and a short note specifically about your backup and recovery experience will help us move faster in scheduling a first conversation.
