Boolean search strings for React developers: hooks, Next.js, React Native and the "react" verb problem
On this page
- React eras, frameworks and credentials that change what a React search finds
- Ten Boolean strings by kind of React work
- What LinkedIn, Dice, GitHub and Google actually support
- Narrowing by rendering model, framework and seniority
- False positives worth excluding with NOT
- A worked example: three passes on a React modernization search
- What a search cannot verify
- Questions people ask
A React developer search works when it writes out every spelling of the framework (React, React.js,
ReactJS) and pairs it with a word only people who build in React write: hooks, JSX, Next.js, Redux
Toolkit or Server Components. "React" on its own is an ordinary verb ("able to react quickly"), and since
2022 it has also been the name of a prompting method that AI engineers use for agents, so a bare
react drifts fast. As of November 2026, react.dev lists React 19.3 as the latest version and
names Next.js, React Router and Expo as its recommended frameworks, which is why the framework a candidate
names tells you more than the word React does.
Below are ten strings by kind of React work, and what LinkedIn, Dice, GitHub and Google support as of November 2026. For front-end roles across every framework, see Boolean search strings for front-end developers; for mobile apps, see Boolean search strings for mobile developers; for the operators themselves, see Boolean search strings for recruiters.
React eras, frameworks and credentials that change what a React search finds
| Kind of React work | Terms candidates write | Common titles |
|---|---|---|
| Single-page applications | React, Vite, React Router, Redux Toolkit, TanStack Query, TypeScript | React developer, front-end engineer |
| Server-rendered and full-stack React | Next.js, App Router, Server Components, Server Actions, React Router v7, Remix | React engineer, full-stack engineer |
| Component libraries | Storybook, design system, MUI, Radix, Tailwind | UI engineer, design systems engineer |
| Older React codebases | Class components, Create React App, Redux with sagas, Enzyme, webpack | React developer, front-end developer |
| React Native | React Native, Expo, New Architecture, native modules | React Native developer, mobile engineer |
- Versions mark the era a developer worked in. React's versions page lists React 16.8 (February 2019, the release that added hooks), React 18 (March 2022), React 19 (December 2024), React 19.2 (October 2025) and React 19.3 (September 9, 2026) as the latest version, as of November 2026. Its page on class components says they are still supported but not recommended in new code. A profile full of class components and lifecycle methods describes pre-2019 habits, or a legacy app the client may need maintained.
- Create React App is a legacy signal. The React team's post Sunsetting Create React App deprecated it for new apps on February 14, 2025 and recommends a framework, or a build tool such as Vite, Parcel or Rsbuild. React's Creating a React App page names three full-stack frameworks: the Next.js App Router, React Router and Expo.
- Remix became React Router v7. The Remix team's May 15, 2024 post says what was planned as Remix v3 would ship as React Router v7, and an update says v7 was released in December 2024. Profiles write either name for the same kind of work, so put both in one OR block.
- The Next.js router shows how recent the work is. The Next.js docs describe the App Router as the newer router that supports Server Components and the Pages Router as the original one, still supported. "App Router" or "Server Components" on a profile points to recent Next.js work.
- React Compiler is new. React's React Compiler v1.0 post (October 7, 2025) calls it a build-time tool that optimizes apps through automatic memoization and says Expo SDK 54 and up enables it by default. Few profiles mention it yet; treat it as a bonus term, never a requirement.
- Redux has an official default. The Redux docs call Redux Toolkit the official recommended approach for writing Redux logic, so "Redux Toolkit" reads more current than "redux-saga" or "Redux" alone.
- The common certificate is entry-level. Coursera lists the Meta Front-End Developer Professional Certificate as a beginner-level, nine-course series with no prior experience required, as of November 2026. Useful for junior roles; shipped applications say more for anyone else.
Ten Boolean strings by kind of React work
Swap in the framework, domain and metro from your own intake; these are examples. Search on the work, never on a term that stands in for age, sex, race, religion, national origin, disability or veteran status, including graduation years.
React web applications
1. React developer — LinkedIn general search
("react developer" OR "react engineer" OR "react.js developer" OR "front-end engineer" OR "frontend engineer") AND (react OR "react.js" OR reactjs) AND (hooks OR jsx OR typescript) NOT ("react native developer" OR recruiter OR instructor)
2. Senior React engineer on current React — LinkedIn Recruiter, Job titles + Keywords filters
("senior react developer" OR "senior react engineer" OR "senior front-end engineer" OR "senior frontend engineer" OR "staff frontend engineer") AND ("react 19" OR "react 18" OR "server components" OR suspense OR "concurrent rendering")
3. Next.js App Router developer — LinkedIn general search
("react developer" OR "react engineer" OR "front-end engineer" OR "full stack engineer") AND ("next.js" OR nextjs) AND ("app router" OR "server components" OR "server actions")
4. React Router or Remix developer — Dice resume search
(react) AND ("react router" OR remix) AND (typescript) AND ("server-side rendering" OR ssr OR vite)
State, testing, migration and React Native
5. State and data fetching — LinkedIn Recruiter, Keywords filter
(react OR "react.js" OR reactjs) AND ("redux toolkit" OR redux OR zustand) AND ("tanstack query" OR "react query" OR graphql OR apollo)
6. Legacy React modernization — LinkedIn general search
(react OR "react.js") AND ("class components" OR "create react app" OR webpack) AND (hooks OR vite OR "next.js") AND (migration OR migrated OR upgrade OR upgraded)
7. React developer who tests — Dice resume search
(react) AND ("react testing library" OR jest OR vitest) AND (playwright OR cypress)
8. React Native developer — LinkedIn general search
("react native developer" OR "react native engineer" OR "mobile engineer") AND "react native" AND (expo OR "new architecture" OR "native modules") AND (ios OR android)
GitHub and X-ray
9. Public GitHub accounts by language and city — GitHub user search
language:typescript location:"austin" type:user repos:>10
10. Public LinkedIn profiles by framework and metro — Google X-ray
site:linkedin.com/in "react developer" "next.js" "typescript" "austin" -jobs -recruiter
GitHub's repository search adds one more route:
topic:react language:typescript pushed:>2026-05-01 lists recently updated public
repositories that their owners tagged with React, and each repository leads to an account. Treat every
GitHub and X-ray result as a lead to check, since most commercial React code is private.
What LinkedIn, Dice, GitHub and Google actually support
As of November 2026, LinkedIn's Boolean help page requires AND, OR and NOT in capitals, supports quotes and parentheses, gives OR the lowest precedence and does not support wildcards, so react, "react.js" and reactjs each need writing out. It says nothing about how periods inside a term are matched, so keep "next.js" and nextjs as a pair too. LinkedIn Recruiter's Boolean page lists Job titles and Skills and Assessments among its Boolean filters and warns that too many facets in one query can cause a search result issue, so put the titles in Job titles and React with its framework in Skills.
Dice's Boolean guide supports parentheses, quotes, AND, OR and NOT, and says its database fills in word endings automatically. That helps for "developer" and "developers," but it means a bare react may also pick up other forms of the verb, so on Dice keep react next to jsx, hooks or a framework. The same guide warns that NOT drops every candidate with the term anywhere in the resume, which is why string 1 excludes the "react native developer" title and not the words "react native."
GitHub's user
search documents language:, location:, repos: and
type:user, says language: matches users with a majority of their repositories in
that language, and returns organizations as well as people unless you add type:user. React is
a library, not a language: GitHub's Linguist
language list counts .jsx files as JavaScript and groups TSX under TypeScript. In our test on
November 11, 2026, language:tsx in user search returned no accounts, so search
language:typescript or language:javascript and read the repositories. The
repository
search page documents topic:, pushed: and language:, which is
how the topic search above works. Google's
search operators page documents quotes,
site:, the minus sign and filetype:, but not OR, so string 10 uses none.
Narrowing by rendering model, framework and seniority
Ask the client how their React is rendered and what it runs on. A client-only single-page app built with Vite, a Next.js site using the App Router and Server Components, a React Router v7 app, and an Expo app that ships to phones are all "React," but the developers who built each write different words and answer different interview questions. Put the client's framework in a required block and the other frameworks in a second pass, because a strong developer on one moves to another quickly; clients often accept that once they see the list.
Then ask whether the role is mostly React or partly backend. If the developer will also write API routes, database queries and deployment scripts, the full-stack developer strings fit better. Seniority shows in scope words: "architected," "led the migration," "owned the design system," "performance budget," "code reviews" and "mentored," over "built components" and "implemented designs." LinkedIn's premium search filters page lists Years of Experience and Seniority Level only for Recruiter and Sales Navigator, as of November 2026.
False positives worth excluding with NOT
- The verb react. Sales, support and operations profiles say they "react quickly" or "react to market changes." A required block with jsx, hooks, "react.js" or a framework removes them; never search the bare word.
- ReAct, the AI agent method. The 2022 paper ReAct: Synergizing Reasoning and Acting in Language Models named a way of prompting language models, and AI engineers now write "ReAct agents." LinkedIn search is not case-sensitive, so it reads the same as React. If agent builders flood the list, add NOT ("react agent" OR "react agents").
- React Native developers, for a web role. They list React and hooks but spend their days on Expo and the app stores. Exclude the "react native developer" title, not the words, so developers who do both stay in.
- Designers who hand off to React. UX and UI designers mention React because their designs become React components. Require a code word (hooks, TypeScript, testing) and see Boolean search strings for UX designers when the client actually needs design.
- Course and bootcamp projects, for senior roles. Entry-level courses teach React, so students list it next to a to-do app. Exclude "student," "bootcamp" and "intern" when the client needs production experience, and keep them for junior hires.
- Recruiters and trainers. Their headlines say "hiring React developers" or "React instructor." Exclude "recruiter," "talent acquisition" and "instructor."
A worked example: three passes on a React modernization search
An invented search, shown as it actually gets narrowed.
Intake: A logistics software company's customer dashboard was started on Create React App with class components and Redux. It needs a senior React engineer to move it to Next.js with the App Router and TypeScript without breaking the tables and forms customers use every day. Not looking for mobile developers or designers.
Pass 1: react AND senior: a huge list mixing account managers who "react
quickly," React Native developers, designers and recruiters.
Pass 2: ("senior react engineer" OR "senior react developer" OR "senior frontend
engineer") AND ("react.js" OR reactjs OR react) AND typescript NOT ("react native developer" OR
recruiter): relevant, but most of the list has only worked on new projects.
Pass 3: add AND ("class components" OR "create react app") AND ("next.js" OR
"app router") AND (migration OR migrated). Those words come from engineers who have carried an old
React app into the current model. The list is short enough to call, and the screen asks which part they
moved first and how they kept the old and new versions running side by side.
The legacy words did the work. The new framework shows where a developer has arrived; class components and Create React App show whether they have made the trip this client is about to make.
What a search cannot verify
A string can find someone whose profile names the right React version and framework. It cannot show whether they understand why a component re-renders, whether their components are accessible, or whether the portfolio work is theirs or the team's. Use the front-end developer screening questions for React, accessibility and performance on the call, the software engineer phone screen questions for general engineering depth, and the interview guide for software engineers for the technical rounds. If the client will take strong developers from another framework, the front-end strings cover Angular and Vue.
Questions people ask
What is a good Boolean string for a React developer?
Write out every spelling of the framework, pair it with a word only React developers use, and keep recruiters out. For example: ("react developer" OR "react engineer" OR "front-end engineer" OR "frontend engineer") AND (react OR "react.js" OR reactjs) AND (hooks OR jsx OR typescript) NOT ("react native developer" OR recruiter OR instructor). LinkedIn has no wildcards, so each spelling has to be typed in full.
How can I tell a current React developer from one who has only maintained old code?
Look for the words of each React era. Hooks arrived in React 16.8 in February 2019, React 19 in December 2024, and react.dev lists React 19.3, released September 9, 2026, as the latest version as of November 2026. Class components and Create React App, which the React team deprecated for new apps on February 14, 2025, point to older codebases; Server Components, the Next.js App Router and React Compiler point to recent ones. Confirm on the call which version they used last.
Should a React web search include React Native developers?
Only if the client wants both. React Native builds iOS and Android apps with React, so the developers share hooks and JSX, but their daily work is mobile: Expo, native modules, app store releases. For a web role, exclude the "react native developer" title and keep developers who list both; for a mobile role, use the mobile strings instead.
Is the Meta Front-End Developer certificate worth searching for?
For junior roles, as an optional signal. Coursera lists the Meta Front-End Developer Professional Certificate as a beginner-level, nine-course series that needs no prior experience and covers React, as of November 2026. It shows someone has studied React, not that they have shipped it in production, so never require it for mid-level or senior roles.