AI-Native UI React Engineer

Read this first

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 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-negotiable

User 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 desig…