Senior Frontend Engineer (React, Next.js, TypeScript)

We are hiring a frontend engineer to own two production applications: an internal operations console and a clinic portal. Both are Next.js App Router applications. The console covers dashboards, billing, and operational logs across clinics. The portal covers day-to-day clinic work: appointments, calendar booking, calls, insurance, refills, staff, billing, and notifications, with separate access for practice, provider, and front-desk users.

This is a production role. You will extend existing applications, not start a greenfield UI.

*What you will do*

• ⁠ ⁠Build and maintain screens in both applications: data tables, filters, charts, forms, and role-based navigation.
• ⁠ ⁠Establish a shared visual system for both codebases. Today each app carries its own Tailwind theme and a copied component set. You will define the palette, type, spacing, and core components, and apply them so new work does not drift.
• ⁠ ⁠Implement list and report views that stay correct under real volume: server-side pagination, filters, date ranges, loading and empty states, and file export. Charts must use bounded data, not an unbounded client fetch.
• ⁠ ⁠Add new modules in the existing pattern: typed API client, Zod-validated forms, and the current auth and route protection. Do not introduce a second data-fetching or styling approach.
• ⁠ ⁠Ship through the existing toolchain: pnpm, TypeScript, ESLint, and a production Next.js build, with environment-based API configuration.
• ⁠ ⁠Handle clinical data as production data. Patient identifiers and call content do not belong in client logs, toasts, or error screens.

*What you bring*

• ⁠ ⁠4 or more years building production web applications, including at least 2 years with Next.js App Router in a shipped product.
• ⁠ ⁠Strong TypeScript. You type API responses, form schemas, and component props instead of using ⁠ any ⁠ to get past the compiler.
• ⁠ ⁠Production React 19: Server Components and Client Components, when each one is appropriate, and how authenticated data is loaded on the server.
• ⁠ ⁠Tailwind CSS in a real product, including design tokens and a component library. Experience turning an ad-hoc theme into a system used by more than one app.
• ⁠ ⁠Data-heavy UI: paginated tables, filters, charts, and exports against a REST API. You have diagnosed slow lists and fixed them by changing the query, not by rendering every row.
• ⁠ ⁠Forms with React Hook Form and Zod, or an equivalent schema-based approach.
• ⁠ ⁠Authentication in Next.js (we use Auth.js), including protected routes and role-based access.
• ⁠ ⁠Careful production habits: reproducible builds, environment separation, and accessible interactive UI (keyboard, focus, labels).