Overview

Technical Lead - Full Stack Developer

Responsibilities

• Own platform development end to end: requirement discussion, design, build, test, deploy, support.
• Analyze the existing ASP.NET v2 application - read legacy code, trace data flows, and determine what functionality must be preserved, replaced, or retired.
• Build and extend the Node.js and React v3 platform, closing feature parity gaps without disrupting live operations.
• Design, develop, and consume RESTful APIs, including integrations with clearinghouses, practice management systems, payer portals, and other third-party vendors.
• Write and optimize SQL queries and stored procedures for performance at production data volumes.
• Deploy and support applications on Microsoft Azure (VM and App Service); improve the deployment path toward automated CI/CD.
• Work directly with Operations, Quality, and the business owners to turn workflow problems into working software, and push back when a requested feature is not the right solution.
• Set and maintain engineering standards: code review, branching discipline, environment hygiene, and documentation of technical decisions.
• Handle production support for the applications you own, including triage of issues raised by operations.
• Mentor and technically direct additional engineers as the team grows.
• Apply data privacy and security practices appropriate to protected health information at every layer of the application.
• Backend: Strong hands-on experience with Node.js, JavaScript/TypeScript, ASP.NET, and C# is required. Knowledge of Python for tooling and automation will be an added advantage.
• Frontend: Strong experience in React, JavaScript, HTML, and CSS is required. Experience with Next.js, TypeScript, and reusable/component library development will be an added advantage.
• Database: Strong experience with Microsoft SQL Server, Stored Procedures, SQL query development, and query performance tuning is required. Knowledge of PostgreSQL and database schema migration tools will be an added advantage.
• Cloud: Hands-on experience with Microsoft Azure, particularly Azure Virtual Machines (VM) and Azure App Service, is required. Experience with Azure DevOps, CI/CD pipelines, and Infrastructure as Code (IaC) will be an added advantage.
• APIs & Integrations: Strong understanding of RESTful API design and consumption, JSON, and third-party/vendor API integrations is required. Knowledge of OAuth 2.0, token-based authentication, webhooks, and queue-based integrations will be an added advantage.
• Automation: Experience with Selenium or Playwright for browser-based automation, particularly payer portal and web application automation, will be an added advantage.
• Version Control & Build: Strong experience with Git, GitHub or Bitbucket, branching strategies, and code review practices is required. Knowledge of Docker and automated testing frameworks/test suites will be an added advantage.
• Development Tools: Proficiency in Visual Studio, Visual Studio Code (VS Code), SQL Server Management Studio (SSMS), and Postman is required. Experience with application performance monitoring, logging, and log aggregation tools will be an added advantage.

Qualifications

• You can navigate both codebases without assistance and have documented the v2 to v3 architecture, data model, and integration points.
• You have produced a written, evidence-based inventory of the remaining v2 to v3 feature gaps, sized and prioritized by operational impact, not by ease of build.
• You have identified the top reliability and performance issues in v3 as experienced by the operations team.
• A sequenced migration plan for retiring v2 is agreed with the business owners, with dates you set and commit to.
• The highest-impact feature gaps are closed and in production.
• A predictable release process is in place: version control discipline, code review, deployment steps that are repeatable and documented.
• Operations has a working channel to you for defects and requests, with visible turnaround.
• The v2 platform is decommissioned, or has a firm, funded, dated plan to be.
• v3 is stable enough that the business trusts it as the single system of record.
• Technical decisions and system behavior are documented well enough that the next engineer does not repeat your first 30 days.
• Bachelor's degree in Computer Science, Engineering, or a related field, or equivalent practical experience.
• 5-7 years of professional full-stack development experience.
• Demonstrated ability to work independently on an existing production codebase with limited documentation. This is the central requirement of the role and will be assessed directly during interviews.
• Excellent written and verbal English communication. You will be writing specifications, documentation, and status updates read by US-based stakeholders.
• Self-starting. You identify what needs doing and start doing it rather than waiting to be assigned work.
• Biased toward shipping. You get working software in front of users quickly and iterate, rather than perfecting in isolation.
• Comfortable with ambiguity. Incomplete requirements and undocumented legacy behavior are the normal condition here, not an obstacle you escalate.
• Direct. You raise problems early, give honest estimates, and say when something will not work.
• Accountable to outcomes. You measure yourself by what is live and working, not by tickets closed.
• Working understanding of HIPAA requirements as they apply to application design, access control, audit logging, and data handling.
• Completion of HIPAA and security awareness training on hire and annually thereafter.
• Execution of a confidentiality agreement covering PHI and company information.
• Successful background verification.
• Development and support performed only on company-approved systems and networks. No PHI on personal devices or unapproved storage.
• Adherence to access control, least-privilege, and audit requirements that flow down from our client agreements.
• US healthcare sector software: EHR or EMR systems, practice management systems, revenue cycle management, claims, or eligibility workflows.
• Healthcare data standards: EDI X12 (837, 835, 270/271), HL7, or FHIR.
• Legacy platform migration or modernization delivered to completion.
• Working in a small team where you were the most senior engineer on the system.
• Initial screen - background, motivation, and working style.