Baba
Fullstack Engineer
New YorkfulltimemidAdded 1 month ago
About this role
Baba is seeking a Fullstack Engineer to build and scale the platform powering healthcare advocacy for seniors. You'll own end-to-end development of web applications, APIs, data pipelines, and internal tools that help advocates coordinate care for thousands of patients.
What you'll do
- Build and maintain web applications, APIs, and backend services for the patient advocacy platform
- Design automated QA and monitoring systems to audit patient outcomes and advocate performance
- Develop internal tools and dashboards to streamline clinical workflows
- Architect data models and pipelines supporting a marketplace of advocates, providers, and patients
- Collaborate with founders and clinical team to translate operational challenges into shipped products
- Own features end-to-end from database design through UI implementation
What they're looking for
- Backend development (Python, Go, Rust, TypeScript, or similar)
- Full-stack web application development
- Distributed systems and data pipeline design
- API architecture and design
- Production debugging and reliability engineering
- System design and data modeling
- AI/ML interest (direct experience not required)
- Ability to work in ambiguous, early-stage environments
Benefits
- Medical, dental, and vision insurance
- 401k
- Flexible PTO
- Free lunch and dinner in office
- Relocation support to NYC
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.
Baba
Baba builds a platform that powers healthcare advocacy for seniors, enabling advocates to coordinate care at scale. The company is hiring Fullstack Engineers to develop and maintain web applications, APIs, data pipelines, and internal tools.
View all jobs at BabaLikely interview questions
- Walk us through a time you owned a feature end-to-end, from database design to UI. What challenges did you face and how did you handle them?
- Describe a production issue you debugged at a previous company. How did you approach it, and what did you learn?