Staff Database Engineer
robert halfSalt Lake City (UT)
Staff Database Engineer
Posted 3 days ago
robert halfSalt Lake City (UT)
SENIORITY
Lead
About the role
We are looking for a Staff Database Engineer to provide technical leadership for a global cloud data environment supporting large-scale, distributed business operations in Utah. This contract-to-hire position will focus on building and improving secure, highly available database platforms across AWS while partnering with engineering teams to strengthen performance, resilience, and scalability. The role is ideal for someone who brings deep database expertise, strong automation skills, and a practical approach to supporting modern data pipelines and enterprise applications.
Responsibilities:
Lead the design and ongoing improvement of multi-region database environments across AWS to support globally distributed workloads.
Administer and enhance a mix of relational and non-relational platforms, including Snowflake, PostgreSQL, DynamoDB, DocumentDB, Cosmos DB, and MongoDB.Drive database migration efforts between cloud platforms, regional deployments, and legacy environments while minimizing operational risk.
Improve system performance through thoughtful indexing, query refinement, capacity planning, and scalable data architecture decisions.
Strengthen availability and cost efficiency by tuning database platforms for enterprise-scale throughput, resiliency, and low-latency access.
Support data ingestion and ETL workflows by collaborating on services and orchestration tools used across cloud-based pipeline ecosystems.
Establish secure connectivity patterns, access controls, encryption standards, and secrets management practices for database services.
Build and maintain backup, recovery, and disaster preparedness processes, including point-in-time restore capabilities and continuity planning.
Expand monitoring and operational visibility using cloud and third-party observability tools, and take ownership of production incident response when needed.
Create and maintain technical documentation such as runbooks, operational procedures, and architecture decision records to support long-term platform reliability
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.