Operating System Engineer
Required Background and Prior Experience
We are seeking a hands-on engineer who has previously built and supported production healthcare software comparable to VerityOS.
1. Relevant healthcare product experience — mandatory
The candidate must have personally developed substantial components of a live U.S. healthcare product involving one or more of the following:
* Practice management.
* Medical billing and revenue cycle management.
* EHR-connected patient engagement and operational workflows.
The product must have been used by real healthcare organizations. Coursework, prototypes, chatbot demonstrations, and internal proof-of-concept projects alone do not qualify.
2. Billing and RCM engineering experience — mandatory
The candidate must have hands-on experience implementing healthcare billing workflows, including:
* Claim creation/submission and acknowledgment or rejection handling.
* Electronic remittance or EOB processing and payment posting.
* Denial management and accounts-receivable workflows.
* Patient balances, adjustments, and reconciliation.
They must understand the distinction between charges, claims, payments, adjustments, and patient responsibility, and explain how their system prevented duplicate transactions and preserved financial history.
They do not need to have built every billing component independently, but must clearly identify the components they personally implemented.
3. EHR or healthcare-system integration experience — mandatory
The candidate must have delivered at least one production integration with an EHR, practice-management system, or healthcare clearinghouse.
Relevant experience includes approved APIs, FHIR, HL7, healthcare transaction interfaces, or secure data exchanges.
They must demonstrate experience with patient matching, synchronization, conflicting updates, failed transactions, and reconciliation. General API experience alone is insufficient.
4. Secure application architecture — mandatory
The candidate must have implemented:
* Role-based permissions and server-side access controls.
* Audit trails and sensitive-data protection.
* Separation of customer organizations’ data.
* Secure credential management.
* Backup, recovery, monitoring, and incident handling.
Experience with a platform serving multiple independent practices or customer organizations is strongly preferred.
5. Hands-on full-stack development — mandatory
The candidate must be able to personally design databases, develop backend services and user interfaces, write meaningful tests, deploy applications, and troubleshoot production issues.
This is a building role, not solely a project-management, consulting, or architecture role.
6. Production ownership — mandatory
The candidate must have supported a product after launch, including resolving incidents, releasing upgrades, managing database changes, and maintaining integrations.
They should be able to describe a significant production failure, its impact, how it was resolved, and what was changed to prevent recurrence.
7. Workflow automation experience — mandatory
The candidate must have built workflows involving task assignment, statuses, deadlines, escalation, document handling, and external-system events.
They must understand how to handle retries, duplicate events, incomplete information, and human review.
8. AI and communications experience — strongly preferred
Preference will be given to candidates who have deployed:
* AI document extraction with validation.
* Tool-using AI agents with defined permissions and human handoff.
* Voice agents or telephony integrations.
* Two-way SMS, e-fax, or secure patient messaging.
Candidates must distinguish production deployments from experimental projects.
9. Patient-facing and specialty experience — preferred
Relevant additional experience includes patient portals, caregiver access, scheduling, authorization workflows, procedure-resource scheduling, infusions, or other specialty-practice operations.
Neurology experience is valuable but not mandatory.
Evidence required with the application
Please provide two relevant project examples. For each, describe:
* The product and type of healthcare organization it served.
* Whether it reached production and how long you supported it.
* Your exact role and the components you personally built.
* EHRs, clearinghouses, or communications systems integrated.
* The scale of deployment, where disclosure is permitted.
* A difficult technical problem and how you resolved it.
* A professional reference who can verify your contribution.
Confidential client names may be withheld initially. Use anonymized descriptions and synthetic data; do not disclose patient information or proprietary code.