The role:

You’ll take on front-end work on our Partner Dashboard — the internal control surface our business and our mobile network operator partner use to configure services and products, billing, finance contracts, campaigns, user administration, moderation, message templates, permissions and reporting. Twenty-plus feature domains, still shipping releases, with real money and live operator services configured through it — which sets the bar for correctness.

It’s also a mature codebase: React 16.14 in plain JavaScript, Redux 4, Emotion 11, an ejected Create React App we maintain ourselves, and very little automated test coverage. Better said here than discovered in your first week — it’s also where much of the opportunity sits. There’s an early exploration of what this dashboard might look like on our current stack, but a rebuild is not approved or scheduled. A possibility, not a plan. If a mature codebase reads as a red flag rather than an interesting problem, this isn’t the role.

What you’d be doing:

• Feature modules — services, billing configs, campaigns, finance contracts, moderation queues, reports.
• Large, complex forms: interdependent fields, conditional validation, server-side validation feedback, CSV bulk upload. Most of the work, and doing it well is a real skill.
• Data-dense views — sortable, filterable tables, pagination, charts and reporting.
• The template editors — variable interpolation, live preview, per-market copy. Intricate, stateful, and the kind of component that rewards care.
• Role-based access control in the UI, and REST integration against our Laravel backend.
• Establishing a testing baseline, plus reviews, mentoring, and working directly with design.

What we’re looking for:

• Earn real context — the domains, the data model, the operator workflows, and the reasons behind decisions that look odd from outside.
• Take ownership of the difficult areas — the modules that have been avoided, left in better shape, release by release.
• Build the case — what’s costing us most, what could be modernised in place, what a rebuild would actually buy and cost. Evidence and options, not enthusiasm.
• Lead it, if it goes ahead — which is why we ask for current-stack experience up front.

Experience required — this codebase:

• Strong JavaScript fundamentals — no compiler is watching your back here.
• Modern React, plus comfort with class components and older lifecycle patterns.
• Redux, properly understood — store shape, thunks, selectors, and the judgement to know what doesn’t belong in global state.
• CSS-in-JS (Emotion or styled-components) — a genuine requirement here, not legacy baggage.
• Complex form and validation work — the heart of the product.
• HTML, CSS and build tooling — semantics matter for people entering data all day, and you should be able to read a Webpack config.

Current practice, and where you’d take it:

• TypeScript, to strict team conventions — any, as assertions and @ts-ignore are lint errors.
• Next.js App Router — server components, server actions, and judgement about where the client boundary belongs.
• Tailwind CSS with shadcn/ui / Radix primitives.
• Migration experience — a legacy front-end taken to a modern stack incrementally, in production, without a feature freeze.
• AI-assisted development. We work with Claude Code against shared coding rules: direct it, review it, reject what’s wrong.

These are requirements, not nice-to-haves: a modernisation case is only credible from someone who knows what good looks like.

Testing:

The clearest gap in the codebase, and we’d like this role to help close it. Our standard elsewhere is that a feature isn’t done until it’s tested — Vitest, Playwright, Testing Library, Storybook. Here, Jest is configured but unit testing never became routine, and the small end-to-end suite is stale and out of CI. We want someone who introduces tests where risk and change-rate are highest, early, and not contingent on any rebuild.

Security:

A privileged internal tool that configures billing and live services, so it carries more weight than it would on a consumer app. You don’t need to be a specialist — what’s genuinely useful is familiarity with the ground and how these are addressed in practice:

• Authentication and session handling — cookie flags, token lifetime and refresh, browser storage trade-offs.
• RBAC in the UI is presentation, not enforcement — the API is the boundary.
• Untrusted input, sanitising anything rendered as HTML, and where XSS and CSRF apply.
• Credentials and internal service URLs kept out of the browser, plus dependency hygiene.

It’s an area we keep under active review, and one where a well-argued improvement carries weight.

Bonus:

• TanStack Query and Table.
• Monorepos (pnpm, Turborepo, Changesets).
• Docker/Kubernetes.
• Laravel or PHP, enough to read the API.
• Any end-to-end framework.

You:

• Comfortable in someone else’s code — you can land a change in an unfamiliar module without breaking three others, and you understand a legacy system before you judge it.
• Able to make a case with evidence — the cost of leaving something, the cost of fixing it, and a credible plan for people who don’t read code.
• Exceptional attention to detail. In a tool that configures billing, a wrong default is a production incident, not a cosmetic bug.
• Patient with a long game, and assertive enough to challenge a weak plan early.

• Feature modules — services, billing configs, campaigns, finance contracts, moderation queues, reports.
• Large, complex forms: interdependent fields, conditional validation, server-side validation feedback, CSV bulk upload. Most of the work, and doing it well is a real skill.
• Data-dense views — sortable, filterable tables, pagination, charts and reporting.
• The template editors — variable interpolation, live preview, per-market copy. Intricate, stateful, and the kind of component that rewards care.
• Role-based access control in the UI, and REST integration against our Laravel backend.
• Establishing a testing baseline, plus reviews, mentoring, and working directly with design.

• Strong JavaScript fundamentals
• Modern React, plus comfort with class components and older lifecycle patterns.
• Redux, properly understood — store shape, thunks, selectors, and the judgement to know what doesn’t belong in global state.
• CSS-in-JS (Emotion or styled-components)
• Complex form and validation work
• HTML, CSS and build tooling
• TypeScript
• Next.js App Router
• Tailwind CSS with shadcn/ui / Radix primitives.
• Migration experience
• AI-assisted development
• Testing frameworks (Vitest, Playwright, Testing Library, Storybook, Jest)
• Familiarity with security best practices (Authentication, RBAC, input sanitization, XSS, CSRF)

• Strong JavaScript fundamentals
• Modern React, plus comfort with class components and older lifecycle patterns.
• Redux, properly understood — store shape, thunks, selectors, and the judgement to know what doesn’t belong in global state.
• CSS-in-JS (Emotion or styled-components)
• Complex form and validation work
• HTML, CSS and build tooling
• TypeScript, to strict team conventions
• Next.js App Router — server components, server actions, and judgement about where the client boundary belongs.
• Tailwind CSS with shadcn/ui / Radix primitives.
• Migration experience — a legacy front-end taken to a modern stack incrementally, in production, without a feature freeze.
• AI-assisted development.
• Familiarity with testing frameworks (Vitest, Playwright, Testing Library, Storybook, Jest)
• Familiarity with security best practices (Authentication, RBAC, input sanitization, XSS, CSRF)