Product Engineer

This is not a traditional engineering role.

The expectation is not just writing good code.

The expectation is building products people actually use.

The ideal person for this role has experienced product-market fit firsthand.

Not through courses, frameworks, or podcasts.

Through shipping, scaling, failing, iterating, and understanding user behavior deeply.

Strong full-stack fundamentals are important.

But engineering skill alone is not enough.

This role requires product instinct:

• Understanding why users behave the way they do

• Knowing what to build vs what not to build

• Making fast product decisions with incomplete information

• Caring deeply about user experience and interaction quality

At Leap, the products being built are AI-native from day one.

Not traditional products with AI layered on top.

Products are designed around the latest model capabilities across reasoning, voice, search, workflows, video, and personalization.

The ideal candidate is already deeply immersed in this space.

Someone who:

• Constantly experiments with new models and tools

• Has strong opinions on model strengths and limitations

• Uses AI heavily while building

• Naturally optimizes for speed and execution quality

• Thinks in terms of products, not just features

• Who started building early and has been tinkering with products for years. 

This role involves working directly with the founders in a high-ownership environment where:

• Thinking is challenged directly

• Speed matters

• Clarity matters

• High agency is expected by default

Signals of a strong fit:

• Graduated in 2023 or later

• Has built and shipped products with real users

• Strong full-stack engineering capability

• Comfortable operating in ambiguity

• Learns and iterates quickly

• High ownership and execution intensity

Applications should include something real:

• A product

• A side project

• A prototype

• A shipped experience

• Anything that demonstrates ownership and product thinking

If there is no live link, applications should include:

1. What was built and why?

2. Why were those features chosen?

3. Why is the product better than alternatives?

4. What is the most delightful part of the experience?

5. What is the go-to-market strategy?