# React Skills Test and Verified React Score > Take an adaptive React skills test on hooks and rendering, refactor components live with a practitioner and connect GitHub repos to prove your React skills. Source: https://getlemma.io/skills/react Almost every frontend CV lists React, so the word alone tells a reader very little. Lemma builds your React record from live sessions, adaptive assessments and the code you have actually shipped. How React is assessed Preparing for an interview? [React interview questions, junior to senior](https://getlemma.io/skills/react/interview-questions) ## What React competence looks like A competent React developer decides where state lives before writing a component. They lift state only as far as it needs to go, reach for context sparingly, and can explain why a component re-rendered. When a list stutters, they check keys, memoisation and effect dependencies before blaming the library. In practice that also means knowing the boundary between server and client components, using Suspense for loading states instead of scattered spinners, and writing custom hooks that hide messy logic behind a clean interface. They keep effects for synchronising with the outside world, not for deriving data that could be computed during render. ### Component architecture Splitting UI into composable pieces, choosing props over context, and keeping components small enough to test. ### Hooks and effects Correct dependency arrays, cleanup functions, and knowing when an effect is not needed at all. ### State management Local state, reducers, context and external stores, chosen by how widely the data is shared. ### Rendering performance Diagnosing unnecessary re-renders with the profiler, stable keys, memoisation and splitting heavy subtrees. ### Server and client components Deciding what renders on the server, what ships to the browser, and how data crosses the boundary. ### Suspense and data loading Loading and error boundaries, streaming, and avoiding request waterfalls in nested components. ## What counts as evidence of React skills? Listing React on a profile proves nothing on its own. What counts is a component you shipped, a session where someone watched you debug one, or a test you passed. These are the records Lemma can hold for your React skill, and where each one comes from. See the [evidence methodology](https://getlemma.io/methodology#evidence-types) for how each source is weighed. [Live session](https://getlemma.io/product/sessions) ### Component architecture review in a live session You build or refactor a component with a practitioner watching. They see how you split responsibilities, name props and handle state, then rate the session. That rating becomes React evidence. [Adaptive assessment](https://getlemma.io/product/assessments) ### Adaptive assessment on hooks and rendering Scenario questions test effect timing, stale closures and re-render causes. A component re-renders on every keystroke: you pick the change that fixes it from the options. [GitHub connector](https://getlemma.io/product/passport) ### A React repository connected through GitHub Link a repository or a specific commit you wrote. Lemma checks the code exists and that your account has access, then re-checks it so the proof stays current. [Vercel connector](https://getlemma.io/product/passport) ### A deployed React app via Vercel Connect a Vercel deployment of an app you built. It shows the work runs in production, not only on your laptop. ## How is a React skills test run on Lemma? The React test is adaptive: 15 to 25 questions, each picked from how you answered the last, built around real interface bugs rather than trivia. Its result joins your live sessions and linked repositories or deployments in your React SCI, which also weighs how recent the evidence is. [How the SCI score is calculated](https://getlemma.io/product/sci)[How adaptive skills assessments work](https://getlemma.io/product/assessments)[Practise React in live skill swap sessions](https://getlemma.io/product/sessions)[Which evidence types count](https://getlemma.io/methodology#evidence-types)[What your Skills Passport shows](https://getlemma.io/product/passport) 1. ### Work through components live Book a session with a React practitioner and refactor a real component together. Expect questions about why state sits where it does and what triggers each render. Teaching React to someone else counts for more than learning it. 2. ### Take the adaptive React assessment Questions get harder as you answer correctly, and harder ones count for more. Expect realistic scenarios about effects, memoisation and server components, each with a time limit and no going back. 3. ### Attach what you have shipped Connect GitHub or Vercel so your React work sits next to your session and assessment record. Keep practising, because evidence goes stale and your score reflects recent work. ## React skills: common questions ### How do I prove I know React without a computer science degree? Show the work instead of the credential. Build or review components live with a React practitioner, pass an adaptive assessment on hooks and rendering, and connect a repository you wrote. Each piece is recorded against your React skill, so a reader sees how you actually work rather than where you studied. ### What should a React portfolio include for a frontend job? Include at least one app with real data fetching, loading and error states, and a clear component structure. Explain a performance problem you fixed and why. On Lemma you can connect the repository and the deployment, then back them with session ratings and an assessment result. ### Is a React certification worth it for getting hired? A certificate shows you finished a course. Hiring managers usually want to know how you structure components, debug renders and reason about state. Live sessions and an adaptive assessment answer that directly, and they sit alongside any certificate you already hold. ### What React topics come up in technical interviews? Expect questions on effect dependencies, why a component re-renders, lifting state versus context, keys in lists, and server versus client components. Lemma's React assessment and practice drills cover the same ground, so preparing for one prepares you for the other. ## Skills related to React [Browse the skills directory](https://getlemma.io/skills) [### Next.js Evidence for rendering, routing and caching decisions in Next.js, backed by deployed work. Evidence for Next.js](https://getlemma.io/skills/nextjs)[### TypeScript Show that your types catch real bugs instead of just silencing the compiler. Evidence for TypeScript](https://getlemma.io/skills/typescript)[### JavaScript Evidence that you understand how JavaScript runs, not just how to write its syntax. Evidence for JavaScript](https://getlemma.io/skills/javascript)[### GraphQL Show how you design GraphQL schemas and resolvers that stay fast and safe. Evidence for GraphQL](https://getlemma.io/skills/graphql) ![Painting of an olive grove in soft sunlight with hills beyond](https://cdn.sanity.io/images/islu4peo/production/613eb3f93566423c9adf45246f2cf1a61437c04c-1680x1120.jpg?w=1080&fm=webp&q=68&fit=max) ## Start your React evidence record. Lemma is in early access. Request an invite and we will email you when your place is ready.