Andrii Panchenko

Backend engineer working on services that run unattended — data ingestion, third-party integrations, and the operational layer that decides what happens when an upstream system changes shape without warning.

Comfortable owning a service end to end: schema, delivery, deployment, and the alerting that tells someone when it has stopped doing its job.

Senior Backend Engineer

• Replace with a result, not a responsibility — what changed because you were there.
• One line on scale where scale is the point: throughput, data volume, users.
• One decision you would defend in an interview, and the reason behind it.

Backend Engineer

• Replace with a result, not a responsibility.
• Something that broke and what you changed so it stopped breaking.

Software Engineer

• Replace with a result, not a responsibility.

Booking notification bridge

A booking platform's mobile app allows only one account signed in at a time, so a two-salon operator never saw notifications for the second one. Email was the only event source: no API, no calendar sync.

• IMAP IDLE ingestion of two mailboxes, with reconnection and a watchdog that restarts a session that has gone quiet at the protocol level.
• A parser over five message templates that reconstructs bookings, reschedules and cancellations without any booking identifier — the templates state the previous slot, which is enough to match on.
• A calendar UI and a chat bot over the reconstructed schedule, both refusing to claim free time for dates whose hours were never provided.

TypeScriptNodeSQLiteDockerCloudflare Tunnel