Meet Maksym Bilyansky: Technology Leader at TEBIN
Maksym Bilyansky is a Board Member and Technology Leader at TEBIN. His role connects company strategy with the tools, data practices, and delivery methods used by multidisciplinary design and engineering teams.
The objective is not to introduce technology for its own sake. It is to identify where software can remove repetitive work, make project information easier to review, and give engineers more time for technical decisions. That distinction guides how TEBIN approaches automation and artificial intelligence.
Technology built around engineering work
Design and engineering delivery contains many repeatable tasks: checking model data, preparing structured outputs, comparing information, tracking issues, and coordinating changes between disciplines. Some of these activities can be supported by scripts, dashboards, automated checks, and artificial intelligence systems. Others require context, professional judgement, and clear accountability.
Maksym's work focuses on defining that boundary. A useful tool should support an identifiable engineering task, operate on controlled project information, and produce an output that a responsible person can review. It should not obscure assumptions or imply that technical responsibility has moved from the engineer to the software.
This approach also applies to large language models. They can support knowledge retrieval, text processing, and structured workflows, but their outputs still require verification against project requirements, standards, and source information.
The practical test is whether a tool makes information clearer and decisions more reliable. Time saved is valuable, but not when it comes at the cost of traceability, review, or confidence in the source data.
Agile methods in multidisciplinary delivery
Maksym also contributes software-development practices to TEBIN's operating model. Scrum-based planning, short feedback cycles, and iterative improvement have formed part of the company's transformation since 2019. Applied carefully, these methods help teams make work visible, respond to change, and improve internal tools through feedback from the engineers who use them.
Engineering projects are not software products, so the methods cannot be transferred without adaptation. Formal reviews, design responsibility, information exchanges, and project approvals remain essential. The value of an agile approach is in improving coordination and learning while preserving those controls.
A responsible digital direction
As Technology Leader, Maksym supports collaboration between engineers, Building Information Modeling specialists, developers, and company leadership. The shared aim is to build practical systems that strengthen quality and information management across real projects.
That work supports TEBIN's wider direction: making built assets more digital without separating digital transformation from the engineering decisions that give project information meaning.