Product Engineer

Hi! I’m Agry, technical co-founder at Nejo. We’re looking for someone to help us fix job search and recruiting for good.

Job search is broken for everyone involved, and we’re building the thing that changes that. Over 350,000 people already use Nejo, and our users tell us they’ve finally found something that “gets” what they’re looking for.

As our Product Engineer, you own what we build next: from the user problem all the way to the shipped feature and the data that proves it worked.

What “Product Engineer” means at Nejo

Not a coder who receives tickets. Not a PM who hands off specs. One person who drives a feature end to end:

1. You talk to users and dig through data to find what’s worth building.

2. You write the spec yourself: the hypothesis, and how you’ll measure success.

3. You drive the implementation, using AI tooling aggressively but never blindly.

4. You ship, then go back to the same users, gather feedback, and iterate.

The outcome is yours, but the build is always a team sport. You know when to pull in your colleagues, and you coordinate them efficiently instead of grinding through everything alone. Owning a feature here means orchestrating the people around it, not locking yourself in a room with it.

Who this role is for

Two backgrounds fit. You’re one of these:

• The engineer who wants more than code. You have a solid software engineering track record, and you’re energized, not threatened, by the fact that pure coding is becoming the lesser part of the job. You want to be the one talking to users, making product calls, taking architecture decisions and owning outcomes. Not just implementation.

• The product person who became technical. You come from product, and you’ve used AI to push way past writing specs from a user’s perspective. You can drive implementation yourself, with a self-taught technical understanding deep enough to ship things far beyond “vibe-coded”. You know what production quality means, and when you’re out of your depth.

Our stack

Whichever of the two you are, this is what you’d be working with. Ideally you’ve worked with most of it professionally before:

• TypeScript end to end

• React + TanStack Start

• Typed Node API

• Python data pipelines

• NoSQL, search engine, vector DB, key-value caches

• Azure Foundry (LLM)

• Analytics, tracing, CI/CD

We love working AI-assisted, and yet we curse this new way of working at least once a day. Ideally you can relate, and you understand context engineering and what it takes (mentally and physically ;)) to stay in charge when working with AI. We use Claude Code, but we’re fine if you prefer a different tool.

How we build

We believe a 10x better product starts with understanding our users deeply.

• We build on evidence, not opinions. Every feature starts with a user-impact estimation and ends with data validation.

• “You think” always yields to “users show.” Everyone here immerses themselves in our users’ world, regardless of role.

What you get: the most ownership you’ll find outside founding your own company

• Extreme transparency: You’ll always know where the company stands and what we’re aiming for next.

• Genuine ownership: Direct work with the founders, and a salary of €60,000 to 65,000 plus company equity.

• Real users, weekly: Regular contact with actual users of a fast-growing platform.

• Vienna office, self-directed: We work together in person because we enjoy it. Home office is yours to decide. No daily standups, no unnecessary meetings.

We’ve built a team that genuinely cares about each other while caring deeply about our business. We’re more a group of friends on a shared mission than traditional colleagues.

Interview process

Straightforward and respectful of your time. We know great candidates have options, and we promise feedback at every stage and aim to move quickly.

1. Initial conversation with a founder: your background and our vision.

2. Product-and-tech deep dive: real problems we’re solving, plus a practical exercise that mirrors the actual work, from user problem to proposed solution.

3. Final meeting with the team: to make sure it’s a mutual fit.

Sounds like your next role?

Apply here and send us what you’ve shipped: a repo, a product, a story.