Epicentr K — Case Study

Context & Problem

No mobile capability

When I joined, Epicentr K had no mobile department, no mobile architecture, and no delivery process. Ukraine's largest retail chain — operating ~75 hypermarkets — needed a mobile presence but had no internal engineering capacity to build or own it.

Build, not just ship

The problem wasn't just writing an app. It was standing up an entire function: defining architecture, establishing coding standards, hiring engineers, wiring a delivery pipeline, and shipping production software — all at the same time.

What I Did

🏗️

Launched the department

Created the in-house mobile apps department from scratch — defined its charter, scope, and operating model. Took it from a zero-headcount idea to a functioning team producing and owning production software.

📐

Set architecture & standards

Designed the mobile architecture for Xamarin cross-platform development. Wrote the coding standards and review guidelines that gave the team a shared baseline and kept the codebase consistent as it grew.

🚂

Built CI/CD & release trains

Put a continuous integration and delivery pipeline in place. Established release train cadences so that shipping didn't depend on heroics — builds were automated, tested, and deployable on a predictable schedule.

🤝

Hired & mentored the team

Recruited mobile engineers and ran technical interviews. Mentored hires through onboarding and into independent contributors — making sure they understood both the standards and the reasoning behind them.

📱

Shipped internal apps

Delivered multiple production internal apps on the Xamarin stack. Kept the architecture decisions grounded by dogfooding them — every standard written was also a standard lived while building real software.

Impact

hypermarkets served

0 → 1 department built

Multiple internal apps shipped

Built ground-up at Epicentr K, Ukraine's largest retailer

Highlights

🏛️
Org-building
Created the mobile department and its charter from nothing. Defined how the team would operate, what it owned, and how it interfaced with the rest of the engineering organization — before a single line of code was written.
Leadership

📏
Standards
Authored the mobile architecture and coding guidelines. A new team with no prior mobile history needed a shared foundation fast — the standards gave every engineer the same reference point and made code review a teaching tool rather than a gatekeeping exercise.
Architecture

⚙️
CI/CD Pipeline
Stood up continuous integration and delivery from scratch. Release trains gave the team a predictable, low-drama shipping rhythm — builds automated, environments stable, deployments repeatable. Shipping stopped being a manual event.
Delivery

🌱
Mentorship
Hired engineers and grew them into independent contributors. Onboarding into a brand-new department with fresh standards and a nascent codebase required active mentorship — pairing on code, reviewing work in depth, and making sure the standards were understood, not just enforced.
Growth

Technical Highlights

Xamarin — cross-platform

Shared C#/.NET codebase across iOS and Android. Xamarin let a small team move at pace without maintaining two divergent native codebases — business logic written once, platform-specific UI handled at the edges via Xamarin.Forms and custom renderers.

CI/CD & release trains

Automated build, test, and distribution pipeline for both platforms. Release trains provided a structured cadence — feature branches merged on a schedule, builds promoted through environments, and releases went out without manual coordination overhead.