Oleksandr Khotemskyi

Engineering leadership for systems that matter

I make complex systems feel boring.

I’m Oleksandr Khotemskyi — an engineering leader with deep quality roots. I turn fragile delivery into calm releases, unclear ownership into working systems, and AI hype into practical engineering leverage.

Read the story Talk on WhatsApp
Portrait of Oleksandr Khotemskyi
Based in Kyiv,
Ukraine
A release should not be an event. It should be a quiet consequence of a system that works.

I started in software quality more than fifteen years ago. That gave me a useful instinct: look for the way a system can fail before it becomes someone else’s emergency.

Over time, the scope grew. Test automation became delivery architecture. Release checklists became operational design. Incident calls became on-call systems, observability, ownership, and faster recovery.

The job was never “find more bugs.” It was to help engineering ship with confidence — and recover without panic when reality disagrees with the plan.

01 / Make it reliable

From release theatre to release routine.

I inherited a process built around chat messages, manual confirmation, and anxiety. We rebuilt it into a calm, documented workflow that needs minutes of attention — not a room full of people.

Release operations

A production event
A boring routine

Automated workflows, clear validation, practical rollback paths, and ownership that survives handovers.

Incident response

Everyone joins
The right people act

On-call rotation, access by responsibility, escalation, status communication, postmortems, and prevention work.

Engineering enablement

More tooling
More leverage

Cost-aware CI/CD, testing infrastructure, and vendor decisions designed around outcomes — not platform fashion.

02 / Multiply the team

AI belongs inside the workflow.

I’m not an ML researcher. I’m an experienced integrator: I connect existing AI capabilities to the places where engineers lose time, context, and attention.

Agents and reusable skills

Purpose-built helpers for repeatable engineering tasks, with real context and clear guardrails.

AI-assisted development

Practical workflows for coding, investigation, documentation, test design, and requirements analysis.

Team adoption

Turning personal experiments into shared processes that engineers can trust, inspect, and improve.

Evaluation over theatre

Start with the bottleneck, measure the gain, keep humans accountable, and drop what does not help.

03 / Founder, CyborgTests

I shipped the workflow I kept needing.

I founded CyborgTests: a Playwright-native way to keep human judgment inside an automated test. Not a second tool. Not AI theatre. A pause where eyes still matter — then the run continues.

04 / Lead beyond the org chart

A decade of making engineers stronger.

Hot Testing grew from a small Protractor.js group into a recognized Ukrainian quality engineering community. It taught me how to lead without authority: earn trust, explain hard things clearly, and keep showing up.

10≈
years building
the community
3,500+
YouTube
subscribers
3,600+
Telegram
subscribers
1,000+
students
trained
100+
talks, workshops
& presentations

This is not a side-note. Community work is proof that I can create momentum across teams, levels, and companies — and translate deep technical ideas into action.

05 / Know what “critical” means

Technology is never just technology.

My career also includes two environments where consequences are immediate: military service and intensive care. They changed how I think about clarity, responsibility, and the people on the other side of a system.

2022 · Ukraine

State Border Guard Service

Served as a soldier during the full-scale invasion, formally in a medical role, including service in the Bakhmut area. Worked with coordination, records, accountability, and logistics in a chaotic operational environment. Combatant status (UBD).

Medical background

Diploma + ICU nursing

Medical diploma as a junior specialist in nursing, followed by six months working in intensive care in Kyiv with postoperative and emergency patients.

06 / Stay hands-on

Enough depth to ask better questions.

I lead through systems thinking and technical credibility. I can read the code, follow the request, inspect the pipeline, challenge the release plan, and work with specialists without pretending to replace them.

Built and operated around

  • TypeScript / JavaScript
  • Node.js
  • Python
  • Playwright
  • Selenium
  • API & contract testing
  • CI/CD
  • Release operations
  • Feature flags
  • Observability
  • Incident response
  • Docker
  • Cloud test infrastructure
  • Performance testing
  • Distributed test farms

No inflated expertise

  • Hardware & embedded: home-level familiarity, not professional experience.
  • Kubernetes: an informed user of Kubernetes-based environments, not a platform specialist.
  • Security: experienced in cross-functional delivery and risk conversations, not positioned as a security engineer.
  • AI: engineering integrator and workflow builder, not an ML scientist.

Why this matters

I know where I can be useful.

Not by pretending to be an embedded engineer. By helping software-heavy products and engineering teams where failure has real cost become more reliable, more observable, faster to improve, and easier to operate under pressure.

Find the risk Build the guardrail Clarify ownership Ship calmly Learn fast

I bring engineering discipline without bureaucracy — and urgency without chaos.

The shortest section

Want to contact me?

If you are building technology where reliability has real consequences, I would like to hear what you are working on.

Message me on WhatsApp