Sample profile — not a real person

Added SLO-based alerting and rewrote the top runbooks; paging volume fell 55% in a quarter.

See the full story

Proof of work

2022

Cut incident rate 55% with SLOs + runbooks

We were paging on-call most nights and the team had stopped believing the alerts, which meant real incidents got the same shrug as the noise. I made reliability the work instead of the afterthought — rebuilt the weakest paths, deleted the alerts that never mattered, and made the ones that stayed worth waking up for.

Added SLO-based alerting and rewrote the top runbooks; paging volume fell 55% in a quarter.

PostgreSQLREST APIs
2021

Reduced cloud spend 30% without losing headroom

Batch jobs ran overnight, so by the time anyone saw a failure the window had closed and the day already started behind. I moved the critical paths to streaming, made retries safe to repeat, and turned a nightly gamble into something that just quietly kept up.

Right-sized clusters and added autoscaling; the monthly bill dropped 50% at the same SLOs.

AWSPostgreSQL
2021

Automated the release train, cutting deploys 8x

The codebase carried a decade of shortcuts, and every change touched three things nobody had written down, so estimates were fiction. I paid down the debt that actually blocked us — carved clean seams, wrote the missing tests first, and made the scary changes routine.

Replaced manual releases with a gated pipeline; deploy time dropped 4x and rollbacks became routine.

TerraformDockerKubernetes
2023

Recovered a corrupted ledger with no data loss

The pipeline lost rows quietly under load and we only found out when a customer's numbers didn't add up, which is the worst possible way to find out. I chased it to the root — backpressure, at-least-once handling, and reconciliation that proved nothing fell on the floor rather than hoping it hadn't.

Replayed the write-ahead log and reconciled balances; zero customer-visible discrepancies.

MicroservicesPythonRedis
2020

Migrated monolith to 9 services, zero downtime

Two teams were blocked on the same shared bottleneck and each was waiting for the other to move first. I designed the contract between them and the migration path to reach it, so both could ship on their own schedule instead of renegotiating scope at every release.

Decomposed the monolith behind a strangler proxy into 9 services — no maintenance window needed.

System DesignNode.jsPostgreSQLDocker

Leave every codebase clearer than I found it.

Off the clock

Locked
Node.jsDockerREST APIs
Locked
Node.jsDockerLinux

In public

Distributed SystemsPythonAWS
Locked
Redis
Locked
Node.jsPostgreSQLKubernetes
Locked
Node.js
Locked
gRPCSystem Design
Locked

Practical bits

Timezones
Europe/Africa
Location
Poland
Languages
Portuguese, Swahili, Turkish
Domains
BioTech, E-commerce
Employment
Contract · Part-time
Annual salary
Available with a company account
Social links
Available after unlocking

Reach out

Unlock with a company account to message directly and reveal:

  • Full name
  • Projects
  • In public
  • Social links

Find someone like this

Jump back to the board with this background already filtered in.