$65-$190/hr frontend engineering work, on your schedule
Review AI UI code for the accessibility violation, the re-render storm, the state bug that only shows in production. The judgment that ships interfaces that feel right. Paid hourly, remote, a few hours a week.
Trusted by top research companies
Hi, we're Zac and Jack, the founders of Terac. We want to talk to you directly, because you are the most important part of what we're building.
Terac is a community of experts. People who have spent years getting good at something specific and hard. The world is about to need more of you, not less. As AI takes on more of the world's work, the bottleneck shifts to the people who actually know what they're talking about.
Expert labor is the rarest resource in the world right now, and it is shockingly hard to find. The companies that need a frontend engineer's eye on a component that breaks accessibility spend weeks chasing people, paying placement fees, and settling for whoever is available. Meanwhile thousands of qualified people are sitting with knowledge that no one ever asks for.
That gap is what we're here to close. Every project that lands on Terac is routed to the people who actually know the answer, on their schedule, paid fairly, and only when the work is verified. No middleman taking a cut of your time. No vague gigs. No chasing checks.
We care about every single person in this community. If you join Terac, you're not a row in a database to us. We read the feedback. We answer the emails. We will fight for you when a customer is being unreasonable, and we will be honest with you when something on our side is broken. The quality of this panel is our entire company, and we owe you a serious bar.
If you've made it this far, here is what we're asking: claim your profile. Put your expertise on the record. Let the world's most ambitious teams come find you for the work only you can do.
Frontend Engineering questions
Still curious? Write to us at support@terac.com.
Niche depth is often the most valuable, because models struggle most with non-tutorial knowledge. If you work daily with WebGL shaders, WASM boundaries, or the Web Animations API, you catch plausible-but-wrong output a generalist misses. Volume varies week to week, but the tasks you see match your specialty.
Tasks are calibrated to senior judgment, not syntax recall: architectural tradeoffs in component design, accessibility tree correctness, performance profiling, and whether a model's reasoning about the rendering pipeline holds up. Junior syntax checks are a small fraction. The more senior you are, the more of the mix fits you.
Real code artifacts: JSX and TSX components, CSS-in-JS and plain CSS, Webpack or Vite configs, WCAG 2.2 audits, and written explanations of the event loop or paint pipeline. You also write worked examples, like walking through why a React reconciliation pattern causes extra re-renders, with annotated code showing the fix.
Both are recognized and strengthen your profile during verification. CWAS is especially relevant for WCAG compliance and ARIA tasks. Google Developer Expert status signals depth in ecosystems like Angular or web performance, and we use that to route matching tasks to you.
No. Every task uses synthetic or sanitized examples built for training, and you never get access to a real company's codebase, repo, or proprietary design system. The worry about reviewing confidential employer work does not apply, because the artifacts are purpose-built for evaluation.
Why your expertise matters
A model generates UI code that passes surface review and then fails on bundle size, a broken accessibility tree, runtime jank on a mid-range Android phone, or a React pattern that triggers subtle hydration bugs. Catching that takes an engineer who has shipped real products. Your reviews teach the model the difference between code that renders and code that holds.
How pay works
Top of the $65-$190 band reflects specialization: performance profiling, WCAG 2.2 and ARIA compliance, design system architecture, or a framework ecosystem like React Native or Next.js App Router. Work is remote, paid hourly on verified completion, not on a fixed schedule.
What the work looks like
A sample of the frontend engineering work you would pick up. Every project is scoped, remote, and paid on verified completion.
- Review a model's React component for prop API flaws, unintended re-renders, and missing error boundaries, annotating each issue with a short rationale.
- Evaluate a code model's responsive data table against keyboard navigation, screen reader announcement order, and 320px overflow behavior.
- Write a canonical worked example of a custom hook managing async state with proper loading, error, and stale-data handling.
- Rate five machine-written Tailwind snippets on semantic HTML, color contrast, and whether utility classes survive a design token override layer.
- Identify failure modes in AI Webpack advice where the code-splitting strategy breaks dynamic imports under a Turbopack migration.
- Build adversarial prompts that test whether a code model knows controlled versus uncontrolled React form inputs, including defaultValue hydration edge cases.
Specialties we match
Frontend Engineering projects span a wide range of focus areas. Tell us where you go deep and we route the work that fits.
- React / Next.js App Router
- TypeScript strict mode
- CSS architecture (BEM, CSS Modules, Tailwind)
- Web performance (Core Web Vitals, Lighthouse)
- Accessibility (WCAG 2.2, ARIA)
- Design systems and component libraries
- Browser rendering and paint profiling
- Webpack / Vite / Turbopack
- React Native / Expo
- Testing (Vitest, Playwright, Testing Library)
- State management (Zustand, Redux Toolkit, TanStack Query)
- Progressive enhancement and SSR/SSG trade-offs
