2

Remote React Js Jobs in Reno, NV (NOW HIRING)

AI-Native UI React Engineer

Truckee, CA · On-site +1

$140K - $210K/yr

You'll create the composable React widget framework and reusable, data-rich interfaces that bring ... Remote-first, async-friendly, US-based hours. * Small senior team - direct access to VP of ...

Software Engineer

Reno, NV · On-site +1

$90K - $105K/yr

We are seeking to bring on talented software developers interested in remote work opportunities. We are an agile development team delivering high quality products on the Web, iOS, and Android with ...

Remote React Js information

See Reno, NV salary details

$23

$59

$85

How much do remote react js jobs pay per hour?

As of Jul 27, 2026, the average hourly pay for remote react js in Reno, NV is $59.09, according to ZipRecruiter salary data. Most workers in this role earn between $49.13 and $68.08 per hour, depending on experience, location, and employer.

What is the difference between Remote React Js vs Remote Front End Developer?

AspectRemote React JsRemote Front End Developer
Required SkillsProficiency in React.js, JavaScript, HTML, CSSProficiency in HTML, CSS, JavaScript, and frameworks like React, Angular, or Vue
CertificationsReact.js certifications or related front-end coursesFront-end development certifications, including React.js
Work EnvironmentRemote, collaborative teams, Agile workflowsRemote or on-site, diverse industries, Agile or Scrum teams
Industry UsagePrimarily in tech companies, startups, SaaS productsAcross tech, e-commerce, media, and enterprise sectors

Remote React Js roles focus specifically on React.js expertise, while Remote Front End Developer positions require broader front-end skills and knowledge of multiple frameworks. Both roles often work remotely in tech environments, but React.js specialists are more niche, whereas Front End Developers have a wider scope of technologies and responsibilities.

What is a Remote React JS Developer?

A Remote React JS Developer is a software engineer who specializes in building user interfaces and web applications using the React JavaScript library while working from a location outside of a traditional office environment. These developers collaborate with teams virtually to design, develop, and maintain interactive web applications. They are responsible for implementing UI components, optimizing performance, and often integrating with back-end services using APIs. Working remotely allows them to contribute from anywhere with a reliable internet connection, providing flexibility and access to global job opportunities.

What are the key skills and qualifications needed to thrive as a Remote React JS Developer, and why are they important?

Success as a Remote React JS Developer requires a solid understanding of JavaScript, React.js, front-end development principles, and typically a degree in computer science or related field. Familiarity with tools such as Git, Redux, RESTful APIs, and modern build systems like Webpack is standard, along with experience using cloud-based collaboration platforms. Excellent problem-solving, communication, and time management skills are crucial for effective teamwork and self-driven productivity in a remote setting. These capabilities ensure efficient code delivery, seamless collaboration, and the ability to adapt to evolving project requirements.

What Are Remote React.js Jobs?

React.js is a type of comprehensive JavaScript library for building user interfaces. Possible remote React.js jobs include full-stack JavaScript developer, React.js developer, backend developer, and user interface developer. These development jobs can all be work from home positions. Your responsibilities include using React.js to develop user-facing features and translating wireframes and designs into high-quality coding. Other duties of this virtual position include building front-end libraries and reusable components for future use and ensuring maximum performance by optimizing components for a variety of web-capable browsers and devices. In any of these positions, you work with a variety of software and computer types.

How does collaborating with a distributed team typically work in a Remote React JS developer role?

As a Remote React JS developer, you’ll frequently collaborate with team members across different locations using tools like Slack, Jira, and GitHub. Daily stand-ups, sprint planning meetings, and code reviews are usually conducted virtually to ensure everyone stays aligned. Clear written communication and proactive updates are essential, as you’ll often work asynchronously with designers, backend developers, and QA testers. Building strong remote collaboration skills helps ensure smooth project progress and a positive team dynamic.
What are the most commonly searched types of React Js jobs in Reno, NV? The most popular types of React Js jobs in Reno, NV are:
What are popular job titles related to Remote React Js jobs in Reno, NV? For Remote React Js jobs in Reno, NV, the most frequently searched job titles are:
Infographic showing various Remote React Js job openings in Reno, NV as of July 2026, with employment types broken down into 80% Full Time, and 20% Contract. Highlights an 100% Remote job distribution, with an average salary of $122,900 per year, or $59.1 per hour.

AI-Native UI React Engineer (Remote)

PropertyRadar.com

Truckee, CA • Remote

$140K - $210K/yr

Full-time

Posted 29 days ago


Job description

Read this first

If you bring an obsession with creating elegant, intuitive user experiences and the technical know how to bring them to life along with AI-first development practices, please read on.

We are betting the engineering org on agentic coding. Our team has already made the transition. Cursor is our primary development environment, and we hire engineers who orchestrate AI agents to ship at multiples of traditional velocity not engineers who use AI to autocomplete the occasional function. We use agentic coding to ship faster, but the bar is not speed alone it's turning complex data into experiences that feel obvious, elegant, and useful.

If I use Cursor/Claude Code for everything now describes you, keep reading. If you are still warming up to agentic workflows, this isn't the role.About PropertyRadar

PropertyRadar is the hyperlocal lead generation platform that property-centric small businesses use to discover, understand, and connect with new opportunities. We turn complex public records data into actionable insights for real estate investors, agents, lenders, and home services pros.

We've been doing this since 2007. We're profitable, owner-operated, and small enough that what you ship matters every release moves the business. We're investing in a modern data and frontend platform to power the next decade of growth, and we're hiring engineers who can help us build it.The role

You will build a UI/UX that delights end users by combining chat-based interactions with rich, embedded product experiences. The bar is a highly intuitive experience that keeps users focused on their goals instead of forcing them to stop and learn how PropertyRadar works. You'll create the composable React widget framework and reusable, data-rich interfaces that bring PropertyRadar's property and owner data into new contexts. This is greenfield frontend work with direct visibility to the VP of Engineering, CEO, and Founder, and you'll work closely with all three on scope and tradeoffs.Why this is a rare role

  • Greenfield, with revenue behind it. You get the blank slate of a startup with the distribution and cash flow of an 18-year-old profitable business.
  • Small team, large surface area. You own end-to-end delivery, not a slice of a slice.
  • Real users, real data. Property and owner data is one of the richest, messiest, most useful datasets in the small-business economy. You'll build the user experience of making this messy, high-value data feel intuitive and actionable.
  • AI-first by mandate. You're joining an engineering culture where agentic coding is the standard, not the experiment.
The stack
  • React 18, TypeScript, Tailwind, Radix primitives
  • Vite as the bundler for both widgets and the host shell
  • OpenAI component kit
  • JSON-RPC 2.0 over for iframe host communication, following emerging AI-host bridge standards
  • Sandboxed iframes with strict CSPs and well-understood cross-origin behavior
What you'll build
  • A composable React widget framework designed to run across multiple embedding contexts sandboxed iframes, web components, shadow DOM with a consistent component model and clean developer ergonomics.
  • Property and owner data experiences: profile views, owner detail panels, interactive maps, lead-gen flows, and outreach actions, all designed to be embedded and reused.
  • AI-powered features within the widgets, integrating LLM capabilities to make data exploration and lead workflows faster and more intuitive.
  • A reusable component library with strong UX, pixel-accurate polish, and accessibility built in.
What we expect of you
  • Bring product taste and craft. You care about the difference between it works and this feels great to use, and you can implement at a pixel level.
  • Ship at agentic-native velocity. We're hiring engineers who deliver materially faster than traditional React teams because Cursor (and other agentic tools) are the primary way they work.
  • Own the spec. Ask sharp clarifying questions, make sound tradeoffs, and ship. We don't hand you tickets.
  • Raise the team's ceiling. Share patterns, prompts, and orchestration techniques that make everyone faster.

About you non-negotiableUser Experience

    • You know how to make dense, data-heavy interfaces feel clear through hierarchy, defaults, progressive disclosure, and state design.
    • You sweat the details: empty states, loading states, error states, interaction polish, and accessibility are part of the product, not cleanup work.
    • You bring deep experience with component libraries and/or design-system engineering, with a strong eye for consistency, usability, and polish.
    • You've supported customer bases of thousands to millions.
    Agentic-native development
    • Cursor (or Claude Code) is your primary IDE not a tool you reach for occasionally.
    • You can describe specific recent projects where agentic coding meaningfully changed your output velocity and quality with examples.
    • You have opinions on agent orchestration: how to scope work for agents, when to break it up, how to review agent output, when to step in manually.
    • Bonus: you've built or contributed to agent workflows, custom Cursor rules, or developer tooling for AI-assisted engineering.

    Expert React + TypeScript

    • Deep working knowledge of React 18, TypeScript, Tailwind, and Radix primitives.
    • Production experience with Vite as a build tool for libraries, applications, or both.
    • You architect complex React frontends comfortably and reach for the right pattern, not the familiar one.
    • You've built data-heavy UIs at scale complex tables, filters, maps, sorting, pagination and you know how to make them performant.
    • You've integrated REST and GraphQL APIs with thoughtful loading, error, and edge-case handling.

    Embedding and iframe craft

    • You've built or shipped against sandboxed iframe architectures and understand the security model end-to-end.
    • You can write and reason about Content Security Policies without reaching for documentation.
    • You've implemented protocols between iframe and host ideally JSON-RPC 2.0 over or a similar structured pattern and you understand origin checks, message validation, and the failure modes.
    • Cross-origin behavior, third-party cookie restrictions, and the practical workarounds for embedded apps are familiar territory.
    Ownership and judgment
    • You don't wait for perfect specs. You drive clarity.
    • You communicate concisely in writing important on a remote, async team.

    Bonus points

    • Hands-on experience with the OpenAI component kit, or comparable embedded-app component libraries. This is a magnet bonus.
    • You've shipped widgets or embedded apps that run inside a third-party host environment.
    • Mapping libraries: Mapbox, Leaflet, Google Maps.
    • PropTech, real estate data, or products built for small businesses.
    • You've owned a design system or component platform used across multiple products or embedding contexts.
    • You've already been through an AI-first eng transformation at another company you can help us avoid mistakes.

    How we work

    • Remote-first, async-friendly, US-based hours.
    • Small senior team direct access to VP of Engineering, CEO, and Founder on this initiative.
    • EOS as our operating framework clear quarterly Rocks, weekly accountability, no surprise priorities.
    • Profitable, owner-operated, no VC pressure. We move fast because we choose to, not because a clock is ticking.