You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Secfix

Head of Product Engineering

  • Remote
  • 6+ years

Salary

Not stated

Similar roles pay €80K - 130K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The hiring manager is Grigory, co-founder and CTO of the company.

The company builds security compliance software that helps teams become and stay compliant with less effort. It is the category leader in Europe.

AI is changing how software is built, and the team is helping define the tools for that shift.

The team has 8 engineers and 2 product designers. The CTO still runs engineering leadership himself, including 1:1s, hiring, design reviews and performance conversations, and is stretched thin.

The company needs a leader who can still build, owns engineering end to end, and has strong product judgement. You will work directly with the CTO.

Over 1.78 million SMBs in Europe must meet frameworks such as ISO 27001, GDPR, TISAX and SOC 2 before enterprise customers will buy. The work is manual and can take over a year. The platform connects to a company's full tech stack, collects compliance evidence automatically, and gets teams to certification in weeks. The fastest customer was certified in 4 weeks, against the 12+ months usually expected.

The company has raised €17M in total, including a €12M Series A from Alstin Capital, Neosfer (Commerzbank) and Bayern Capital. It is profitable, growing fast, and aims to serve European companies from SMBs up to mid-market.

Its new AI product, CISO AI, is early, with a large amount of engineering work ahead in agentic workflows, intelligent evidence collection and context-aware policy generation.

Responsibilities

  • First 3 months: in month 1, ship a meaningful AI feature in the codebase with the team, showing that you build to the standard you expect and ask the right questions.
  • Month 2: find features that take 3 weeks but should take one, and fix the cause through tooling, testing and review, or how work is assigned. Start regular 1:1s with each engineer on weekly output, quality and use of AI.
  • Month 3: take over engineering hiring with a process that runs without the CTO. Decide how the team is organised as it grows and which lead roles to hire or grow first. The CTO moves to final interviews.
  • After the first quarter, you run engineering: its direction and organisation. You own how engineers test, review each other's code and security changes, how the team is structured, and who gets hired next.
  • The team is expected to grow from 8 engineers and 2 designers to about 16 within 12 months, with most of that hiring led by you.
  • You will still build with the team now and then, though not every week.
  • Speed: own cycle time from spec to production and keep refining processes, tooling, review flow and how work is split.
  • Quality: improve how engineers test and automate, and how they review code and security changes. Keep the zero-bug policy working as the team grows toward 20.
  • Leadership: shape team structure, run performance reviews, own the hiring plan, and develop the managers and tech leads.
  • AI: keep building out the team's encoded skills and rules, and apply AI to your own work such as hiring and 1:1s.
  • Success at 6 months: you are one of the strongest performers and have coached others to improve. You own the agentic engineering playbook and keep improving it. New hires are productive in their first week, AI review catches issues before humans see them, and cycle time falls without quality dropping. Hiring runs without the CTO and has added 2 engineers. Sales, CS and product notice faster and better shipping.
  • Success at 12 months: the team is 12-16 people, the zero-bug policy still holds, and the CTO is no longer on the engineering critical path. You have hired or grown the first engineering leads, and the structure can handle the next doubling.

Requirements

  • Required: 10+ years as a software engineer, including 6+ years leading engineering teams and 2+ years managing managers or tech leads.
  • You have grown an engineering team to 15+ at a VC-funded startup and hired most of it yourself, and you have been through the messy middle.
  • You have built the basics a growing team needs, such as hiring process, levels, performance reviews and salary bands, and kept them lightweight.
  • You have shipped AI features to production, such as retrieval, RAG or agentic workflows, and you can tell a working demo from one that holds up on real customer data.
  • You have strong product taste and say so when something falls short.
  • You have built and shipped with Claude Code and Cursor in production work, and you have a view on where AI helps and where it adds debt.
  • You were a senior or principal engineer before managing, and you can still contribute in a design review, a debugging session or while building a feature.
  • You have built something zero to one at a startup, or scaled a team through the messy middle, and you are comfortable without a playbook.
  • You work in the CET/CEST time zone and are based in EMEA, ideally in Germany or the UK.
  • You have grown an engineering organisation past 20 in the AI era.
  • You have taken an engineering team through an ISO 27001 or SOC 2 audit.
  • You have led engineering for a B2B SaaS product moving from SMB into mid-market.
  • You have led an engineering org and made it ship faster, and can point to cycle time you reduced.
  • You can recognise strong engineers quickly, understand what makes them productive, and know how to develop them.
  • You have an exceptional IC record before becoming a manager and did not move into management because coding was not working out.
  • You are comfortable giving direct feedback and having hard performance conversations.
  • You have used Cursor and Claude Code in real production work and want to push a team to move faster with AI from ideation to release.
  • You have worked at startups and are fine with low process where the answer is to figure it out and ship.
  • You believe a small, high-performing team can keep a startup culture as it grows with little process.
  • You communicate proactively in writing, since decisions and context are shared that way on a remote team, and you are comfortable pair programming.

Conditions

Interview process: a 30 minute intro call with the talent team, a 45 minute interview with Grigory, a 60 minute technical interview, a 5 hour AI-assisted build session covering system design for a real feature and building part of it with AI, and a 2 hour leadership session with the founders. You receive an offer at the end, and if none is made you are told why.

Engineers have fewer than 2 hours of meetings per week. Writing comes before meetings. Loom handles async walkthroughs, Notion holds specs, Gather is used for pairing, and Slack is for urgent or light messages. There are no status meetings.

Work happens in small temporary teams, such as a designer with two engineers, formed around a problem and disbanded after shipping. There are no standing squads for now, and the people closest to the problem usually shape the solution.

AI is part of daily work. Claude supports design exploration and spec drafting. Engineers use Cursor with encoded skills and rules in the codebase covering components, folder structure, architecture and the Figma to Angular path. AI checks code against architecture rules before human review, and a design QA skill compares Figma with the coded output. AI is used to reach the bar faster, not to lower it.

Zero bugs is a firm policy because trust is central in compliance. Critical issues are fixed immediately, high-severity issues within 48 hours, every bug has an owner, and quality is reviewed weekly during Monday planning. Serious customer-facing problems are not left in a backlog behind roadmap work.

Customer feedback is treated as signal, not instruction. The team stays close to customers through CS check-ins, support tickets, Mixpanel events and onboarding calls, but none of these makes product decisions alone.

Salary is competitive and benchmarked to European market rates. Specifics are shared during the conversation.

Benefits

  • 100% remote work, with a virtual office in Gather.
  • Generous equity, since everyone here is an owner.
  • Development budget of €1,000 per year, to spend on anything that improves your work.
  • Remote workspace support and co-working access.
  • 26 days of holiday plus local public holidays.
  • Comprehensive health insurance.
  • An annual team retreat. Past destinations include Alicante, the Austrian Alps, Portugal, Italy and the Spanish Islands.
  • Latest MacBook, monitors and headphones.

Where you’d work

Fully remote

You can work from

  • Europe
  • Germany

About the company

Secfix

2 of their 2 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 18 checks run
  • 1 red flag

Still hiring?

12 checks

No red flags

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation, Employment
Tech stack
  • AWS
  • Angular
  • Azure
  • RAG
  • Figma
  • Jira
Seniority
Head of
Type
Contract
Equity
Equity offered
Specialty
Product Manager
Region
Europe
Show 6 more factsShow less

Role

Category
Product & Project
Specialty
Product Manager
Seniority
Head of
Experience
10+ years
Tech stack
  • AWS
  • Angular
  • Azure
  • RAG
  • Figma
  • Jira

Location

Work model
Remote
Region
Europe
Remote from
  • Europe

Compensation

Salary
Salary by agreement
Pay period
Annual
Equity
Equity offered

Employment

Type
Contract

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason