Product Engineer

„We don’t need someone who can build what we spec. We need someone who can figure out what to build.“

 

You’ve shipped products. Not features – products. You’ve made decisions about what to build, argued about scope, cut things that weren’t working, and watched real users interact with your work. You’ve developed taste. You know when something feels right and when it doesn’t.

You’ve also figured out how to move absurdly fast with AI. You see a problem, open Claude Code, and it’s fixed in minutes. That’s not a party trick – that’s how you work now.

You want to own something from the ground up.

 

The Role

You’ll own a product area at BigBongo. Not tickets. Not features. An outcome.

 

Your cycle:

1. Notice something that needs to be better (from feedback, data, your own judgment)

2. Decide what to build or change

3. Build it with Claude Code – often in minutes

4. Ship it

5. See if it worked

6. Repeat

 

There’s no Jira. No one assigns you tasks. You’ll receive strategic direction from leadership, then you figure out the rest.

 

What You’ll Actually Do (A Real Week)

Monday: You watch yesterday’s user session recordings. Something’s confusing in the onboarding flow. You don’t file a ticket. You open Claude Code, explore the fix, ship it before lunch. The whole loop – noticing, deciding, building, shipping – took 20 minutes. Record a video showing what you changed and why.

Tuesday: Founder feedback video points out an edge case you missed. You fix it in 10 minutes, then realize the whole feature could be simpler. You simplify it. Ship again.

Wednesday: Deep work. You’re building a new capability that will take a few days. You’ve already decided the scope-what’s in v1, what’s not. No spec doc. You know what matters.

Thursday: Your feature is working but feels clunky. You iterate on the interaction three times until it feels right. Ship to staging, record a demo.

Friday: Team sync. You show what you shipped. Someone suggests an improvement. You decide whether it’s worth doing now or later. You decide-not a PM, not a spec.

 

What You Bring

 

Product ownership experience

You’ve shipped products where you decided what to build, not just how. You’ve made trade-offs, cut scope, killed features. You have opinions about what makes products good.

Taste

You know when something feels off. You simplify by instinct. You care about whether it works for users, not just whether it works technically.

Technical fluency

You understand how software systems work. You can verify AI output, debug problems, make reasonable architectural decisions. You don’t need to be an expert in our stack-you need to learn fast and know enough to build well.

AI-native workflow

Claude Code is your primary building tool. You’ve invested in your prompts, your workflows, your setup. You’re not just „using AI“ – you’re 2-20x faster because of it. This isn’t optional. It’s how we work.

Things are moving fast in AI tooling. You stay curious — you try new techniques, read about what’s working for others, and share what you learn with the team. Everyone here does this. Getting better at working with AI is a continuous thing, not a one-time setup.

Builder energy

You ship things. You can’t not build. Shipping weekly feels slow to you.

 

The Tech (And Why It Doesn’t Matter Much)

 

We use Python, Django, PostgreSQL, Linux, Tailwind + JS (Later React).

But here’s the thing: with Claude Code, specific stack knowledge matters less than it used to. What matters is:

– Can you learn fast?

– Can you make good decisions about what to build?

– Can you verify that what you built is correct?

 

If you’ve shipped products in any modern stack and you’re technically fluent, you can work here.

 

What Success Looks Like

Month 1: You’ve shipped multiple improvements to your area. You’ve made decisions without asking permission. Some were right. You learned from the wrong ones.

Month 3: Your area is noticeably better. Users or metrics confirm it. The team trusts your judgment.

Month 6: You’re proposing initiatives leadership didn’t think of. You’ve killed or simplified things that weren’t working. You’ve raised the bar.

 

The Team

Small by design. 3 developers, 1 Head of Product, 1 Community/Marketing, 1 Strategic Project Coordinator, 2 founders.

 

– No PMs translating requirements

– No sprint planning theater

You’ll communicate daily via real human in person communication and async video – record what you built, watch feedback, iterate. No meetings unless they’re actually useful.

 

The founders are technical. They’ll have opinions. They’ll also trust you to make calls in your area.

 

Why This Instead of Big Tech

 

Big Tech                                                                          BigBongo

You own a feature                                                       You own a product area

PMs decide what to build                                          You decide what to build

Ship quarterly                                                                Ship daily

AI tools „being evaluated“                                         Claude Code is how we build

Employee #4,847                                                           Core team

 

The Honest Trade-offs

 

What makes this role special:

– Full ownership – you decide what to build, build it, and ship it

– Speed that feels like a superpower – problems go from noticed to fixed in minutes

– No layers between you and impact – no PMs, no sprint ceremonies, no Jira

– Founding team with real influence

 

This role probably isn’t for you if:

– You want clear specs and defined requirements before you start

– You prefer someone else to decide what’s important

– You like having specialized roles (PM decides, designer designs, you code)

 

Benefits

 

Compensation

– Competitive salary for Sofia

– Annual reviews tied to company performance

Environment

– Office in Sofia, occasional at-home work

– Equipment budget-whatever you need

Growth

– Own real product outcomes from day one

– Direct mentorship from founders

– Conference/Training budget

 

Interview Process

 

1. Application Review (1-2 days) – We read your materials

2. Screening Call (30 min) – Quick check on fit and experience

3. Product Thinking Session (45 min) – We give you a real problem, you walk us through how you’d approach it

4. Paid Trial Day (compensated) – Work with us for a day on a real task

5. Offer (within 48 hours)

No leetcode. No whiteboard algorithms. We evaluate how you think about products and whether you can ship.

 

How to Apply

 

Send us:

– Products you’ve shipped – What you built, what you decided, what you learned

– Your AI workflow – Show us your Claude Code setup, your prompts, how it changes how you build. This matters a lot to us.

– Why BigBongo – What interests you about this specifically

– Something you’ve built outside of work – Side project, tool, anything