Location: Stockholm, Sweden
Email: tomas.lindqvist@example.com
Phone: +46 8 123 4567
LinkedIn: linkedin.com/in/example
Engineering Lead with 12 years in software and 6 leading teams of 6-12 engineers. Comfortable owning both the architecture and the delivery: I still review designs and write code, and I run the hiring and growth side of the team. Looking for a lead role at a company where the hard problems are technical rather than political.
Deploys had become a queue: eleven teams shared one release train, and a bad change from any of them blocked everyone. Led an 18-month split of the order and fulfilment domains into 22 services across 9 bounded contexts, peeling out one context at a time and dual-writing during each cut-over so nothing went dark. Release cadence went from fortnightly to on-demand, and teams stopped coordinating deploys with each other.
Offer-accept rate was 48% and two hires in a row left within a year. Rewrote the loop around a work-sample exercise reviewed blind, replaced the whiteboard round, and wrote a scoring rubric interviewers actually filled in. Time-to-offer dropped from five weeks to twelve days, and offer-accept reached 81% over the following 18 months.
The team was paged 60-70 times a month and two engineers were close to leaving over it. Spent a quarter treating alert noise as a project rather than a chore: deleted alerts nobody acted on, replaced threshold alerts on symptoms with alerts on customer impact, and required every remaining alert to name a runbook. Pages fell to under 15 a month with no increase in missed incidents, measured against customer-reported outages.
Engineering Lead | Jan 2020 - Present
- Lead 2 squads (11 engineers) across order management and fulfilment.
- Own architecture review for the domain; set the service boundaries and the deprecation path for the monolith.
- Run hiring for the group: 9 engineers hired, and rewrote the interview loop.
- Still hands-on: Java (Spring Boot), TypeScript, code review daily.
- Report delivery risk to the CTO and negotiate scope with product leadership.
- Introduced written design docs for anything touching more than one service, and a two-week RFC window before large changes.
- Run the incident review process: blameless postmortems with owned follow-up actions tracked to completion.
Senior Engineer, then Tech Lead | Sep 2015 - Dec 2019
- Grew from IC to leading a team of 6 on a B2B analytics product.
- Designed the ingestion pipeline handling 8M events/day on Kafka and ClickHouse.
- Introduced trunk-based development and a CI gate, moving the team from monthly to weekly releases.
- Mentored three engineers into senior roles.
Software Engineer | Jun 2012 - Aug 2015
- Built customer-facing features in Java and JavaScript for an insurance platform.
- Took over the release process and automated it, removing a two-day manual checklist.
- Team: Hiring, performance reviews, career development, running 1:1s.
- Delivery: Roadmap planning, scope negotiation, dependency management, incident command.
- Communication: Translating technical risk for executives; written design docs and RFCs.
- Languages: Java (Spring Boot), TypeScript, SQL.
- Architecture: Domain-Driven Design, event-driven systems, service decomposition.
- Infrastructure: Kubernetes, Kafka, PostgreSQL, ClickHouse, GitHub Actions.
- Practices: Trunk-based development, design docs and RFCs, blameless postmortems, contract testing.
- NDC Oslo, 2024 - "Splitting a monolith without stopping the world": what dual-writing costs and when it is worth it.
- Internal engineering blog - series on service boundaries, design docs, and running incident reviews people are willing to attend.
MSc Computer Science | 2010 - 2012
- Swedish: Native.
- English: Fluent.