Frontend Engineer

About DICE

DICE is a venture builder operating on a Build, Buy & Scale model. We don't just invest — we operate.

We're a distributed team across New York, Istanbul, Ankara, and remote, building and scaling companies from zero to seven figures in ARR. Our technology team consists of 14 passionate individuals.

Our thesis is simple: AI has democratized product creation. The moat is no longer building — it's how fast and how well you can scale what you build. That's where this role lives.

The engineering team makes that scale possible.

The Role

We're looking for a Frontend Engineer who can ship polished, reliable interfaces across multiple DICE portfolio products — on both web and mobile. You won't be styling a single static marketing site. You'll build the customer-facing surfaces.

The core stack is React, React Native, and Redux. Our products are powered by a NestJS backend, so you'll be working against its REST APIs daily — you don't need to write NestJS, but understanding how the backend is shaped will make you far more effective.

What You'II Do

• Build and ship user interfaces for web (React) and mobile (React Native) across the DICE portfolio
• Manage application state cleanly with Redux — predictable, debuggable, and not a tangle six months from now
• Integrate against REST APIs served by our NestJS backend, handling loading, error, and edge states properly rather than for the happy path only
• Translate design into product — work directly with design and the founders to turn Figma into something that actually feels good to use
• Own quality end to end — responsive layouts, accessibility basics, performance, and the small details that separate a product that works from one people trust
• Write code that survives — readable, componentized, and clear to the next engineer who touches it
• Learn fast. New portfolio companies bring new domains — fintech-adjacent, mailroom logistics, subscription apps, e-commerce. You won't be in your comfort zone for long, and that's the point.
• Hands-on experience building AI pipelines and working with LLMs. This is the part we care about most. We're looking for someone who has built with AI: written and iterated on prompts, chained model calls together, wired LLM APIs into a real product, or set up workflows where a model actually does part of the work.

What You'II Bring

• Strong React experience — you understand hooks, component composition, and rendering behavior, not just how to assemble a UI library
• React Native experience — you've shipped or meaningfully contributed to a mobile app, not only built web
• Solid Redux — you know when state belongs in Redux and when it doesn't, and you can keep a store maintainable
• Comfort consuming REST APIs — you can read an API contract, integrate it, and handle real-world failure cases
• Product instinct — you care how it feels for the user, not only whether it renders
• Ability to learn new technologies quickly — our stack and our domains evolve; you move with them without hand-holding

Nice to Have

• Familiarity with NestJS or another structured Node.js backend (so you can read the API source, not just its docs)
• Experience with TypeScript across a React / React Native codebase
• Exposure to AI-assisted development workflows — you use modern tooling to ship faster, not despite it
• Track record working across multiple products or a small team where you owned the frontend rather than a slice of it
• Eye for design and motion — you can take a rough spec and make it feel finished

Why DICE

• Real ownership. You'll own entire frontends, not tickets handed down through three layers of management.
• Direct line to decision-makers. You talk to the founders and product directly. Decisions happen in hours, not sprints.
• Range. Few frontend roles let you ship a B2B SaaS dashboard, a consumer mobile app, and internal tooling in the same quarter. Here that's normal.
• Pace. We ship, learn, and ship again. If watching your work go live quickly is what you're after, this fits.

How to Apply

Send us:

1. Your CV and links to things you've actually shipped — App Store / Play Store links, live products, or working demos.
2. Your GitHub — the repos that best represent how you build. We'd rather read real code than a list of frameworks.
3. An answer to one question: What's the most exciting AI work you've done — and what was your hands-on role in it? A few honest paragraphs beat a polished essay. We're reading for what you actually built and decided, not how it's worded.

Apply to: [email protected]