Full Stack Engineer

End-to-End Product Feature Delivery

Build RESTful APIs in Kotlin + Spring Boot, using the platform’s established architecture.

Implement React-based clinical UIs (web — Next.js/React recommended).

Collaborate with UX, architect, and QA to ship usable clinical features on time.

Work on feature verticals, e.g.:

Patient Record + Care Pathway Viewer

Therapist Session Workflow

Appointment / Scheduling Flow

Therapist Notes + File Upload Flows

Secure Patient Portal UX

Engineering Craft & Standards

Write clean, maintainable Kotlin & TypeScript — zero “feature-now-clean-up-later” attitude.

Reuse platform patterns — not reinvent.

Follow safe data access patterns defined by data specialist (ex: no unsafe pagination, no custom raw SQL unless approved).

Write meaningful unit tests + integration tests and collaborate tightly with QA automation.

Team Collaboration

Convert clinical/business requirements into clean, working user flows with minimal rework.

Contribute ideas — not just code — to improve therapist/patient experience.

Help catch UX edge cases (latency moments, bad data states, multi-user race cases).

Be a builder, not a ticket executor.

---

You MUST Have

3+ years experience writing production backend apps in Kotlin/Java (Spring Boot)

2+ years building React or similar SPA frontends

Real-world experience delivering business-critical / user-facing features end-to-end

Strong grasp of DDD-ish thinking, not just CRUD APIs

Knows when to defer to infrastructure/data rules (not a cowboy engineer)

Can turn Figma / requirement docs into working UI/API flows efficiently

---

Nice to Have

Experience with FHIR / healthcare / scheduling systems or case management platforms

Experience with React Query / SWR / Tanstack patterns

Ability to build usable UI with minimal supervision (NOT a UI designer)

---

Mindset / Personality Fit

You care deeply about usability, not just “API works”.

You are a multiplier, not territorial — you push the feature forward fast.

You love collaborating with product, architect, QA, and don’t see specs as “throw over the wall”.

You are biased toward shipping clean product, not shipping spaghetti.

---

What You Will NOT Be

Not purely backend-only or frontend-only specialized

Not an “API-only/no-UX” engineer

Not a data infrastructure person

Not a pixel-perfect UI frontend designer

You are the core product builder — someone who turns intent into working software clinicians actually use.