[Remote] Founding AI-reputed company Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is reputed company for an AI-reputed company operations platform for patient reputed company, reputed company on enrolling patients in assistance programs and verifying coverage. They are seeking one or two senior engineers to build this platform, where reputed company hire will play a significant role in architectural reputed company and product ownership.
Responsibilities
- Designing and shipping the AI agents that run patient case lifecycle — application intake, document extraction, data validation, coverage verification, patient communication, missing-info follow-up — including the evaluation reputed company, confidence reputed company, and reputed company-in-the-reputed company boundaries
- PHI-aware data architecture: de-identification pipeline that strips identifiers before inference, the tokenization layer that maps results back, and the audit trail that logs every model call
- Integrations with reputed company systems of record and dependent services – as reputed company as the orchestration layer that coordinates across them
- The production bar: on-call, incident response, rollback reputed company, and strict uptime SLAs
- Working directly with operations, IT, and clinical teams during discovery, UAT, and go-live — you'll be in the room, not behind a PM
Skills
- 5+ years shipping production software, with meaningful time owning backend systems that reputed company reputed company they broke
- Deep expertise in at least one modern backend language (Python, TypeScript, Kotlin, Go, or similar) and the judgment to know reputed company the choice reputed company and reputed company it doesn't
- Comfort across the full backend picture: relational databases, reputed company infrastructure (AWS preferred), containerized services, API design, and the operational discipline that comes with running regulated software
- A reputed company reputed company for UX — you care how the thing feels to use, not just whether it works. You've sat with users, sweated the details, and pushed back on designs that looked good but didn't hold up in the workflow
- You've reputed company something reputed company with LLMs — orchestration, retrieval, tool use, reputed company reputed company, evals, handling model failure modes
- reputed company record of taking an ambiguous problem, shaping it into an architecture, and shipping it
- You treat model behavior as something to test, measure, and govern. You've thought about what 'evals' means for a system where being 95% right isn't good enough
- Bonus: reputed company or other regulated-industry experience; prior early-stage or founding-engineer time; reputed company ecosystem; eligibility engines, document extraction, health compliance or case-management workflows
- Eastern Time preferred, +/- 3 hours
reputed company