Senior Database Administrator

OCTAGOS HEALTH, INC.Houston, TX
5d

About The Position

Octagos is modernizing remote cardiac monitoring with AI-powered automation, seamless EHR integrations, and accuracy proven in high-volume, real-world clinics. Atlas AI™ triages cardiac device transmissions to filter nonactionable alerts and highlights the events that need true clinical attention. Through our Two-Brain Approach™ – combining Atlas AI™ with IBHRE-certified oversight – Octagos delivers 99%+ accuracy, sensitivity, and specificity for near-perfect clinical performance. With fast bi-directional EHR integrations, and flexible, cost-effective implementation, Octagos helps clinics scale care efficiently without compromise. Recognized by TIME and Statista as one of the World’s Top HealthTech Companies 2025, Octagos is redefining how cardiac care is delivered. Role Summary We are looking for a dynamic Database Administrator who can serve as both a hands-on performance engineer and a strategic data architect for our Azure SQL Server environment. Our database tier spans multiple schemas (production, Power BI reporting, analytics, ETL procedures, audit, support, and watchtower schemas), powers 300+ stored procedures, views, and scheduled Azure Elastic Jobs. We are in the middle of a comprehensive data architecture modernization effort that includes table decomposition, view rationalization, read/write separation, Redis caching integration, and event-driven ingestion. This role will be central to that transformation. The ideal candidate is not someone who simply keeps the lights on. We need a DBA who thinks in data models, designs for query performance from day one, establishes and enforces coding standards that prevent tech debt at the SQL layer, and partners with application engineers to ensure the full stack (SQL to C# Dapper to Angular) is aligned, performant, and maintainable. You will set the standard for how the team writes, reviews, and optimizes SQL.

Requirements

  • 10+ years of experience as a DBA or Senior DBA, with at least 2 years managing Azure SQL Database or Azure SQL Managed Instance in a production SaaS environment.
  • Proven track record of designing and evolving data architectures: table decomposition, schema normalization, denormalization strategies for reporting, and migration planning across hundreds of dependent database objects.
  • Deep expertise in T-SQL performance tuning: execution plans, index strategies (clustered, non-clustered, filtered, covering, indexed views), wait statistics, Query Store, parameter sniffing diagnosis, and Resource Governor.
  • Strong experience with stored procedure development following structured patterns (SET NOCOUNT ON, TRY/CATCH, parameterized queries, pagination with OFFSET/FETCH or keyset) and the ability to establish and enforce these standards across a team.
  • Ability to optimize complex views with 10 to 15+ joins, diagnose nested view performance degradation, flatten view-on-view chains, and recommend indexed view strategies for high-read workloads.
  • Experience authoring SQL development standards, style guides, and review checklists that are adopted by application engineering teams.
  • Hands-on experience with Azure database services: elastic pools, geo-replication, automated backups, threat detection, auditing, and cost optimization.
  • Solid understanding of HIPAA technical safeguards, encryption requirements, and audit logging for healthcare data at the database tier.
  • Experience with CI/CD-based schema migrations (DbUp, Flyway, or similar) and the discipline to assess blast radius across dependent stored procedures, views, and application-layer DTOs before every migration.
  • Familiarity with Dapper ORM or other micro-ORM data access patterns, including multi-mapping, Dynamic Parameters, and column-to-property mapping nuances, with the ability to partner with application engineers on data access optimization.
  • Strong written and verbal communication skills; comfortable collaborating with a distributed engineering team across US and India time zones and presenting architecture recommendations to engineering leadership.

Responsibilities

  • Own and drive the data architecture strategy for the platform, including the ongoing Transmission table decomposition, schema normalization, and entity relationship optimization across the Clinic, Patient, Device, and Transmission hierarchy.
  • Lead view rationalization across 100+ views: identify and eliminate redundant views, flatten deeply nested view-on-view chains that degrade optimizer effectiveness, and consolidate overlapping views into well-designed base views with clear single-purpose contracts.
  • Design and implement read/write separation strategies, including Redis caching layer integration for high-read, low-write data such as clinic settings, lookup tables, and device metadata.
  • Architect the evolution of the analytics ETL pipelines, stored procedures, consumption patterns and Azure Elastic Jobs that drive reporting.
  • Evaluate and recommend event-driven data ingestion patterns (Azure Service Bus, Event Grid) to replace polling-based data flows and reduce latency in the transmission processing pipeline.
  • Conduct proof-of-concept testing for schema changes (e.g., extension tables vs. EAV patterns) and present data-driven recommendations to engineering leadership with migration paths and rollback plans.
  • Manage schema evolution using DbUp migrations, ensuring backward compatibility, zero-downtime deployments, and a documented blast-radius assessment for every migration that touches dependent stored procedures, views, C# Dapper mappings, DTOs, and Angular interfaces.
  • Maintain a living data dictionary and entity relationship documentation covering all schemas (dbo, pbi, analytics, audit, support, watchtower), key tables, column-level lineage, and cross-schema dependencies.
  • Establish continuous performance tuning practice. Proactively identify and resolve slow queries, blocking chains, deadlocks, and resource bottlenecks across stored procedures and views before they impact clinical operations.
  • Analyze execution plans, leverage Query Store for regression detection, and maintain index health (rebuild/reorganize schedules, statistics freshness) across high-volume tables including Transmission, Transmission Status Map, Patient, and Patient Device Information.
  • Develop and maintain an index strategy covering clustered, non-clustered, filtered, and covering indexes. Evaluate indexed views for high-read-frequency reporting views. Track index usage stats and remove unused indexes that add write overhead.
  • Partner with .NET engineers to optimize Dapper-based data access patterns: diagnose column-alias mismatches that cause silent nulls, eliminate implicit type conversions that bypass index seeks, tune multi-mapping queries and Dynamic Parameters usage.
  • Optimize Hangfire job-related queries and the analytics ETL pipeline to ensure scheduled jobs complete within their time windows without competing for resources with real-time portal queries.
  • Enforce sargable query patterns by identifying and refactoring anti-patterns such as functions on indexed columns in WHERE clauses, cursors used for row-by-row processing, SELECT in stored procedures, and NOLOCK hints applied without DBA approval.
  • Own tempdb contention management: identify procedures creating excessive temp table churn, recommend CTE or table variable alternatives for small datasets, and monitor tempdb allocation wait stats. Conduct periodic full-environment performance reviews: top-N slowest queries, top-N resource consumers, wait stats analysis, plan cache bloat, and parameter sniffing hotspots. Deliver findings and remediation plans to the engineering team quarterly.
  • Define and enforce stored procedure standards across the engineering team: SET NOCOUNT ON, SET XACT_ABORT ON with transactions, TRY/CATCH error handling, proper parameterization, pagination with OFFSET/FETCH or keyset, and the standards naming convention.
  • Author and maintain a SQL development style guide covering naming conventions for all object types (stored procedures, views, functions, indexes, schemas), parameter design, error handling patterns, transaction scoping rules, and comment/documentation requirements.
  • Enforce standard active-record filters across all data-access objects and build automated checks to detect missing filters in new or modified stored procedures.
  • Establish code review standards for all SQL changes: require execution plan review for any query touching high-volume tables, mandate index impact assessment for schema migrations, and enforce consistent use of time zone conversion patterns (AT TIME ZONE) for SessionDate display.
  • Implement anti-pattern detection as part of the CI/CD pipeline or periodic audit: flag cursors, SELECT , missing SET NOCOUNT ON, string-concatenated dynamic SQL, functions on indexed columns in WHERE clauses, and transactions wrapping read-only queries.
  • Enforce cross-layer data structure alignment as a standard practice: SQL column types/nullability must match C# DTO properties, Dapper column aliases must match C# property names, and enum/lookup table values must stay synchronized across SQL, C#, and Angular layers.
  • Govern the analytics schema pattern, create and maintain stored procedure and view templates that the engineering team can use as starting points, ensuring every new database object follows established patterns from day one.
  • Administer and monitor MySQL and Azure SQL databases across development, staging, and production environments, ensuring 99.9%+ uptime for a platform that processes cardiac device transmissions around the clock.
  • Manage capacity planning, elastic pool sizing, and Azure SQL tier optimization, balancing performance against cost as clinic onboarding accelerates.
  • Own backup and restore strategies, point-in-time recovery testing, and disaster recovery runbook maintenance for databases containing PHI.
  • Monitor and triage performance alerts using Azure Monitor, Application Insights, and custom OpenTelemetry telemetry dashboards.
  • Coordinate maintenance windows for index rebuilds, statistics updates, and schema migrations with zero downtime to clinical operations.
  • Implement and enforce HIPAA-compliant data access controls, auditing, and encryption (TDE, Always Encrypted where applicable) across all schemas.
  • Manage database-level permissions, row-level security, and service account credentials in alignment with SOC 2 Type II requirements.
  • Ensure PHI never appears in stored procedure PRINT/RAISERROR messages, dynamic SQL trace outputs, plan cache, error messages, or URL parameters.
  • Participate in security audits, vulnerability remediation, and PHI exposure assessments at the database tier.
  • Execute and extend the data quality playbook including automated SQL checks, KPIs, and remediation runbooks that monitor data integrity across the Clinic, Patient, Device, Transmission hierarchy.
  • Build and maintain database health dashboards covering query performance, wait statistics, DTU/vCore utilization, job success rates, tempdb contention, and blocking/deadlock trends.
  • Instrument custom telemetry events at the database layer integrated with the platform’s OpenTelemetry and Application Insights observability stack.
  • Serve as the database subject-matter expert across the engineering organization, supporting US (Houston) and India development teams.
  • Contribute to architecture decision records (ADRs) for database-impacting changes, including schema migrations, index strategies, and caching layer design.
  • Document database objects, data flows, schema dependencies, stored procedure inventories, and operational runbooks in the team wiki (Azure DevOps Wiki / GitHub Wiki).
  • Participate in sprint ceremonies, root-cause analysis (RCA) reviews, and cross-functional working sessions with application engineers, QA, and the data team.
© 2024 Teal Labs, Inc
Privacy PolicyTerms of Service