React developers vetted for the Hooks era.
Modern React placements need more than “knows React.” Server Components, Suspense data flow, hydration tradeoffs, design-system discipline, build performance — the surface is wider than it was. sourceBOLD’s 4-gate gauntlet calibrates the technical screen against the actual React stack your team ships in: Next.js, RSC, Suspense + Streaming, design systems, tooling.
Same gauntlet, calibrated for the React stack.
60-minute structured exercise calibrated against modern React patterns — hooks, Suspense boundaries, component composition, state management beyond useState. Two human reviews, blind to candidate identity, must agree to pass. Reviewers are Staff+ React engineers who currently ship production React.
Architecture round. We ask the candidate to walk through partitioning a real-world product surface — when to render server, when to render client, how data flows, what caches where. Same questions every time so the calibration is real, not vibes-based.
Two-hour real-codebase session. The candidate ships a small feature against a Next.js benchmark repo. We watch how they handle a stack trace, how they reach for the docs, how they communicate while debugging. Stack-specific judgment is what G4 catches that résumés don’t.
Full funnel walkthrough at /guides/4-gate-vetting — including G1 (communication assessment), the blind double- review pattern at G2, and why we publish the 3.9% acceptance rate rather than treating it as proprietary.
Week 1 — shipping by Friday.
- DAY 1Repo access, dev environment running, SOW kickoff doc reviewed. Standup attendance starts on day one.
- DAY 2–4Picks up a “good first issue” — typically a UI polish ticket or a self-contained bugfix. Your tech lead reviews the PR. Comms happen in your team’s existing Slack + standup rhythm — no sourceBOLD-side intermediary.
- DAY 5First feature ship — typically something that touches both client + server code so the next PR has more surface area to lean into.
- WEEK 2+Real feature work. Integrates into the standup rotation, code-review rotation, on-call (if applicable). Treated like a senior member of the team — because that’s what they are.
The contracting layer sits underneath all of this. From your team’s day-to-day, the developer is a senior React contractor on Slack. The cross-border tax shape, the bi-weekly invoice cycle, the Wise dispatch in the developer’s local currency — those are sourceBOLD’s operational concerns, not your team’s.
Side-by-side, where each model fits.
Pick by the situation, not by the pitch.
- Pick in-house if you need a full-time React engineer with benefits, equity, and an at-will employment relationship.
- Pick a US-based contractor if you need US-only data residency or a very short engagement (under four weeks).
- Pick sourceBOLD if you need senior React capacity on month-to-month engagement, with published pricing and 4–8 hours of US time-zone overlap — typical Series-A-to-C scaling scenario.
Scale your team.
Surge ahead.
A concise scoping call. Pre-vetted candidates. First standup in a few short weeks.