Expertise 08 / Consulting

Focused help for difficult technical decisions

I work with teams that need a new architectural foundation, a clear diagnosis of an existing project, recovery from accumulated coupling, or an experienced second opinion before an expensive decision.

01 / Problems

When outside perspective
creates immediate value

Architecture audit

Trace real game flow, ownership, dependencies, testability, and hot paths; identify risks and the smallest changes that restore control.

Project rescue

Stabilize a team blocked by accumulated coupling, recurring failures, unclear client/server responsibilities, or development paths that have become too slow.

Foundation and handover

Design and implement the essential architecture, establish working patterns and tools, then transfer ownership to the internal team.

Technical decision review

Evaluate networking, backend, content, rendering, performance, or Unity architecture choices before they become costly commitments.

Production workflow

Align engineering, Game Design, QA, documentation, estimation, and delivery so the organization supports fast iteration.

Mentoring

Develop architectural judgment around dependencies, isolation, failure boundaries, data flow, performance, and project-wide consequences.

02 / Method

Change only what
the result requires

  • Start from the product and its constraints. Release horizon, team strength, genre, platforms, content workflow, and business needs shape the recommendation.
  • Inspect actual control flow. Framework names and diagrams matter less than who really owns state and how changes propagate at runtime.
  • Prefer focused boundaries over broad rewrites. Restore control locally and give the team a migration path it can execute while shipping.
  • Leave capability behind. A successful engagement gives the internal team rules, examples, tools, and reasoning—not a permanent dependency on the consultant.
  • Stay available when useful. Some projects need a one-time review; others benefit from periodic collaboration as new decisions appear.

03 / Experience

Consulting in practice

8D Studio / Sketch Tales

Two-month architecture setup and handover

Joined for a predefined engagement to design and implement the core Unity architecture and the part-based character renderer central to the product. Transferred ownership to the internal team as planned and continued advising through much of later production.

Alfa Bravo / Recurring collaboration

Architecture, technical art, packages, and backend choice

Continued periodic collaboration after employment. Work has included architecture and technical-art guidance, selecting Unity ContentDirectory over extending Flexy.Bundles for a simpler workflow, adapting Flexy.AssetRefs, and recommending Orleans for Azure scaling without a separate backend department.

Short VR outsourcing engagement

Estimate, structure, and deliver

Over roughly two months, several hours one day per week, helped an outsourcing team evaluate incoming VR work and shape architectures for fast, reliable delivery. Guidance covered VR camera movement and input, performance-safe approaches, and simple game structures appropriate for deadline-driven client projects.

Educational-game platform

Modular mobile hub consultation

Provided several consultations to a company planning a mobile hub into which new educational games could be integrated and launched. The work focused on technical structure and viable implementation approaches.

Ciklum / Unity team

Half-day architecture and process review

Spent a focused half day with Ciklum's Unity team helping establish practical process and architecture decisions.

Long-term technical mentoring

From dependencies to CTO-level ownership

Early recurring mentoring focused on dependencies, isolation, and preventing one part of a game from breaking another. The programmer later became CTO of his own game company, uses the architecture in his games, and the collaboration still continues periodically.

04 / Lead experience

Consulting skills developed
inside production teams

Architecture reviews were a regular responsibility across lead and CTO roles even when the work was not called consulting. I reviewed global game flow, system boundaries, client/server responsibilities, performance structure, technical art, reusable packages, and production workflow while sharing responsibility for delivery.

At Wargaming, the first major task as client-team lead was to recover a blocked architecture; the role then expanded across client/server flow, gameplay, rendering, and production. This kind of hands-on responsibility is the foundation for external project-rescue and audit work.

05 / Formats

Engagements sized to the problem