03Frontend EngineerSep 2026Remote · Lagos, Nigeria
Sandwich
Multi-application job board and HRMS frontend
- Product
- Job board, employer ATS and HRMS
- Apps
- Candidate, employer, HRMS, admin, two marketing sites
- My focus
- Shared platform packages, data table, API and query state
- Ownership
- Sole frontend engineer
- Stack
- Next.js 16
- React 19
- TypeScript
- Turborepo
- Tailwind CSS 4
- TanStack Query
- OpenAPI codegen
- zod
The product
Sandwich covers hiring from both sides and the HR work that follows: candidates search and apply for jobs, employers post jobs and move applicants through a pipeline, and companies manage their people in the HR app.
The frontend is a pnpm and Turborepo monorepo of Next.js apps that share one set of internal packages.
My role
I handled the Sandwich frontend on my own, from setting up the monorepo and its shared packages to building features across the candidate, employer and HR apps, working with the backend team on the API.
A shared frontend platform
Every app is assembled from the same internal packages, so a fix or a new primitive lands everywhere at once.
UI package
Vendored shadcn primitives plus shared composites: the data table, dashboard shell and sidebar, form field wrappers, a wizard stepper, charts and a workspace switcher, with brand tokens per app.
API client package
The SDK, types and query helpers are generated from the backend's OpenAPI spec and committed. A hand-written layer adds one axios instance, a typed error class, and a sign-out bridge on 401 that apps register themselves, so the package never imports a router.
Codegen that does not break the build
The generation script probes the spec first. If the spec is unreachable it keeps the committed SDK so builds continue, and on a fresh clone with no spec it writes typed placeholders so the repo still type-checks.
Query package
One query client with the shared retry policy, created per request on the server and once in the browser.
Security package
A single Content-Security-Policy builder that each app can extend, restrictive default headers, a report-only mode, and a Cloudflare Turnstile gate used by every app's auth routes.
UI primitives and portal features
A standard DataTable
Generic over the row type, with three pagination modes chosen by the props you pass: client (the table slices rows), server (page, size and total) and cursor (a Load more button). Sorting cycles through ascending, descending and off, sets aria-sort, and sorts a copy so cached data is never mutated.
Careful states
Skeleton rows while loading, separate empty and no-results states, and select-all that covers only the visible page. The card and its toolbar stay mounted across states, so a search box does not lose focus mid-typing. In development it warns if local sorting is used over server-paged data.
Candidate portal
Job search with filters and cursor paging, job detail and apply with résumé and screening questions, saved jobs with optimistic updates, applications and offers.
Employer portal
Job management, a hiring pipeline with stage moves, rejections, offers and notes, applicant pages, company profile, and team invitations.
HR app
Sign-in, company setup, roles and invitations, plus the attendance, leave and performance screens.
API integration and query state
Retry rules by status
Client errors and cancellations are never retried. Server errors and dropped connections retry at most twice with backoff. A rate-limit response retries once, and only when the server asks for a wait of a few seconds. Mutations are never retried. Without this, a single 401 would have triggered sign-out four times.
Cancellation handled correctly
Every query passes its abort signal through to the request. A cancelled request is re-thrown as a cancellation, so it is not converted into a server error and retried.
Cursor pagination
Infinite lists read the server's cursor and has-next flag, stop cleanly when the cursor is empty, and keep the previous rows visible, dimmed, while a new filter loads.
Cache updates without flicker
In the hiring pipeline a change is patched into every cached list that contains the applicant, keeping the paging data intact, and the lists are then refetched in the background. The inbox marks messages read optimistically, with a snapshot to roll back to if the request fails.