Frontend Engineer (React/Next.js)
Build fast, accessible, and reliable web experiences for patients and providers. You'll craft AI-assisted UX (explanatory, guardrailed), elevate Core Web Vitals, and ship with strong privacy & security defaults.
On This Page
Role overview
Ownership
Patient & provider journeys (discovery → evaluation → booking), account & messaging, content & search UX.
Architecture
Next.js SSR/ISR, routing, data-fetch strategies, error boundaries, streaming UIs, and graceful fallbacks.
Design system
Composable, accessible components; tokens; dark mode; localisation; robust empty & loading states.
AI-assisted UX
Explanatory AI features with retrieval and guardrails; measure quality, cost, and latency.
Collaboration
Partner with Product, Design, Backend, Security, and Provider Ops; write crisp RFCs and PRDs (tech sections).
| Area | Summary |
|---|---|
| Ownership | Patient & provider journeys (discovery → evaluation → booking), account & messaging, content & search UX. |
| Architecture | Next.js SSR/ISR, routing, data-fetch strategies, error boundaries, streaming UIs, and graceful fallbacks. |
| Design system | Composable, accessible components; tokens; dark mode; localisation; robust empty & loading states. |
| AI-assisted UX | Explanatory AI features with retrieval and guardrails; measure quality, cost, and latency. |
| Collaboration | Partner with Product, Design, Backend, Security, and Provider Ops; write crisp RFCs and PRDs (tech sections). |
What you'll build
AI UX patterns & guardrails
Curated answer
FAQ-like, non-diagnostic info from vetted content.
Retrieval-first; cite sources; no medical advice; escalation paths.
Summarizer
Condense long provider info or reviews.
PHI redaction; tone constraints; character limits; human spot checks.
Smart defaults
Pre-filled filters or messages.
Explainability; user control/undo; log decisions for audits.
Safety nudges
Risk-reducing hints (e.g., consultation prep).
Clear boundaries; non-prescriptive wording; rate-limit intrusiveness.
| Pattern | When to use | Guardrails |
|---|---|---|
| Curated answer | FAQ-like, non-diagnostic info from vetted content. | Retrieval-first; cite sources; no medical advice; escalation paths. |
| Summarizer | Condense long provider info or reviews. | PHI redaction; tone constraints; character limits; human spot checks. |
| Smart defaults | Pre-filled filters or messages. | Explainability; user control/undo; log decisions for audits. |
| Safety nudges | Risk-reducing hints (e.g., consultation prep). | Clear boundaries; non-prescriptive wording; rate-limit intrusiveness. |
Privacy boundary
No PHI or consumer health data to non-approved endpoints. Prefer retrieval of vetted content and clear hand-offs to providers.
Accessibility & performance
Testing & tooling
Type safety & lint
Strict TS, ESLint rules, pre-commit checks.
TypeScript, ESLint, Prettier
Unit & integration
Test critical logic and components; contract tests for data.
Jest, React Testing Library
E2E & accessibility
User-journey tests; a11y assertions in CI.
Playwright, axe checks
Visual regression
Stable snapshots for core components/pages.
Storybook + screenshot diffs
Observability
Web vitals, errors, traces; experiment flags.
Web-Vitals API, logging, feature flags
| Stage | What you'll do | Illustrative tools |
|---|---|---|
| Type safety & lint | Strict TS, ESLint rules, pre-commit checks. | TypeScript, ESLint, Prettier |
| Unit & integration | Test critical logic and components; contract tests for data. | Jest, React Testing Library |
| E2E & accessibility | User-journey tests; a11y assertions in CI. | Playwright, axe checks |
| Visual regression | Stable snapshots for core components/pages. | Storybook + screenshot diffs |
| Observability | Web vitals, errors, traces; experiment flags. | Web-Vitals API, logging, feature flags |
Success metrics
Core Web Vitals
% of pageviews in "good" for LCP/CLS/INP.
No regressions post-feature; monitor by route.
Accessibility score
Automated + manual checks passing rate.
Keyboard & SR parity for critical flows.
Error rate
Front-end error events per 1k sessions.
Release gates on spikes; fast rollback.
Conversion
Search → inquiry → booking funnel lift.
Maintain safety/compliance signals.
AI UX quality
Offline eval pass rate; cost/latency SLO.
No medical advice; explainability present.
| Metric | Definition | Guardrails |
|---|---|---|
| Core Web Vitals | % of pageviews in "good" for LCP/CLS/INP. | No regressions post-feature; monitor by route. |
| Accessibility score | Automated + manual checks passing rate. | Keyboard & SR parity for critical flows. |
| Error rate | Front-end error events per 1k sessions. | Release gates on spikes; fast rollback. |
| Conversion | Search → inquiry → booking funnel lift. | Maintain safety/compliance signals. |
| AI UX quality | Offline eval pass rate; cost/latency SLO. | No medical advice; explainability present. |
Requirements
Must-have
- 3+ years building production React apps with TypeScript.
- Next.js SSR/ISR experience; routing, data-fetching, caching strategies.
- Accessibility fundamentals (WCAG), semantic HTML, keyboard flows.
- Performance literacy (CWV), profiling, and pragmatic optimization.
- Clear communication and collaboration with Design/Backend.
Nice-to-have
- Design-system work (tokens, theming, Storybook).
- AI UX experience (retrieval-first patterns, guardrails, evals).
- Experience with experimentation, analytics, or feature-flagging.
- Healthcare marketplace or trust & safety context.
| Must-have | Nice-to-have |
|---|---|
|
|
Hiring process
Apply
Resume/CV + brief note on a performance/a11y win and an AI UX decision you made.
2–5 business days
Screen
30 min on React/Next fundamentals and product instincts.
~1 week
Deep dive
Architecture & trade-offs; small code walkthrough; design system discussion.
~1 week
Practical
Time-boxed task or prior work review (includes a11y/perf and a light AI-UX prompt/eval step).
3–7 days
Panel
Cross-functional; collaboration and product sense.
~1 week
Offer
Comp band, benefits, start date. Background check post-offer where lawful.
48–72 hours
| Step | What to expect | Typical time |
|---|---|---|
| Apply | Resume/CV + brief note on a performance/a11y win and an AI UX decision you made. | 2–5 business days |
| Screen | 30 min on React/Next fundamentals and product instincts. | ~1 week |
| Deep dive | Architecture & trade-offs; small code walkthrough; design system discussion. | ~1 week |
| Practical | Time-boxed task or prior work review (includes a11y/perf and a light AI-UX prompt/eval step). | 3–7 days |
| Panel | Cross-functional; collaboration and product sense. | ~1 week |
| Offer | Comp band, benefits, start date. Background check post-offer where lawful. | 48–72 hours |
Accommodation requests: email care@clinicbooking.com (subject: "Interview Accommodation").
Apply
Email your applicationwith your resume/CV and links to 1–2 shipped projects (explain your role, metrics impact, and any AI UX choices). If available, include a component/story you're proud of.
Prefer an ATS? Usethe application form if available.
Notices
- Equal Opportunity: We welcome applicants of all backgrounds and do not discriminate on any protected basis.
- Right to work: Work authorization required in your country of residence.
- Privacy: Your data is handled per our Applicant/Candidate Privacy Notice and Records Retention Summary.
Owner/Operator: Spyface Tech Company, LLC (d/b/a "ClinicBooking"). Address: 30 N Gould St Ste N, Sheridan, WY 82801, USA · Contact: hello@spyface.com (corporate), care@clinicbooking.com (talent).
Ready to Apply?
Send your resume and a brief note about your React/Next.js experience to get started.
Apply Now