USA remote
Senior Software Developer - Databases
About this role
Role Overview When radiologists receive the right study at the right time, patients get answers faster, and behind every worklist, search, and assignment is a database that has to respond quickly and correctly. As a Senior Software Developer focused on the data layer of our InteleOrchestrator team, you’ll modernize the SQL Server-backed platform that streamlines radiology workflows for healthcare providers around the world.
You’ll write the code that changes the database: refactoring schemas and queries, untangling legacy data-access code, and moving it to type-safe, well-tested patterns while the system stays live for clinicians. This is a hands-on software development role, not a database administration role; your time will be spent in code, query plans, and pull requests rather than in backups, patching, or server operations. Success in this role means faster, safer, and more maintainable data access that reduces clinical burden and gives time back to the clinicians who depend on it.
Key Responsibilities Lead complex database refactoring across a large, mature SQL Server schema, including restructuring tables, keys, and indexes, retiring legacy structures, and backfilling and normalizing data, delivered as safe, incremental, version-controlled migrations (e.g., Liquibase) with no disruption to clinical users. Diagnose and resolve performance problems at the source by reading execution plans, rewriting queries to be sargable and set-based, replacing row-by-row processing with batched writes and properly indexed temp tables, and designing covering and filtered indexes based on real workload evidence.
Modernize the data-access layer by migrating legacy and inline SQL in PHP and C# code into type-safe Kotlin and jOOQ repositories, preserving behavior through characterization, regression, and scale testing. Harden data access for security and reliability by eliminating SQL injection through parameterization and automated checks, establishing consistent locking, isolation, and query-timeout conventions, and building query attribution and diagnostics that trace database load back to the code responsible for it.