Database Engineer​/Developer - terra

Ontario hospitals lose funding they are entitled to because of gaps in how care gets coded and reported. 3terra builds Data Quality Assist, the platform roughly 50 community hospitals use to find those gaps and close them. Better data means better funded care, and our work shows up in hospital budgets across the province.

We are now building something new. A multi-tenant datastore that will let hospitals benchmark their performance against peer organizations, across outcome metrics, quality based procedures, and emergency department metrics. Today it is a prototype and a set of screen designs with no data model underneath it. We are looking for the person who will design and build that.

You will own our data layer. That means the schemas, the stored procedures, the reporting abstractions, and the pipelines that bring hospital EMR data in from Meditech, Cerner, and soon Epic. You will also work in the .NET services and APIs that sit on top of it.

We are a team of ten, which means the work is broad and the distance between you and the people using it is short. You will engage with the coding and decision support professionals in hospitals whose day gets better or worse depending on what you build. You will report to our Engineering Lead and work alongside two Senior Software Developers, our Senior Product Manager, and our QA and client teams.

• The data model and aggregation layer behind our new benchmarking platform, including peer grouping and cross-organization comparison
• Schema design and complex T-SQL across DQA and our reporting framework
• EMR integration: source-to-target mapping and extraction pipelines from hospital reporting databases
• Performance across large hospital datasets, from execution plans to index strategy on read-heavy reporting workloads
• Leading our move to tool-based database version control and repeatable deployments
• Translating CIHI DAD and NACRS specifications and hospital business rules into SQL that has to be exactly right

• Five or more years building and owning data layers, with deep SQL Server experience: complex T-SQL, stored procedures, dynamic SQL, indexed and materialized views
• Real strength in performance tuning, execution plan analysis, and index design on large datasets
• Schema design judgment for both transactional and reporting workloads, and a working feel for when to normalize and when not to
• Comfort with JSON and semi-structured data in SQL Server, which we use heavily in reporting and in our load processes
• Experience building ETL or ELT pipelines that handle incremental loads, corrected data, and failures without manual intervention
• The ability to take an ambiguous requirement and turn it into something accurate, testable, and maintainable