Senior Product Engineer (remote, Europe)

Hey, I'm Dima . I lead a product engineering team at Modash, and I’m hiring a Senior Product Engineer to help us turn messy customer problems into simple, useful products.

Why we're hiring

Modash looks simple on the surface. Underneath, it’s a data-heavy product with complex workflows, search, integrations, reporting, automation, attribution, and payments.

We have around 20 engineers across four product teams. We need senior engineers who can get close to customers, make product and technical decisions, work across the stack, ship, and stay accountable for whether the solution actually works.

This isn’t a narrow frontend or backend role, and it isn’t a ticket factory. You’ll own problems end to end.

If you want a feel for how we build software, check our Engineering Blog .

What you'll actually own

1. Turn customer pain into product decisions.

You’ll understand what users are trying to achieve, where they get stuck, and what the simplest useful solution looks like. You won’t wait for product or design to hand you every answer.

2. Take work from problem to production.

You’ll shape the approach, design the system, build across the stack, ship it, measure what happens, and improve it. Senior engineers here own outcomes, not just implementation.

3. Build across deep product surfaces.

Depending on the team, you might work on:

• Discovery: take a huge creator pool and get a marketer to “these are the ones” fast enough that they start a list, not another search.
• CRM: make managing hundreds of creator relationships feel as easy as managing a handful.
• Campaigns: turn a flood of creator posts into two answers: did this campaign work, and how do we make the next one better?
• Creator: get a sale tracked and the creator paid without invoices, vendor onboarding, or anyone chasing the money.

4. Raise the quality of decisions around you.

You’ll ask better questions, challenge weak assumptions, give useful feedback, and help the team move without waiting for perfect certainty.

What the day-to-day looks like

Here’s what a typical week might include:

• Monday. You watch a customer struggle through a campaign workflow and realise the missing button they requested won’t solve the real problem. You map what they’re trying to do and propose a simpler approach.
• Tuesday. Deep-focus time. You build the first useful version across Vue and Node.js, including the required data-model changes.
• Wednesday. You review the approach with product and design. A polished concept would take six weeks; a narrower version could validate the important behaviour in one. You make the tradeoff explicit and get it moving.
• Thursday. A third-party integration starts behaving inconsistently. You trace the issue through asynchronous jobs and improve the failure handling for customers.
• Friday. You review what happened after launch. Adoption is lower than expected, so you speak with users and ship an improvement rather than declaring the project finished.

We keep meetings purposeful and protect time for deep work. You’ll collaborate closely with engineers, product, and design, while having the autonomy to create clarity and move work forward.