About
I'm Dragan Lalos, an engineering leader based in Frankfurt. I build and scale teams and platforms in B2B environments-especially when growth exposes weaknesses in architecture, operations, and delivery. This page is a public snapshot of how I work: the principles I use, how I operate day-to-day, and the problems I'm typically brought in to solve.
Principles
Make outcomes measurable.
Define success with clear operational and delivery metrics (SLIs/SLOs, cycle time, incident impact) so engineering decisions stay grounded.
Design for ownership.
Clear boundaries, explicit decision records (ADRs), and end-to-end responsibility beat process-heavy coordination.
Stability enables speed.
Reliability practices aren't "extra work"-they remove drag and make product delivery predictable.
What I do
- Scale teams: hiring, structure, leadership layers, and clear expectations that support growth without chaos.
- Scale platforms: modernization, reliability engineering, and performance work so systems stay resilient under growth.
- De-risk delivery: operating cadence, metrics, and execution systems that make delivery predictable and aligned with goals.
How I operate
- Priorities: a tight quarterly focus with explicit trade-offs and clear owners.
- Metrics: delivery flow (lead time, deploy frequency) and reliability (SLIs/SLOs, MTTR) tied to outcomes.
- Rituals: lightweight planning, strong reviews, and consistent incident learning-not bureaucracy.
- Decisions: document the "why" (ADRs) and keep architecture aligned with product strategy.
Where I'm strongest
- Modernization programs (monolith to services, platform enablement, migrations)
- SLO-driven reliability and incident response
- Delivery systems (CI/CD, release engineering, quality gates)
- Stakeholder alignment and executive communication
Values: clarity, ownership, measurable outcomes.
If you’re navigating growth pressure and want to sanity-check an operating model, share a short note with context. If there’s a real match, we’ll go deeper.