KASHII UPDATEZ Everyday Student Requirements & Python Coding Tutorials by Python Kashi
N #3172
Applications open Full-Time Job

Head of Engineering - EHR Integration

Xpertdox

  • Noida, India
  • 80 Lacs-1.25 Cr PA
  • 10-20 Yrs
  • Posted Today
HR
Recruiter contact
Recruiter / hiring contact
No public email in this post. Use a source-linked contact instead.

About the role

Head of Engineering: EHR Integration Pay: 80 to 120 lakh per year

Location

Noida, Uttar Pradesh, India Type: Full-time Hours: 12:30 PM to 9:30 PM IST Entity: XpertDox India Private Limited (XIPL) Department: EHR Integration On-site or remote: On-site, Monday through Friday Reports to: Chief Technology Officer About XpertDox XpertDox, Inc. is a physician-founded, venture-backed healthcare AI company headquartered in Scottsdale, Arizona, with a global delivery team in India. Our platform, XpertCoding, autonomously codes outpatient medical claims directly from clinical documentation using neural networks, machine learning, and natural language processing. We serve outpatient healthcare organizations in almost all 50 states, with deep expertise in Federally Qualified Health Centers (FQHCs), womens health and OB/GYN practices, and behavioral health providers.

Position Summary You own the integrations that move every XpertCoding claim from the EHR to submission. That covers the full portfolio of RPA and EHR integration across every supported EHR and client instance, and the reliability of the claims pipeline: scheduled runs, encounter pickup, coding handoff, claim creation, and submission. You decide how failures are detected, who responds, and what changes after an incident.

You lead the EHR Integration team and are responsible for its hiring, performance, standards, and code review. The bots and pipelines handle protected health information under XpertDoxs SOC 2 Type 2, ISO 27001, and HIPAA controls, and you hold the team to them. This is an architecture and leadership role.

The team writes the code. You decide what gets built, how, and in what order, and you review what ships. It is not for someone who wants to spend most of the week building bots, and it is not for someone who has only managed an RPA vendor.

Key Responsibilities

  • In this role you will: Own the architecture, roadmap, and delivery of RPA and EHR integration across every supported EHR and client instance.
  • Own the reliability of the claims pipeline from scheduled run to submitted claim.
  • Define the monitoring and alerting that surfaces failures in unattended bots the same day they occur.
  • Own incident response and root cause analysis for integration failures, and close every corrective action.
  • Set engineering standards for the code: version control, code review, testing, release discipline, and documented configuration changes before they reach production.
  • Lead the EHR Integration team: hiring, performance, standards, and code review.
  • Report delivery, risks, and capacity to the CTO on a regular cadence.

Required Qualifications

  • 10 or more years building production software. 3 or more years leading a software engineering team with direct responsibility for hiring, performance, and delivery.
  • Has owned production RPA bots or integration pipelines at scale, where failures had direct business impact.
  • Current architecture ability in Python for production services and integrations.
  • Production experience with AWS, MongoDB, and SQL databases.

Preferred Qualifications

  • EHR integration experience: HL7 v2, FHIR, or direct connections to major ambulatory EHR systems.
  • Experience with applications that handle protected health information or other regulated data.
  • Daily use of AI coding tools, such as Cursor or GitHub Copilot, to lead and raise the output of an engineering team.
  • Has built monitoring, alerting, and incident ownership for unattended bots or batch pipelines.
  • Location and Schedule This role is on-site at the XIPL office in Noida, Monday through Friday, 12:30 PM to 9:30 PM IST, to overlap with the Arizona workday.
  • It is not remote and not hybrid.
  • Candidates outside Delhi NCR must relocate to Noida before the start date.
  • Occasional travel to the Scottsdale, Arizona headquarters may be required; XpertDox may sponsor a B2 visa for that travel.
  • Compensation Base salary of 80 to 120 lakh per year, commensurate with experience.
  • Stock options.
  • Relocation assistance, reimbursed against receipts.
  • Benefits Health insurance, provident fund, and leave per XIPL policy.
  • Company cab service for all Noida employees.
  • To Apply Apply at https://careers.xpertdox.com/ .
  • XIPL is an equal opportunity employer.

Eligibility & process

Who can apply

Experience: 10-20 Yrs. Open to matching qualifications.

Skills & stack

EHR Review Code Review Integration Incident Rpa HL7 Python

Selection process

  1. Online Assessment / Technical Interview Rounds / HR Review

Prep kit

20 resources
Study material 4
Company-specific guides 4
Likely coding questions 4
Round-wise strategy 4
Round 1: Online Assessment (OA) Aptitude, Quantitative Logic & 2 Coding Problems Focus on accuracy and speed. Practice arrays, strings, and standard arithmetic puzzles.
Round 2: Technical Interview 1 Core Tech Stack (EHR, Review, Code Review, Integration, Incident, Rpa, HL7, Python) & Live Code Tracing Explain your thought process aloud. Analyze time & space complexities before coding.
Round 3: System Design & Problem Solving Database Schemas, APIs & Architecture Basics Clarify edge cases, diagram schemas cleanly, and discuss scalability trade-offs.
Round 4: HR & Cultural Fit Discussion Xpertdox Core Values, Learning Agility & Offer Terms Demonstrate passion, strong communication, and readiness for full-time collaboration.
Technical questions 5
Explain OOP (Object-Oriented Programming) principles with real-world examples in EHR. Answer
Model answer: 1. Encapsulation (data hiding via private fields/getters). 2. Abstraction (hiding implementation complexity). 3. Inheritance (code reusability). 4. Polymorphism (method overriding/overloading).
What is the time and space complexity of QuickSort vs MergeSort? Answer
Model answer: QuickSort: Average O(N log N) time, O(log N) space. Worst O(N^2). MergeSort: Guaranteed O(N log N) time, but requires O(N) auxiliary space.
Explain the difference between SQL Indexing (B-Tree vs Hash) and when not to use an index. Answer
Model answer: Indexes speed up SELECT queries via B-Trees. However, they slow down INSERT, UPDATE, and DELETE operations because indexes must be updated on disk. Avoid on low-cardinality columns (e.g., boolean flags).
What happens under the hood when you enter a URL in a browser? Answer
Model answer: 1. DNS lookup (resolves IP). 2. TCP 3-way handshake (SYN, SYN-ACK, ACK). 3. TLS negotiation for HTTPS. 4. HTTP GET request sent. 5. Server responds with HTML/CSS/JS. 6. Browser renders DOM & CSSOM tree.
What is the difference between REST and GraphQL APIs? Answer
Model answer: REST uses multiple fixed endpoints with possible over/under-fetching. GraphQL uses a single endpoint allowing clients to query exact fields in a single request.
Behavioural & HR questions 3
Why do you want to join Xpertdox as a Head of Engineering - EHR Integration?
Highlight Xpertdox's market reputation, recent tech innovations, and how your skills in EHR directly solve their team's objectives.
Describe a challenging bug or academic project roadblock and how you resolved it.
Use the STAR method: Situation (project context), Task (what needed solving), Action (specific tools/logic applied), Result (quantifiable positive outcome).
How do you handle strict deadlines or sudden scope changes?
Explain your prioritization strategy, proactive communication with mentors/peers, and agile mindset.
Xpertdox 80 Lacs-1.25 Cr PA
Recruiter Resume Apply
Chat Chat with Kashii