How to hire a Three.js / WebGL developer

To hire a Three.js or WebGL developer in 2026, first decide if you actually need one. Most product teams who say "we need 3D" are best served by Spline plus a regular React engineer at $40-90/hr. Reserve the dedicated WebGL specialist (senior day rates of $90-220/hr) for custom shaders, perf-critical visualization, or marketing sites where the craft is the product.

The pool of working creative WebGL engineers is small and getting smaller as the senior cohort moves into AI tooling. That makes hiring slow, expensive, and easy to get wrong if you over-spec the role. This post walks you through which camp your project is in, where the real talent lives in 2026, how to evaluate them in under an hour, and what to actually pay.

First, decide if you actually need a WebGL specialist

There are three buckets of "we need 3D on the web" work, and only one of them justifies a dedicated WebGL hire.

Bucket 1: Spline plus a React generalist. A static or lightly animated 3D scene on a landing page, a hero element, a product mockup that spins. Spline lets a designer build the scene visually, export to a React component, and ship in a day. Your existing front-end dev wires it up. No WebGL hire needed. This covers maybe 70% of the requests we see described as "we need a Three.js developer."

Bucket 2: React Three Fiber (R3F) generalist. An interactive product configurator, a 3D viewer for an e-commerce SKU, a data viz with mild interactivity. R3F plus the Drei helper library (raycasting, controls, loaders) plus a <model-viewer> fallback handles this stack. A strong React engineer with two weeks of R3F practice ships it. You don't need a creative WebGL specialist; you need a senior React dev who can read shader docs without panicking.

Bucket 3: Genuine WebGL specialist territory. Custom GLSL shaders. Particle systems with thousands of instanced meshes. Physics simulations. WebXR scenes. Award-bait marketing sites where the craft is the entire product (the kind of work that wins FWA or Awwwards). Perf-critical visualization on low-end mobile. This is where you actually need someone whose primary stack is Three.js and who can write vertex and fragment shaders without Stack Overflow.

If you're in Bucket 1 or 2, stop reading this post and go hire a regular React developer instead. The rest is for Bucket 3.

What a great Three.js / WebGL developer can actually do

The job listings on Upwork and Arc tend to lump everything under "Three.js developer." In practice, the skill stack for a senior in 2026 looks like this.

• Vanilla Three.js fluency. They can build a scene, lights, camera, materials, and a render loop without a tutorial open. They know when to drop out of R3F into imperative Three.js for perf reasons.
• GLSL shader writing. Vertex and fragment shaders in their head. They can write a Fresnel effect, a noise-displaced surface, or a custom post-processing pass without copy-pasting from the Book of Shaders.
• R3F + Drei + Leva ecosystem. They reach for useFrame, useGLTF, Instances, Float, OrbitControls from Drei before reinventing them. They use Leva for in-browser tweakable params during dev.
• Asset pipeline discipline. DRACO compression for geometry, KTX2 for textures, Meshopt for everything else. They know the polygon and texture budgets that keep a scene under 5MB.
• Performance budgeting. They can tell you the target frame time on an iPhone 13 (16.6ms for 60fps) and they know how many draw calls and triangles fit inside it. They profile with Spector.js, not vibes.
• AI-native baseline. Every Cadence engineer is AI-native by default, vetted on Cursor, Claude, and Copilot fluency before they unlock bookings. For shader work specifically, that means using Claude or Cursor as a GLSL pair-programmer (most LLMs are surprisingly competent at shader math) and treating prompts as specs for iterating on visual effects.

If the candidate ticks four of those six boxes and has a portfolio that proves it, they're senior. Three of six is mid-level. Two of six is junior, and you should pay junior rates accordingly.

Where to find Three.js / WebGL developers in 2026

The best WebGL developers don't sit on Upwork. The pool is tiny enough that the working pros all know each other. Here's where they actually are, ranked by signal-to-noise.

Three.js Discord and the Three.js forum. The Discord has roughly 50,000 members and a #hiring channel. The forum (discourse.threejs.org) has a Jobs category. This is where freelancers who already have client work hang out. Cold-DM the people answering hard questions, not the ones posting "looking for work."

Bruno Simon's Three.js Journey alumni. Bruno's course is the largest practical funnel of working WebGL devs in the world. The completion Discord is gated and full of people who actually finished a 96-hour course on shaders. Post a job in the alumni channel and you'll get serious replies in 48 hours.

Codrops contributors and alumni. Codrops publishes weekly creative WebGL tutorials. The contributor list is a who's-who of working creative engineers. Read recent articles, find the authors, look up their portfolios.

Awwwards and FWA agency engineers. The senior creative WebGL talent in 2026 came up through agencies like Active Theory, Resn, Hello Monday, Lusion, and Unseen. Many are now freelance or open to interesting project work. LinkedIn-search by ex-employer and the work history alone tells you the level.

WebGL specialists from a gaming background. Unity and Unreal devs who pivoted to web. They bring real-time graphics intuition that pure web devs lack. They cost more, but for visualization and physics work they're often the right call. Cross-reference with our guide to hiring a Unity or Unreal developer if you're weighing console-game backgrounds.

GitHub: pmndrs and the React-Three ecosystem. Look at contributors to react-three-fiber, drei, @react-three/postprocessing, and react-three-rapier. These are the people writing the libraries the rest of us use. Booking one of them is fastest by reading their open-source pinned issues and emailing them.

What we'd skip. Generic Upwork search ("Three.js developer") returns thousands of profiles where the actual portfolio is one tutorial scene. Fiverr is fine for a 3D model upload, useless for a custom shader. LinkedIn job ads attract Bucket 1 and Bucket 2 candidates almost exclusively.

How to evaluate skills (the live-shader test)

The standard 60-minute interview for backend or generic front-end roles doesn't work here. Three.js work is visual. You evaluate it visually.

Start with the portfolio, not the resume. A WebGL developer without three to five linkable scenes shipped to real domains (not just CodePen) is junior, regardless of years of experience. Look for FWA or Awwwards mentions, agency credits, or a personal portfolio that loads in your browser without crashing.

Ask them to walk through one project's perf budget. "Take me through the frame budget on your last shipped scene. What was the target device? Where did you spend the milliseconds? What did you cut?" A senior answers in concrete numbers. A junior says "we just made it look good and tested on Chrome."

Live-pair on a tiny shader bug instead of whiteboarding. Open a shadertoy or a CodeSandbox with a deliberately broken fragment shader (a Fresnel effect with the dot-product inverted, say). Ask them to fix it while you watch. You learn more in 15 minutes here than in a 90-minute system-design interview.

Ask the AI-native question. "Walk me through how you used Cursor or Claude on your last shader. What did you delegate to the model versus do yourself?" The answer tells you whether they're using AI as a shader pair-programmer (good), as a code-completion crutch (mid), or not at all (a tell for 2026; the productivity gap on shader iteration is significant).

Reference checks that ask about shipping, not interviewing. "Did they ship the scene under budget?" "Did the scene survive the first round of mobile testing?" "Would you book them again for a similar scope?" These three questions surface the truth that a candidate's interview prep can't fake. The same logic applies broadly when you vet any developer before hiring.

Red flags. Portfolio is only Codepen demos with no production URLs. Can't answer perf-budget questions in numbers. Has never used DRACO or KTX2. Talks about "making it run smoother" instead of frame times. Has never shipped to a non-Chrome browser.

What it costs to hire a Three.js / WebGL developer in 2026

Here's the channel comparison, with honest trade-offs.

Channel	Day rate	Speed to start	Best for	Trade-off
Three.js Discord / direct outreach	$60-150/hr	2-6 weeks	Niche shader work, repeat hires	No vetting, no replacement guarantee
Toptal / Arc / Revelo	$80-150/hr	1-2 weeks	Vetted senior generalists	Thin on creative-WebGL specialists
Active Theory / Resn / agency	$200-450/hr blended	4-8 weeks	Award-bait launches, full creative team	Minimum scope $80k+, slow start
Cadence (booking by the week)	$500-$2,000/wk	48 hours	2-12 week scopes, R3F + product 3D	Not built for multi-quarter creative leads
Spline + your existing React dev	~$0 + your dev	Same day	Static-ish 3D scenes, marketing pages	Caps out at moderate complexity

The reference data from public marketplaces in 2026: ZipRecruiter pegs the median Three.js hourly at $56 with a band of $49-$83, and the WebGL salary band runs $84k-$198k. Those are generalist numbers. The senior creative pool (Bucket 3) sits well above that, $90-220/hr, because the supply is genuinely small.

Cadence weekly tiers map cleanly to the work types:

• Junior, $500/week. Asset cleanup, GLB optimization, model loader integration, R3F scene wiring with provided designs. Don't task them with shader work.
• Mid, $1,000/week. End-to-end product viewers in R3F, configurator UIs, integration with your existing React app. Light shader work.
• Senior, $1,500/week. Custom shaders, perf budgeting, mobile optimization, full scenes from a Figma plus reference. This is where most Bucket-3 work lands.
• Lead, $2,000/week. Architectural decisions for a 3D platform (configurator engine, viewer SDK), team mentoring, perf-critical viz from scratch.

For a one-off marketing scene or a single product viewer, you're typically looking at 2 to 6 weeks of senior time. That's $3,000-$9,000 on Cadence versus $25,000-$60,000 on an agency engagement. The agency is worth the premium when you need a full creative team (designer, motion, sound, copy); the booking model wins when you have the brief and just need execution.

The alternative: book by the week instead of hiring

Most 3D web work is project-shaped, not headcount-shaped. A product viewer launch. A marketing site. A 6-week WebXR experiment. A configurator MVP. These don't justify a 12-month FTE search through a 50,000-person Discord.

That's the bet behind Cadence's booking model. Founders book vetted engineers in 2 minutes. Every engineer on the platform is AI-native by default, vetted on Cursor / Claude / Copilot fluency before they unlock bookings. Weekly billing, 48-hour free trial, replace any week with no notice. The pool is 12,800 engineers with a 27-hour median time to first commit.

Where booking does NOT win: you're building a 3D product with multi-year R&D (a CAD platform, a configurator engine sold to other companies, a real-time collaborative 3D editor). For those you want an FTE with equity who'll still be there in three years. Cadence is honest about that. We don't try to convert a Lead Graphics Engineer FTE search into a weekly booking; the incentive shapes don't match.

For everything else (the one-off scene, the configurator MVP, the marketing launch, the product viewer), booking beats hiring on speed, total cost, and risk. You don't pay severance to remove a bad fit. You don't lose six weeks if the project scope changes. You get someone shipping inside two days instead of two months.

If you're staring at a 3D scope right now and not sure whether you need a Spline + React combo or a true WebGL specialist, see Cadence's hiring flow. We'll match you against the right tier in 48 hours, you try the engineer for 2 days at no cost, and you only commit by the week.

What to do next

If you're in Bucket 1 or 2, hire a generalist React engineer and pair them with Spline or R3F. You'll save 5x the cost and ship faster.

If you're in Bucket 3, start with the Three.js Discord and Bruno Simon's alumni channel for direct outreach, or skip the sourcing problem entirely by booking a vetted senior on a marketplace. Whichever you pick, evaluate with the live-shader test and the perf-budget question; resumes lie, portfolios don't.

Ready to skip the 8-week recruiter loop? Book a senior Three.js engineer on Cadence with a 48-hour free trial and weekly billing. Replace any week, cancel anytime, no notice period.

FAQ

Do I need a Three.js specialist if I just want a 3D product viewer?

Probably not. Spline plus a competent React engineer using <model-viewer> or basic React Three Fiber covers most product viewers. Hire a dedicated WebGL specialist when you need custom shaders, physics, particles, or guaranteed 60fps on low-end mobile.

What's the difference between Three.js and React Three Fiber?

Three.js is the imperative WebGL library that wraps low-level GPU calls. React Three Fiber (R3F) is a React renderer for Three.js: same engine, declarative API. Most product teams should default to R3F because it integrates cleanly with React state. Perf-critical scenes still drop to imperative Three.js for the hot loop.

How long does it take to hire a Three.js developer?

FTE searches typically run 8 to 14 weeks because the pool is small and senior creative WebGL talent rarely circulates on job boards. Vetted marketplaces deliver in 1 to 2 weeks. Booking platforms (Cadence and similar) start in 48 hours but cap engagements at project length, not multi-year roles.

Should I worry about WebGPU in 2026?

Not yet for hiring. WebGPU is shipping in Chrome, Edge, and Safari Technology Preview, but Three.js's WebGPURenderer is still maturing and most production work targets WebGL2 for browser coverage. Hire for WebGL and GLSL fluency today; treat WebGPU and WGSL as a bonus, not a requirement.

How much does a senior Three.js developer cost in 2026?

US freelance senior creative WebGL rates run $90-220/hr depending on portfolio pedigree (ex-Active Theory or ex-Resn engineers anchor the high end). FTE base salaries land $140-180k in major US markets. On Cadence, senior weekly rate is $1,500.