React
Front ends that hold up on the hard screens
Our engineers have built oncology trial matching, live fuel-site dashboards and a repair shop's booking calendar. They join your repo and your review process, and you interview them before anyone starts.
What you are getting
4 things that decide this
- 01Senior engineers only, with React running in production across clinical, financial, IoT and marketplace products on this site.
- 02You interview every engineer before they join, using your own process and your own bar.
- 03They work in your repository, open pull requests against your review rules, and stay on the same product instead of rotating.
- 04You own the code from the first commit. Every engineer is interviewed by you, and a no from you costs nothing.
What a React developer actually does here
Most React work is not about components. It is about state that arrives late, arrives twice, or contradicts itself.
On TrialTriage the same screen is read by an admin, a nurse, a patient and an insurer, and each sees a different slice of one oncology record. On ZhoopZhoop a collision shop's calendar updates over WebSockets while a Twilio voice agent books into it, so two sources write to one view. On TankAware a site manager watches tank levels from IoT sensors that drop offline and come back with a gap.
Different industries, one repeated skill. Deciding what the screen shows when the data is incomplete, stale or contested.
What they take off the team that inherits it
Server state, handled once
Caching, refetching and stale data through TanStack Query rather than a hand-rolled loading flag in forty components.
Role-aware interfaces
One product, several audiences. Permissions checked on the server and reflected in the UI, never enforced only by hiding a button.
Real-time views that reconcile
WebSocket updates merged into cached data so a live change and a page refresh agree with each other.
Accessibility built in
Keyboard paths, focus handling and labels done as the component is written. Retrofitting it later costs several times more.
A build that stays fast
Code splitting and honest bundle budgets. Speed is a thing you keep, not a thing you fix in the last sprint.
- Server dataCached, refetched, shared
- URLFilters and the current view
- FormLocal until submitted
- GlobalSession and theme only
- ComponentEverything else
Most React problems we inherit are one category of state stored in the wrong box. Server data in a global store is the usual one.
Interfaces built on contested data
“Their attention to detail, quality of employees, and work ethic were outstanding.”
Nicolas de Quesada · CEO, Lexpair
How hiring works
- 01
Show us the screen that worries you
A free call about the product, the team and the part of the interface nobody volunteers to change. If a designer would help you more than an engineer, we say so.
- 02
Meet the engineers
We put forward people who have maintained a front end through several years of change, and you interview them against your own bar. No is a complete answer.
- 03
They embed
Your repository, your standups, your pull request rules. One of our engineers is named on the work and stays on the same product.
- 04
They hand over
Tested components and a written answer to where each kind of state lives, so the next developer is not guessing. Where a team would rather we kept maintaining it, we do that under a service level we agree.
Stack
React
Styling and UI
Behind it
Bring us the screen nobody wants to touch
Show us the part of the product that breaks when you change it. The scoping call is free, and you will leave with a read on what is actually wrong.
01Can they work on an older React codebase?
Yes, and most of this work is exactly that. They start by reading what exists and shipping something small, because a rewrite proposed in week one is a red flag from any vendor.
02Do they build mobile as well?
Several do, through React Native. ExtraaJe and Shift Link both pair a React Native app with a web dashboard, which is the usual shape when field staff and office staff need different things.
03How do they fit into our code review process?
They open pull requests in your repository and follow your rules for approvals, tests and merges. Your team reviews their code, which is also the fastest way for you to judge the hire in the first fortnight.
04Will they use React or a framework like Next.js?
Whichever the product needs, and the React team itself now recommends starting with a framework for new apps. A plain React and Vite build is still right for an internal dashboard behind a login, where search visibility and first-load speed matter less.
05Can they work alongside our designers?
Yes. They build from your design files and push back where a design will not survive real data, such as a table that looks fine with three rows and breaks at three thousand.
06How is a React engagement priced?
By how much product there is and how tangled the current code is, not by a rate you compare in isolation. A component library with tests prices very differently from five years of untested screens. Scoping calls are free. Where we must read an existing codebase to answer properly, a paid two-week diagnostic turns the estimate into a fixed price.
