Posting record
Open 12+ days
- DistantJob's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking DistantJob, so its true age is longer.
Last checked Nov 4, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat it asks of you
- 7+ years of experience
What the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
Q - What did the DBA say to the Developer?
A - It doesn't matter, he wasn't listening anyway
Q - What did the Developer say to the DBA?
A - It doesn't matter, the answer is "No".
Enough with the humor! Let's get to the point.
DistantJob is hiring a Senior SQL DBA for one of our clients, a growing US-based SaaS company serving 150+ enterprise clients on a highly customized, multi-tenant platform.
This isn't a "big data" role — the databases themselves are modest in size. The real challenge is complexity: each client runs on their own database instance, and while most of the schema and logic is standardized, a meaningful portion is customized per client. That means no two performance issues look exactly alike, and a one-size-fits-all runbook doesn't cut it here.
What you'll do
- Serve as the primary point of contact for critical database issues during US business hours, diagnosing and resolving performance, reliability, and availability problems
- Partner with developers to design, review, and optimize SQL queries, stored procedures, and database logic — and coach the team on performance best practices
- Proactively monitor database health across client environments, building alerting thresholds, runbooks, and dashboards to catch risks before they become incidents
- Own the database side of test-environment readiness — syncing test databases, validating configuration, and building automation to reduce manual setup work
- Review and approve database-related pull requests, maintaining coding standards and evaluating changes for performance, risk, and backward compatibility
- Perform routine database maintenance (backups, patching, capacity planning) during business hours to avoid production disruption
- Document recurring issues, resolutions, and operational procedures for the team
What we're looking for
- 7+ years of experience as a DBA, with real production support experience — not purely development-side database work
- Strong SQL Server / T-SQL skills, including query optimization and execution plan analysis
- Comfort working across highly customized, multi-instance environments rather than a single standardized database
- Genuine interest in both reactive incident response and proactive, collaborative dev support — this role is a mix of both, and that balance is expected to shift over time as processes mature
- Azure and .NET/ORM familiarity a plus
Schedule: Primarily CST hours (EST also considered) — this role exists specifically to extend coverage into the US afternoon.
Why this role: You'll join a team that's intentional about long-term growth for this position — not just filling a support ticket queue, but building someone into a trusted, embedded part of the development process.
If you meet these qualifications and are ready to contribute your expertise to a dynamic team, we encourage you to apply!
Something wrong with this posting?