Every database administrator interview eventually asks the same question: have you ever restored from backup, for real, under pressure? A resume can’t answer it. It lists PostgreSQL, SQL Server, Oracle, replication, and a stack of certs. The cover letter is where you tell the story that does — a recovery you executed, a restore test that proved the backups were good, or a performance crisis you traced to its cause and fixed.
That’s the letter’s job: one database problem you owned — a recovery, a query tuned from seconds to milliseconds, a high-availability setup that survived a failover, a major-version upgrade with no data loss — and which kind of DBA you are.
The examples below are grouped by the situations DBAs apply from and the contexts that change what a hiring manager screens for. Read the closest one, then write your own — a general cover letter structure guide covers the mechanics; this page is the DBA version. DBAs work closely with backend engineers, and the backend developer cover letter examples cover that side; the broader Software & IT cover letter examples cover adjacent roles.
What Hiring Managers Actually Read For
Two reads. A recruiter checks that your engine, your platform, and your certs match the posting; the DBA hiring manager checks that you protect the data, keep it fast, and stay calm when it’s slow or down.
The recruiter screen
- Engine and platform match: the database (PostgreSQL, MySQL, SQL Server, Oracle, or a NoSQL store), and whether it’s self-managed or a cloud service (RDS, Aurora, Cloud SQL, Azure SQL).
- The kind of DBA work you do: operations and administration, performance tuning, high availability and DR, cloud database ops, or database reliability engineering — stated plainly.
- Certs and level — a vendor cert (Oracle OCP, Microsoft, an AWS database specialty), where the role asks.
The hiring manager’s screen
- A recovery story — a real restore you ran, or a tested restore that proved the backup and the runbook work.
- A performance number — a query or a workload tuned, a p99 cut, a lock-contention or bad-plan issue fixed at the root.
- Change and safety discipline — an online migration on a large table, a major-version upgrade rehearsed and executed, patching without downtime, least-privilege access.
Skip “I’m passionate about data and databases” and open with a recovery, a tuning win, or an upgrade — and a number.
Database Administrator Cover Letter Examples by Situation and Context
Entry-Level / Junior Database Administrator
Best for: a first DBA title after a SQL-heavy analyst or developer role, a database cert, and a home lab with backups, replication, and restores.
This example leads with one thing the candidate owned — a tested restore, a backup schedule they set up, a slow query they fixed — names the analysis, and points at a documentation contribution. It’s honest about what’s still lab-scale. Full text below.
- Why it works: “I set up nightly backups and point-in-time recovery on our reporting Postgres, then actually tested a restore to a scratch instance and wrote the runbook — before that, nobody knew if the backups worked” is the story a DBA reviewer wants.
- Names the analysis — an execution plan, a missing index, wait events — instead of a feature list.
Database Administrator at a Product Company
Best for: DBAs who own the production databases for a product — backups, replication, HA, patching, tuning — applying to a similar role.
It leads with a database problem a reviewer can picture: a real recovery, a replication or failover setup, a query tuned from seconds to milliseconds, an online schema change on a huge table. It names the engine, the platform, and the number that moved. Full text below.
- Why it works: “our checkout query’s p99 had crept to 3s from a stale statistics issue and a missing partial index; I fixed both and it dropped to 40ms” pairs a claim with a mechanism.
- Names tested restores and online migrations as defaults, not selling points.
Developer or Sysadmin Moving Into Database Administration
Best for: backend developers or systems administrators moving into a DBA title, with strong SQL or infrastructure skills and growing database-ownership work.
The letter maps what transfers — a developer’s grasp of query plans and schema design, or a sysadmin’s feel for storage, memory, and what breaks in production — onto backups, replication, HA, and patching, points at the database tasks the candidate already owns, and is honest about which parts (recovery under pressure, the deep internals) are still being built.
Performance Tuning–Focused DBA
Best for: DBAs whose depth is making databases fast — query and index optimization, plan analysis, lock and I/O contention, workload tuning.
It leads with a performance problem solved at the root: a query rewritten and indexed for a real latency drop, a lock-contention issue diagnosed from wait stats and fixed, a workload change that cut database CPU enough to defer a hardware upgrade. It shows the candidate reads a plan and reasons about the optimizer, not just adds indexes. Full text below.
- Why it works: “I traced a nightly job’s slowdown to a plan flip after a data-skew change, pinned the plan and fixed the underlying statistics, and the job went from 90 minutes to 12” is diagnosis, not guesswork.
- Talks about the optimizer and wait events, which is what a tuning reviewer checks for.
High Availability / Disaster Recovery–Focused DBA
Best for: DBAs whose focus is keeping the database up and recoverable — replication topology, failover, backup strategy, RTO and RPO, restore testing.
It leads with an HA/DR outcome: a failover that worked when a primary died, a recovery executed inside the RTO, a restore-testing program that turned “we think the backups are fine” into “we know.” It names the replication setup, the RPO and RTO targets, and how often recovery is actually rehearsed. Full text below.
- Why it works: “when the primary’s storage failed at 2am, automatic failover promoted the replica in under 30 seconds and I had the old primary rebuilt as a replica before the morning” is HA that held under a real failure.
- Names a restore-testing cadence — “a monthly restore to a scratch instance, timed against the RTO” — not just a backup schedule.
Database Administrator Returning After a Career Break
Best for: DBAs coming back after a year or more away — caregiving, health, a layoff, time in another field.
This example closes the gap in the opening lines: what the time away was, that it’s over, and a concrete recent step — a cert renewed or added, a home lab rebuilt with a current engine version and cloud-managed instances, a short contract — that shows the skills are live. Then it moves to the solid DBA experience before the break.
Senior Database Administrator
Best for: DBAs with six or more years applying for a senior or a lead-track role.
The letter operates at the right altitude: the database estate owned over time, a standards and monitoring program built, junior DBAs mentored, and an unglamorous major-version upgrade or platform migration driven to completion across many databases with no data loss. It ends on how the candidate decides where to invest redundancy and tuning effort and where “good enough” is right. Full text below.
- Why it works: “I upgraded 40 Postgres instances two majors forward over a quarter, rehearsed on clones first, one maintenance window each, with a tested rollback — no data loss, no missed window” is senior scope.
- Describes a redundancy-versus-cost judgement in one line, not a claim to be “pragmatic.”
Answering a Specific Job Posting
Best for: a role you want specifically, where the posting spells out the engine, the platform, the replication model, and the compliance context.
It mirrors the posting without parroting it: the same environment the team runs (PostgreSQL on Aurora, a read-replica fleet, a SOC 2 context), the parts the candidate genuinely has, and one project close enough that the reader sees the fit. It leaves out everything the role doesn’t ask for. Full text below.
- Why it works: “You run PostgreSQL on Aurora with a read-replica fleet in a SOC 2 environment — that’s the exact setup I’ve run for three years” answers the screen in one line.
- Names the one gap honestly (Aurora, less bare-metal Postgres tuning) instead of hoping it won’t come up.
Cloud Database Administrator
Best for: DBAs whose work is managed cloud databases — RDS, Aurora, Cloud SQL, Azure SQL — the operations, the tuning within the constraints, and the cost.
The letter leads with a cloud-database outcome: a migration onto a managed service that cut operational load, tuning done within the parameter-group limits the platform allows, a cost reduction from right-sizing instances and storage, a Multi-AZ or global setup that held through an AZ event. It shows the candidate knows where the managed service helps and where it takes control away.
Database Administrator Changing Engines or Platforms
Best for: DBAs moving between engines (Oracle to PostgreSQL, SQL Server to MySQL) or platforms (on-prem to cloud-managed).
The letter separates what’s portable (relational theory, indexing and query plans, backup and recovery principles, replication concepts, capacity planning, change discipline) from what’s new (the engine’s optimizer behavior, its backup tooling, its replication mechanics and quirks), and is specific about the real work already done on the new engine — a lab, a migration project, a cert.
Self-Taught DBA Without a Degree
Best for: DBAs with no degree who came from development or operations and learned database administration through work and self-study, with two or more years of production database ownership.
It doesn’t apologize for the missing degree — it leads with the databases owned and the recovery and performance numbers, then names the certs and the fundamentals filled in deliberately (a database-internals book, a query-optimization course, a backup-and-recovery deep-dive). It picks a company whose interview is a practical scenario, not a credential check.
Database Reliability Engineer–Leaning DBA
Best for: DBAs moving toward reliability engineering — automation, infrastructure-as-code for databases, SLOs, self-service provisioning, treating the database platform as a product.
The letter names the shift: from hand-running database operations to codifying them. It points at what’s already automated — provisioning a new database from a template, automated backup verification, a self-service schema-migration pipeline, SLO dashboards — and is honest about which pure-dev parts (testing, deeper software design) are still growing.
Database / Data Platform Lead
Best for: senior DBAs applying for a database lead, data platform lead, or database manager role.
The letter bridges “already leading” to results: an estate-wide upgrade or migration delivered, database reliability and recovery confidence improved across teams, on-call made sustainable, DBAs mentored to senior. It’s clear the candidate wants to keep doing hands-on database work as a lead, and says why. Full text below.
- Why it works: “database-caused incidents across the estate dropped by about 70% over a year, and every critical database now has a restore tested monthly” is an estate-level result, not a personal task.
- States a position on staying hands-on — a real judgement a hiring manager decides candidates on.
Copy These Full Database Administrator Cover Letters
Six complete letters for the situations DBAs most often write from. Each is one page, three or four short paragraphs, addressed to a named person, with one database problem and a number. Copy the closest one, then swap in your own engine, project, and company research — a reviewer can tell a real letter from a filled-in template within two lines.
1. Entry-level — a restore you actually tested
Write this one when the role would be your first DBA title. It leads with one thing you owned — a tested restore, a backup schedule, a query fixed — the analysis you did, and a runbook.
Dear Ms. Reyes,
I’m applying for the Junior Database Administrator position at Redwood Systems. I’ve spent two years as a data analyst who wrote a lot of SQL and gradually took on the care of our reporting database, and I run a home lab with PostgreSQL replication, backups, and restores.
The thing I’d point to: our reporting Postgres had backups configured but nobody had ever tested a restore. I set up proper nightly base backups plus WAL archiving for point-in-time recovery, then actually restored to a scratch instance, verified the data, timed it, and wrote the runbook. It took 40 minutes, which is fine for that database — but before, we didn’t know. I also fixed a dashboard query that took 8 seconds: the plan showed a sequential scan on a 20-million-row table, I added a partial index for the common filter, and it dropped to 60ms.
Where I’m still building is recovery under real pressure and the deeper engine internals. I’m applying to Redwood because the role is a real step into database administration with senior DBAs to learn from.
Thank you for considering my application. I’d welcome the chance to walk through the restore test.
Sincerely,
Rhea Ashby
2. Product company — a performance crisis fixed at the root
A product-team letter leads with a real recovery or a tuning win with a mechanism, names the engine and platform, and treats tested restores as normal.
Dear Mr. Adeyemi,
I’m applying for the Database Administrator role at Ramp. I’ve spent four years owning the production databases for a fintech — PostgreSQL, mostly on self-managed instances with streaming replication — including backups, failover, patching, and tuning.
The work I’d point to: our checkout query’s p99 had crept from under 100ms to about 3 seconds over a few weeks. It was two things — the table’s statistics had gone stale after a data-distribution shift, so the planner chose a bad join order, and a partial index the query needed had been dropped in a migration. I fixed the statistics, restored the index, and set autovacuum thresholds so it wouldn’t recur; p99 went back to 40ms. Separately, I run a monthly restore test to a scratch instance, timed against our RTO, so the backups are proven, not assumed. Schema changes on the big tables go out online, in batches, behind a flag.
I reach for the plan and the wait stats before I reach for a new index. I’m applying to Ramp because the data is money and correctness and speed both matter.
Thank you for your time. I’d welcome an interview.
Sincerely,
Mira Yates
3. Performance tuning — diagnosis, not guesswork
A tuning-focused letter leads with a performance problem traced to its cause through plan and wait analysis, with a workload-level number.
Dear Ms. Okafor,
I’m applying for the Database Performance Engineer position at Timescale. I’ve spent four years as the DBA teams call when the database is slow, across PostgreSQL and SQL Server, and reading a plan and the wait events is most of what I do.
The case I’d point to: a nightly aggregation job that had run in 15 minutes for a year suddenly took 90. The plan had flipped — a data-skew change made the optimizer pick a nested loop where a hash join was right. Rather than just hint it, I fixed the underlying statistics and the extended stats on the correlated columns, and added a small covering index; the job went back to 12 minutes and stayed there. In another case, high lock waits on a hot table turned out to be a long-running reporting transaction holding a share lock — I moved reporting to a replica and the contention disappeared. Over a year of this kind of work I cut our primary’s CPU enough that we deferred a planned upgrade.
I don’t add indexes hoping; I read the plan and the wait profile first. I’m applying to Timescale because performance is the product and it’s the work I’ve gone deepest on.
Thank you for your consideration. I’d welcome an interview.
Sincerely,
Quinn Kade
4. HA / DR — a failover that held under a real failure
An HA/DR letter leads with a failover or recovery that worked when it mattered, and names the restore-testing cadence.
Dear Mr. Larsson,
I’m applying for the Database Reliability position at Fastly. I’ve spent five years focused on keeping databases available and recoverable — replication topology, failover, and a real restore-testing program — for a high-traffic marketplace on PostgreSQL.
The night I’d point to: the primary’s storage array failed at 2am. Automatic failover promoted the synchronous replica in under 30 seconds, the application reconnected, and the only customer impact was a few seconds of errors. By morning I’d rebuilt the failed node as a new replica and we were back to full redundancy. That worked because we’d rehearsed it — I run a controlled failover test every quarter and a restore to a scratch instance every month, timed against our 15-minute RTO and one-minute RPO. Before I set that up, the team believed the backups were fine; now we know, because we’ve watched them work.
I treat “we think it’s recoverable” as an incident waiting to happen. I’m applying to Fastly because the scale makes reliability genuinely hard and it’s the work I want to keep doing.
Thank you for your consideration. I’d welcome an interview.
Sincerely,
Alba Halloran
5. Answering a specific posting — mirror the environment
Write this when the posting names its engine, platform, and compliance context. Match what you genuinely have, name the one gap, and leave the rest out.
Dear Ms. Bello,
I’m applying for the Database Administrator position at Vanta. Your posting describes PostgreSQL on Aurora with a read-replica fleet, in a SOC 2 environment with audited access — that’s the exact setup I’ve run for the last three years.
At my current company I own our Aurora PostgreSQL estate: a writer and four read replicas, with the read traffic split by workload. I manage the parameter groups within what Aurora allows, I own the failover testing and the cross-region backup, and I keep our access model least-privilege with quarterly reviews that export cleanly for the auditor. Last year I migrated our largest database onto Aurora from self-managed Postgres with about two minutes of write downtime using logical replication for the cutover.
The one gap against your posting: I’ve been on Aurora, so I’m less current on bare-metal Postgres tuning — some of the knobs Aurora manages for you. The fundamentals carry and I’ve kept a self-managed lab, but I’d rather name it. I’m applying to Vanta because the environment and the compliance context match my experience closely.
Thank you for your time. I’d welcome an interview.
Sincerely,
Dahlia Okafor
6. Database lead — estate reliability up, DBAs grown
A lead letter bridges “already leading” to results: an estate migration delivered, reliability and recovery confidence up across teams, DBAs promoted — plus a position on staying hands-on.
Dear Mr. Feld,
I’m applying for the Data Platform Lead position at PlanetScale. I’ve been a senior DBA on a four-person team for four years and effectively the lead for the last eighteen months — running the upgrade roadmap, the on-call rotation, and the standards for an estate of about 60 databases across PostgreSQL and MySQL.
The results I’d point to: I led an estate-wide upgrade that took every database at least one major version forward, rehearsed on clones, one maintenance window each, with a tested rollback — no data loss and no missed window. I put a standard in place that no database is “production” until it has monitoring, a tested restore, and an owner, and database-caused incidents across the estate dropped by about 70% over the following year. Every critical database now has a restore tested monthly, automatically. I rebuilt the on-call so it’s sustainable. Two DBAs I’ve mentored moved up to senior.
I still take the hard recoveries and the deep tuning myself; a database lead who’s stopped doing the work loses the instinct for what’s risky. I’m applying to PlanetScale because the product is databases and the scale is real.
Thank you for your consideration. I’d welcome an interview.
Sincerely,
Dahlia Iversen
How to Structure a Database Administrator Cover Letter
One page, three or four short paragraphs, addressed to a person where you can find one — the hiring manager or the recruiter by name. The opening names the role, the kind of DBA work you do, and one database problem you solved. The middle carries the evidence: your current work, one problem with a root cause and a number, a recovery or restore-testing story, change discipline, the engine and platform you run. The close names why this team and asks for the interview. Start from an ATS-friendly cover letter template so the formatting parses cleanly.
Dear Ms. Park,
I’m applying for the Database Administrator role at Stripe. I’ve spent three years owning our PostgreSQL estate — streaming replication, monthly tested restores, online migrations — and last quarter I cut our busiest endpoint’s database time from a 2s p99 to 35ms by fixing a stale-statistics plan flip and a missing partial index.
Dear Hiring Manager,
I am a passionate database administrator with expertise in Oracle, SQL Server, MySQL, PostgreSQL, MongoDB, Cassandra, replication, clustering, backup and recovery, performance tuning, indexing, partitioning, and high availability, holding OCP and MCSA, seeking a challenging role.
The Anatomy of a Database Administrator Cover Letter
The opening (2–3 sentences). Role, the kind of DBA work you do, and one database problem you solved with a result. If someone referred you, name them first. Don’t spend this paragraph on your fascination with data.
Dear [hiring manager’s name],
I’m applying for the [exact role title] position at [company]. I’ve spent [N years] owning [what — the production databases / HA and DR / the cloud database estate] on [engine and platform] at [current or most recent employer], and [one database problem you solved and its result]. I’m looking to move to [one specific, true reason tied to this team].
The body (1–2 paragraphs). Your current role, then one problem a reviewer can picture: the symptom, the root cause, how you found it, and the fix. Add the recovery or restore-testing story, and the change discipline — the online migration, the rehearsed upgrade. Name the engine, the platform, and the scale.
On [current estate] I own [scope — instances, engines], on [platform].
The one I’d point to: [the symptom]. The root cause was [what — a stale plan, a missing index, lock contention, a full disk], which I found by [how — the execution plan, wait stats, logs]. I fixed it with [the fix], and [metric] moved from [before] to [after]. Recovery is proven, not assumed — [restore-testing cadence].
The close (2–3 sentences). Connect where you’re headed to what this team offers, thank the reader, and ask for the interview. One honest line about how you work — “I’d rather rehearse the upgrade on a clone twice than improvise it once in the window” — beats another adjective. Leave compensation out unless the posting asks.
I’m applying to [company] specifically because [one concrete thing — the scale, the engine, the way the team works], which is where I want to work.
[One plain sentence about how you work.] Thank you for considering my application — I’d welcome the chance to talk through [a problem from your letter].
Sincerely,
[Your name]
What to Quantify in a Database Administrator Cover Letter
A resume lists metrics as fragments. A cover letter makes them read like sentences a person would say. One number a reviewer can picture beats three claims of “ensuring database performance and availability.” If a project is hard to quantify, quantify its scope — “a major-version upgrade across 40 instances, one window each, no data loss.”
| What to quantify | Examples | How it sounds in a sentence |
|---|---|---|
| Recovery | RTO and RPO met, a real restore’s duration, restore-test cadence, a failover’s promotion time | “automatic failover promoted the replica in under 30 seconds” |
| Performance | Query or workload latency, a job’s runtime, p99 cut, database CPU reduced | “the nightly job went from 90 minutes to 12” |
| Availability | Uptime, database-caused incidents reduced, an outage class eliminated | “database-caused incidents across the estate dropped about 70%” |
| Scale & cost | Instances or databases managed, an upgrade or migration’s size, a cloud-database cost cut | “upgraded 40 Postgres instances two majors forward in a quarter” |
Common Mistakes on Database Administrator Cover Letters
Hiring managers read a lot of these, often right after an automated resume screen. The same few things quietly cost interviews.
Skip these
- Opening with “I’m passionate about databases” instead of a recovery, a tuning win, or an upgrade
- A wall of engines, features, and certs with no project attached to any of them
- Nothing about backups or recovery — the first thing a DBA reviewer looks for
- Describing responsibilities (“maintained and monitored database systems”) instead of one thing you fixed
- A tuning claim with no mechanism — “improved performance by 50%” with nothing about how
- Nothing about change discipline on a role where a bad migration means data loss
- Claiming an engine or platform the posting names but you’ve barely run — the scenario interview finds it
- The same letter to every company — obvious when the reason for applying is generic
Entry, Mid, Senior, and Lead Letters Are Read Differently
Same job family, four different reads. An entry-level letter is judged on one thing owned — a tested restore, a tuned query — a cert and a lab, and an honest gap. A mid-level letter is judged on a recovery or a performance fix with a mechanism and a number. A senior letter shifts to owning the estate, a standards and monitoring program, and a major upgrade or migration finished cleanly. A lead letter moves to estate-level reliability and recovery confidence, plus DBAs grown. Write to what the reader is deciding, and pair the letter with a resume built on the same evidence — the database administrator resume examples and the skills section guide cover that side.
- Entry-level: can this person protect a database and reason about a slow query? Lead with a tested restore or a tuning win, and one honest gap.
- Mid-level: can they run a recovery and fix performance at the root? Lead with the symptom, the cause, the fix, and the number.
- Senior: can they own the estate and run a clean upgrade? Lead with the estate owned, a standards program, a major migration finished.
- Lead: can they move estate-level reliability and keep DBAs? Lead with incidents down and recovery proven across the estate, and promotions.
Which Engine, Platform, and Practices Belong in the Letter
Name what the posting names, and only claim the depth you have. Keep the rest for the resume.
- Engine and platform: the database the role uses (PostgreSQL, MySQL, SQL Server, Oracle, or a NoSQL store) and whether it’s self-managed or a cloud service (RDS, Aurora, Cloud SQL, Azure SQL) — with a project attached.
- Core DBA areas: backup and point-in-time recovery, replication and failover, patching and major upgrades, monitoring, capacity planning, and access and encryption.
- Practices that changed your work: tested restores on a schedule, online schema migrations, rehearsed upgrades on clones, query-plan-driven tuning, database automation and infrastructure-as-code.
Anything you’re still learning is fine to say plainly: “I’ve run PostgreSQL for five years; the role is SQL Server, which would be new, but the relational fundamentals carry over and I’ve built a lab and started the Microsoft certification.”
Related Guides and Templates
Once the content is right, the format has to stay out of the way. These cover the pieces around the letter:
- Software & IT cover letter examples — the broader category, with more technical roles.
- Cloud engineer cover letter examples — the infrastructure side your databases run on.
- Professional cover letter templates — clean layouts that parse correctly in applicant tracking systems.
- Simple cover letter templates — when you want nothing between the reader and the words.
- All cover letter examples by profession — the same situation-by-situation approach for other roles.
- How to write a resume — the document your cover letter sits on top of.
Pairing this with a database administrator resume? Give that document the same scrutiny — our free ATS resume checker scores it in seconds.
Ready to write your Database Administrator cover letter?
Turn what you just read into a cover letter that gets you shortlisted for Database Administrator roles.
Create Cover Letter
Database Administrator Cover Letter FAQ
Do database administrators need a cover letter in 2026?
For a role at a company you care about, yes. DBA postings get heavy volume and resume screens are automated, so a short, specific letter is a cheap way to get a human to read you first — and to tell the recovery or tuning story a resume can’t, which is exactly what a DBA hiring manager is trying to assess. For a mass application through a job board it matters less, but when the form has a field for it, a good letter only helps.
Should I put a recovery story in the letter?
If you have one, yes — it’s the single most convincing thing you can say. A real restore executed under pressure, or a restore-testing program that proved the backups and the runbook work, tells a reviewer more than any list of features. If you haven’t done a production recovery, lead with a tested restore you ran in a lab or a lower environment and say so plainly.
How technical should the letter be?
Technical enough to be credible, not a full incident writeup. One problem told well — symptom, root cause via the plan or the wait stats, the fix — shows more than a paragraph of feature names. The reader is also checking that you can explain a database decision clearly, which matters when you’re advising developers on schema and query design.
How long should it be?
One page, three or four short paragraphs, about 250 to 350 words. A reviewer is often reading it between other tasks; a second page works against you.
Which certifications should I mention?
Name the ones the posting asks for or that materially change your candidacy — a vendor cert (Oracle OCP, a Microsoft SQL Server cert, an AWS database specialty) tied in one sentence to the work. Don’t list every badge; the resume holds those. A cert opens the door; the recovery or tuning story in your letter is what gets you the interview.
Do I need to tailor the letter to every company?
The opening reason and the company paragraph, yes — every time. The body evidence can stay largely the same, but swap which project you lead with to match the role: a recovery story for a reliability-focused role, a tuning story where the posting talks about performance, a migration story where they’re moving engines or moving to the cloud.
