Latent Defense
Software Engineer (Frontend)
About this role
Join a healthcare AI startup building modern clinical systems to replace outdated EHRs. You'll architect intuitive React-based interfaces that help providers and patients access critical healthcare data efficiently, directly improving patient care outcomes.
What you'll do
- Architect scalable React ecosystem for complex healthcare widgets and AI tools
- Design intuitive UI/UX for clinical workflows including Prior Authorizations and Appeals
- Implement interfaces for patient interactions prioritizing clarity and speed
- Collaborate with backend engineers to define APIs and frontend architecture
- Own frontend code quality and user experience standards
- Translate complex backend and AI functionality into accessible user experiences
What they're looking for
- React
- TypeScript
- Frontend architecture
- UI/UX design
- Command line proficiency
- Scalable application development
- Healthcare domain knowledge (bonus)
- EHR systems experience (bonus)
Benefits
- Work on mission-critical healthcare technology
- In-office culture in San Francisco
- Opportunity to impact patient care directly
- Exposure to clinical domain expertise
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Latent Defense
Latent Defense builds modern clinical AI systems designed to replace outdated EHRs and improve healthcare workflows for providers and patients. The company is hiring frontend engineers, DevOps infrastructure specialists, backend developers, and machine learning engineers to develop intuitive interfaces, ensure production reliability, power clinical data pipelines, and deploy personalized healthcare ML systems.
View all jobs at Latent DefenseLikely interview questions
- Tell us about a large-scale React application you've architected. How did you structure it to handle complexity and support rapid iteration?
- Describe your experience building interfaces that display complex, mission-critical data. How did you prioritize clarity and usability?