Pavel Komiagin

Who they are

Pavel Komiagin is Head of Engineering at Netology — a career-long insider who climbed from Front-end Developer to engineering lead at the same edtech company, and wrote 'Stop arguing about code style in pull requests!' on DEV Community.

Person

Pavel studied Applied Mathematics and Computer Science at Chelyabinsk State University (2007–2011), then picked up a Master's in Database Technologies at South Ural State University (2011–2013) — a dual technical grounding that bridges software craft and data. His first industry role was as a Game Developer at OrangeApps (2012–2015), overlapping with his Master's, before he moved to The.travel as a Front-end Developer (2013–2015). He joined Netology in 2015, when the company had just closed its Series A, and has grown entirely inside it: Front-end Developer (2015–2017), Senior Frontend Developer (2017–2021), Team Lead (2021–2024), and now Head of Engineering from August 2024. The through-line is depth over breadth — one company, one craft, progressively more scope. He writes actively on LinkedIn in Russian on engineering leadership, AI in software development, deployment practices, and feature flags, and published a piece on DEV Community arguing against relitigating code style in pull requests — a practical, process-first stance. He keeps a site at pavelkomiagin.ru and has picked up a Coursera certification in Front-End Web Development with React (2019), signalling he kept sharpening his IC skills even as he moved into management.

Company

Netology is a professional online learning platform operating in the Russian market, currently sitting under the TalentTech holding. The most recent structural move on record is its June 2022 merger with EdMarket, which became a division of Netology — a consolidation play to broaden its curriculum and market footprint. Its external funding history dates to a Series A in February 2015, with a total of $8.8 million raised across three rounds; no subsequent external rounds are on record, suggesting the TalentTech holding has been the primary capital structure since. Pavel joined as Head of Engineering in August 2024, stepping into the top engineering seat at what is an established, acquisition-active edtech platform.

Market

Netology competes in Russia's online professional education market alongside Foxford — which, like Netology, was acquired by Sberbank — pointing to significant state-adjacent consolidation in the sector. Broader geopolitical and regulatory dynamics specific to Russia shape the competitive environment, with market consolidation through mergers (Netology–EdMarket) reflecting an industry trend toward scale over fragmentation.

Network

Concrete named edges from Pavel's network are limited in the available data. Possibly — he engages with Gregor Ojstersek, an engineering leadership content creator, amplifying his resources on LinkedIn. Possibly — he follows and engages with Addy Osmani of Google Chrome on AI and software engineering topics.

How they likely show up

  • Spent the entirety of his post-2015 career at Netology, progressing through four distinct roles → likely thinks in multi-year arcs and values institutional context over job-hopping.
  • Moved from IC (Senior Frontend Developer) to Team Lead to Head of Engineering within the same organisation → understands the codebase and team dynamics from the ground up, not just from a management altitude.
  • Published 'Stop arguing about code style in pull requests!' on DEV Community → process-first thinker who prefers automating friction out of engineering workflows rather than debating conventions.
  • Active LinkedIn poster in Russian on deployment practices, feature flags, AI tools, and engineering leadership → comfortable making opinions public and likely responds well to substantive technical or management discussion.
  • Picked up a Coursera React certification in 2019 while already a Senior Frontend Developer → continues sharpening hands-on skills even as responsibilities grew, suggesting he doesn't want to lose touch with the craft.
  • Possibly — amplifies engineering leadership content creators like Gregor Ojstersek → probably values curated learning resources and mentoring junior developers, consistent with the stated interest in mentoring.

Conversation tips

  • → Reference the DEV Community post on pull request code-style debates — it's a specific, opinionated take and shows you've read his actual work, not just his job title.
  • → Ask about the transition from Team Lead to Head of Engineering at Netology in August 2024 — it's the freshest career move and he'll have views on what changed at that level.
  • → He writes in Russian, so if you're meeting in a Russian-language context, matching that register will feel natural; in English, acknowledge the Russian market specifics of his edtech context.
  • → Bring a concrete technical or process angle — deployment practices, feature flags, AI in development workflows are his stated themes. Vague 'leadership philosophy' questions will land flat.
  • → Don't skip his IC roots: he was a game developer and frontend engineer before he managed people. Acknowledging that hands-on background will resonate more than treating him as a pure manager.

Toolbox

Openers

  • Open on the DEV Community article — 'Stop arguing about code style in pull requests!' is a pointed, practical stance on reducing engineering friction; ask what prompted him to write it and whether the team actually adopted the approach at Netology.
  • Lead with the Netology–EdMarket merger context: he stepped into the Head of Engineering role two years after a significant consolidation under TalentTech — ask how absorbing EdMarket changed the engineering surface area he inherited.
  • Reference his deployment practices and feature flag content on LinkedIn — these are specific operational topics he posts about, which signals they're live concerns, not abstract interests.

Discovery questions

  1. You moved from Team Lead to Head of Engineering at Netology in August 2024 — what shifted in how you spend your week, and what did you have to unlearn from the Team Lead role?
  2. Your DEV Community post argues for automating code-style decisions out of pull requests entirely — how far have you taken that at Netology, and where does the automation still fall short?
  3. You post about AI tools in software development — are you actually shipping AI-assisted workflows on the engineering team at Netology, or is most of that still experimental?

Avoid

Don't treat him as a generic 'engineering manager' who drifted up from individual contributor — he's spent over a decade at one company by choice, and implying that depth is a limitation rather than a deliberate strategy will close the conversation down fast.

Make it yours

Tailor these openers to what you sell

These openers are generic. Sign in and tell Brief what you sell — it rewrites the hooks and questions around your pitch.

Sources

Brief on your next meeting?

Type any name. Get a structured pre-meeting brief in seconds.

Try Brief →

Generated by briefthecall.com from public web sources on August 21, 2026. Each claim is linked to its source above.

Automatically generated by AI from public sources. May be inaccurate or out of date. Remove or correct this profile →