This is not a typical Frontend role.

If you're looking to translate Figma to pixels, wire up APIs, and stop there, this isn’t for you.

But if you care about building interfaces that think,

If you see frontend as a system, not just a layer, and if you want real ownership over product, architecture, and how users experience intelligence - keep reading!

What we’re actually building

At Chargeflow, we’re not building dashboards.

We’re building decision-making systems.

Real-time. High-stakes. At scale.

Fraud is messy, ambiguous, and constantly evolving.

Our product needs to take complex data, surface the right signals,

and enable users or the system itself to act instantly.

The frontend is not a “client” here. It’s part of the system.

This is where you come in.

What you’ll actually do

• Build the core product experience - not just UI, but how users interact with intelligence
• Own features end-to-end - from idea to production to iteration
• Design scalable frontend architecture in a fast-moving, high-growth environment
• Turn complex data into clear, usable, real-time interfaces
• Work closely with product, backend, and data to shape how the system behaves
• Push performance, responsiveness, and UX to production-grade standards
• Use AI as part of your daily workflow - not as a tool, but as leverage
• Help define how modern frontend engineering should look in an AI-native company

What we care about (beyond buzzwords)

• You’ve built real products - not just components
• You think in systems - state, data flow, async behavior, not just UI
• You’ve worked with React + TypeScript deeply, at scale
• You understand trade-offs in architecture, performance, and developer experience
• You care about code quality - not as a rule, but as a standard
• You don’t wait for perfect specs - you figure things out
• You take ownership beyond “frontend”

AI is not optional here

You actively use tools like Copilot, Cursor, and Claude - daily

You don’t just generate code - you think with AI

You understand where AI accelerates, and where it breaks

You’re curious about how frontend development is changing because of AI

What makes this role different

• You won’t just build UI - you’ll shape how users interact with complex systems
• You won’t just consume APIs - you’ll influence how they’re designed
• You’ll have a real impact on the product, not just implementation
• You’ll work on problems that are messy, ambiguous, and actually matter
• You’ll help define what frontend engineering looks like in an AI-first company

Stack (for context, not as a checklist)

• React (Functional Components)
• TypeScript (deep, not surface-level)
• State management (Redux / React Query / modern patterns)
• Modern frontend architecture
• Testing (Jest, RTL, Cypress)
• Web performance & scalability
• If you want to “build UI”, this isn’t the role.
• If you want to build systems, own product experience,
• and rethink what frontend engineering actually means - we should talk.

Super competitive compensation for the right people!