Check out my Linkedin profile for a detailed overview of my work experience and education.
Why hire me?
Over the past two decades, I've run engineering teams in a wide variety of
contexts: corporations, family-run businesses, early stage startups.
I gained experience building and running infrastructure, backend, data, frontend, and mobile systems.
In each of these contexts, a recurring theme emerged: I built many teams and systems from scratch which makes me a perfect fit to build your MVP.
I wrote detailed articles about both aspects of my career:
As a programmer, I'm the most fluent solving infrastructure, data, and backend problems. That's how I've spent most of my programming career.
What am I looking for?
So apart from some deal breakers, I can work in any capacity.
I get the most excited with infrastructure, especially development infrastructure like testing pipelines, build tools, or streaming data platforms since I have lots of experience with Apache Kafka, its ecosystem, and streaming platforms in general.
While I would advise you not to hire freelancers for leading your teams, I'm OK with ad-interim roles if a project excites me and it's the right solution for your problem. Context is always key.
I prefer working on one large, difficult problem at a time over many simple problems one after the other.
Solving one large problem at a time often leads to a long-lasting mutually beneficial working relationship because this is where my technical and leadership skills converge.
I'm good at breaking down large problems into small, simple artifacts. I can write design proposals for them and coordinate the work.
While I enjoy working pretty much on any product, do not contact me for anything blockchain, and military related.
- The technological stack is highly relevant to me.
- The goal of the project you want to hire me for is performance related. Making systems use less resources is climate friendly.
At the moment, I cannot take 40-hour per week contracts.