CV
Maksym Lukianov
Head of Engineering at OTAKOYI · Lviv
I make engineering predictable through architecture, explicit decisions, delivery systems, and risk control. What I bring is clarity of decisions. Written down, reviewed, and still legible to the team a year later.
- Lviv, Ukraine
- Web engineering since 2006
- Ukrainian · English
- Consulting · engineering transformation
The English PDF opens in a new tab; save it using your browser controls.
Expertise
Where I create system-level outcomes
Architecture and legacy modernization
Incremental migrations, service boundaries, event-driven and microservice architecture where load and ownership justify them.
Engineering leadership
Standards, assessment, competency roadmaps, ownership, and delivery risk as one manageable engineering system.
AI-enabled product engineering
SDD/MAE, specifications as executable contracts, LLM workflows, and controlled legacy support.
Full-stack delivery and performance
Web platforms, APIs, data, cloud, quality, SEO, and safe change from architecture decision to production.
Internal OTAKOYI operating measurements
Context for claims, not decorative numbers
4 projects · 9 engineers
SDD delivery
Actual SDD delivery hours were 60–70% below prior manual-work estimates; defects measured at 5–7% of the previous level.
Weekly → rare
Legacy modernization
After staged modernization, failure incidents moved from approximately weekly to rare; infrastructure cost increased.
51 assessments · 26 engineers
Engineering assessment
In 2026, the system identified 18 engineers in a technology-stack compatibility risk zone.
Internal, owner-attested measurements; not independently audited client outcomes.
Experience
From web engineering to an engineering operating system
Now
Head of Engineering · OTAKOYI
I own engineering standards, architecture decisions, technical presale, inherited-system audits, team formation, delivery control, and engineering-function development.
Since 2006
Web foundations
Markup, interfaces, and frontend formed the engineering base — performance, accessibility, and clear contracts.
Since 2011
Co-Founder · OTAKOYI
Building the company and delivery teams, working with client context, and covering the full digital-product lifecycle.
Next stage
Full-stack · Tech Lead · Team Lead
Moving from individual implementation to architecture, standards, team ownership, and predictable delivery.
Current focus
Engineering organization
Legacy modernization, platform scale, competency systems, AI-enabled delivery, and transformation-risk control.
Approach
How I work
- A decision lives in a document, not in someone's head. ADRs and specifications instead of hearsay.
- Module boundaries, contracts, and ownership come first; tooling follows.
- If a task is outside my responsibility, I say so directly and point to a viable direction.
Writing
Read this instead of a first interview
Architecture decisions, migrations, performance, and engineering clarity are already examined in public work — a fast way to see whether our thinking aligns.
Sounds like your problem?
Describe where the system stalls — architecture, process, team, or AI adoption. I lead the diagnosis personally; when implementation capacity is needed, the OTAKOYI team can join.