Purpose

The Head of Engineering Operations owns how we build software at the company. They ensure that our engineering processes, tools, and data support fast, reliable, and predictable delivery of a high-quality SaaS product. This role is hands-on in automation and tooling, but its real impact comes from establishing best-practice ways of working and making them stick.

Core Accountability

• Full ownership of company’s engineering processes — defining, implementing, and improving how code moves from idea to production.

• Ensure that our development, release, and monitoring systems reflect modern SaaS best practice.

• Build the data foundation that makes engineering performance visible and actionable — ensuring that logs, metrics, and process data are structured, collected, and automated across systems so that product reliability, delivery efficiency, and incident trends can be measured and improved continuously.

Responsibilities

1. Own and continuously improve how we build software.

Take accountability for company’s engineering process end-to-end — from planning and development to testing, release, and follow-up. Identify gaps, introduce best-practice workflows, and make sure they are automated, measurable, and followed.

2. Build and maintain enabling systems

Be hands-on in establishing the CI/CD, monitoring, and observability stack. Own key operational tools (Grafana, Prometheus, JIRA workflows, alerting integrations) and make sure they serve both developers and leadership.

3. Make performance measurable

Structure and automate data collection so we can track product reliability, team efficiency, and system health. Enable dashboards and alerts that highlight deviations before customers do.

4. Enforce delivery discipline

Ensure planning, estimation, and retrospectives follow consistent patterns across teams. Hold us accountable to our own processes — enforce JIRA hygiene, close the loop on learnings, and ensure definition of done is met in practice, not just in theory.

5. Partner and influence

Work across engineering and product teams to align ways of working and priorities. Partner with the CTO on engineering strategy — aligning technical direction with operational reality. Translate strategic objectives into process, tooling, and data improvements that make the organization faster, safer, and more predictable.

Profile

•  Experienced software engineer who still codes and automates.

•  Has worked in or closely with a modern, successful SaaS company and knows what best practice looks like in reality.

•  Passionate about processes, automation, and developer experience.

•  Analytical and data-driven — methodical about turning metrics into improvement.

•  Pragmatic, not bureaucratic — believes that process should serve speed and quality, not slow them down.

•  Based in the Lund region (~50 % in-office).

•  Bonus: AWS infrastructure design, QA process design, or experience introducing observability systems.

Authority and Evolution

Initially operates through influence and data, demonstrating impact by improving visibility and discipline. As systems and trust mature, the role gains formal authority over release and delivery processes. The role is intended to evolve into a managerial position leading engineering operations and developer productivity.

Why This Role Matters

Our success depends on how efficiently and reliably we can build and ship software. This role closes the gap between what we want to deliver and how we deliver it — ensuring that quality, speed, and learning are built into our everyday way of working.

Location: Lund, Sweden.

Reports: directly to CTO.

Contact:
johan.nilsson@inducon.se / +46 735 340 200