Sr. Software Engineer - EMR

DataQ Health · Islamabad, Islamabad Capital Territory, Pakistan

What You'll Work On

• REST APIs in ASP.NET Core (.NET /C#)
• SQL Server stored procedures (Dapper, no ORM/EF — raw parameterized SQL against a large existing procedure library)
• React/Next.js (TypeScript) UI in a Redux Toolkit-based frontend (slices, async thunks, RTK patterns)
• Cross-cutting features that touch all three layers in the same change (e.g., a new field means a SQL Server column + stored proc change + C# model/service + API contract + Redux slice + React component)
• Integration work with third-party services (Twilio , Auth0 f, FHIR/HL7 interop touchpoints)

• Backend: C#, ASP.NET Core Web API, Dapper (or comparable micro-ORM), comfortable writing and debugging non-trivial T-SQL
• Database: SQL Server — stored procedures, joins, temp tables, window functions; comfortable working in a schema with no ORM-managed migrations (SSDT-style .sql scripts)
• Frontend: React, TypeScript, Next.js; state management with Redux Toolkit (or equivalent — Redux/MobX/Zustand experience that transfers)
• Git-based version control and working against a ticket/work-item system
• Ability to trace a bug through the full stack — given a UI symptom, find whether the root cause is in the component, the API, or the stored procedure

• Experience in healthcare software (practice management) or another
• Familiarity with PHI handling constraints: never logging PHI, treating test data carefully, understanding why schema changes need to be backward-compatible
• Experience with SMS/telephony integrations (Twilio or similar) and multi-scheme authentication (JWT, OAuth/Auth0)
• Comfortable reading and extending a large, imperfect legacy codebase rather than only greenfield work

• FHIR R4 / HL7 v2 / C-CDA / QRDA exposure (healthcare interop standards)
• Experience introducing automated testing (unit/integration) into a codebase that doesn't have much yet — this team is actively building that discipline out
• On-prem Azure DevOps Server (TFS) experience specifically, vs. cloud Azure DevOps