Location : Prague office 2 days a week

Frontend / React Engineer

## About the role
We run a large multi-brand WordPress VIP platform for Merck Healthcare. The frontend is not a single SPA — it's a set of TypeScript/React applications that run across the platform: on the public site, inside the Gutenberg block editor, and inside custom admin dashboards. You'd own and evolve these React apps, the typed PHP↔React data contracts they depend on, and the tooling around them.


## What you'd work on
React features live across many plugins in the platform; the examples below are representative, not the full list.

- Frontend React apps rendered from Gutenberg blocks: filterable listings, URL-synced state, server data via React Query.
- Configuration-driven form experiences: forms described as config on the PHP side, rendered by a generic React renderer with conditional field logic, schema-based validation, sync + async validators.


## The stack
- **React 18 + TypeScript**.
- **Data/state:** React Query; react-hook-form; custom URL-param state stores.
- **Validation/typing:** zod at runtime; OpenAPI-driven type generation.
- **UI:** Ant Design and Radix headless primitives; type-safe CSS; `@wordpress/components`.
- **i18n:** i18next / react-i18next with an extraction sync check; RTL support.
- **Build/QA:** Webpack; ESLint, Prettier, Jest.


## What makes this role different
- **You build React that integrates with WordPress, not a standalone app.** Your components run on the public site, in the block editor, and in admin — so you work within WordPress's rendering and styling context, not just an empty canvas.
- **The frontend consumes typed contracts produced by PHP.** You'll read PHP to understand the data shape, and frontend changes are kept in sync with PHP fixtures. We invest in typed boundaries (codegen, zod, generated types) to keep that seam healthy.
- **It's a large WordPress VIP / Composer monorepo.** You don't need to be a PHP or DevOps expert, but a working understanding of how built assets reach a running site helps.
- **Healthcare context:** correctness, accessibility, and i18n discipline matter; multiple markets, languages, and RTL.


## Must-haves
- Strong **React 18 + TypeScript** with strict typing.
- Solid **CSS** fundamentals — specificity and the cascade, responsive and RTL layouts, styling React components within a WordPress context.
- Comfortable with **server-state** (React Query or equivalent) and **runtime schema validation** (zod or similar).
- Pragmatic about tooling and CI gates; keeps contracts and generated artifacts in sync.
- Good judgment on **accessibility** and **internationalization**.


## Nice-to-haves
- WordPress / Gutenberg experience (`@wordpress/*`, block editor, `apiFetch`).
- Ant Design or Radix/headless UI; type-safe CSS approaches.
- OpenAPI codegen and i18next.
- WordPress VIP / Composer monorepos; comfort reading modular PHP.

‍