Role Overview
Our client is building a greenfield web platform that delivers modern, cloud-based experiences aligned with Sensei Cloud. The application is modular in nature and will grow over time.
As a Full-Stack Engineer with a frontend focus, you will be a core contributor shaping the user experience and frontend architecture from the ground up — while remaining capable of working across the entire stack when needed. Your primary ownership area is the React/TypeScript frontend: building customer-facing features, implementing responsive layouts, and integrating with the Rails API. You will also contribute to backend work as the team and product evolve.
This is a full-product ownership role in a HIPAA-regulated healthcare environment, requiring strong technical judgment, attention to compliance, and close collaboration with your fellow engineers and product stakeholders.
You will work within a Human → AI → Human engineering workflow, using AI tools to accelerate development while maintaining full accountability for code quality and correctness.
Key Responsibilities
Primary (Frontend)
- Design, build, and maintain React components for a dental practice scheduling application
- Implement responsive, mobile-first layouts using Tailwind CSS and standard breakpoints (sm, md, lg)
- Integrate frontend features with a Rails-based API using Axios and TanStack Query for data fetching, caching, and mutations
- Implement Azure AD B2C authentication using MSAL, including protected routes, token acquisition, and Axios interceptors
- Maintain clean, readable TypeScript code that conforms to ESLint and Prettier standards
Shared (Full-Stack)
- Contribute to Rails API endpoints, data models, and background jobs as needed
- Collaborate closely with backend-focused engineers and product stakeholders throughout feature development
- Participate in AI-augmented development workflows, reviewing and validating AI-generated code against acceptance criteria
- Follow Git best practices: feature branches, pull requests for all changes, and conventional commit messages
- Proactively update documentation when behavior or architecture changes