Ten years ago, mobile development was still a bet — a fast-moving, unproven corner of software engineering that most established programmers viewed with skepticism. Today, the applications architected by Siarhei Krupenich are used daily by millions of customers of major banks and global retailers. A Senior Mobile Software Engineer currently based in Warsaw, Poland, Siarhei Krupenich has spent nine years building for fintech, retail, Web3, and IoT, leading teams, conducting technical audits for financial institutions, and mentoring the next generation of developers. We sat down with him to talk about the decisions that shaped his career, the technical challenges behind some of his highest-impact projects, and where he believes the role of the software architect is headed.
A Side Bet on a New Framework
Siarhei Krupenich’s path into mobile began almost by accident, at the intersection of two technologies he was juggling as a student.
“My path into mobile development began at the intersection of two technologies. At university I was studying Java Web, while freelancing on the side as a .NET developer. That was exactly when the mobile industry was booming — smartphones were turning from toys into full business tools. I could clearly see that trend and understood the future belonged to mobile.”
Around the same time, the Xamarin framework emerged, allowing developers to build cross-platform mobile apps using the .NET stack he already knew. Rather than wait for the technology to mature, he began building his own side projects to learn the fundamentals of mobile architecture while it was still new ground.
“As soon as I added Xamarin to my resume, a company looking for developers in that space noticed me almost immediately. That offer let me move from university straight into the commercial sector.”
He is candid that he wasn’t thinking about scale at the time. But that early decision — to bet on an emerging niche and build real projects just to gain experience — laid the foundation for the architecture patterns he continues to refine today, now used by millions of customers across major banks and retail chains.
Why Fintech, Retail, Crypto and IoT All Still Interest Him
Siarhei Krupenich’s portfolio spans strikingly different industries: financial services, cosmetics retail, cryptocurrency wallets, and even smart speakers. Asked what keeps him engaged across such varied domains, he points to the direct impact mobile technology has on everyday life.
“What keeps me here is the incredible feeling of influence on real life. A smartphone is something that’s always in our pocket. We’re essentially wrapping the most complex business processes into a convenient digital shell the size of a small device. A few taps and swipes on a six-inch glass rectangle connect a person to the whole world — access to knowledge, shopping, managing finances, earning money. Knowing that your decisions make someone’s life easier right here, right now, is a huge motivator.”
He notes that while the business logic differs sharply between fintech, retail, crypto, or IoT devices, user experience follows the same underlying principles everywhere. Staying relevant, he says, means anticipating where an industry is heading rather than simply reacting to current trends.
Rebuilding a Bank’s App Without Slowing It Down
Among the more sensitive projects in Siarhei Krupenich’s career is his work on the flagship mobile app for a leading Georgian bank and the design system he built for Space Neobank. Financial applications leave little room for error, and legacy code had accumulated over years of rapid iteration.
“Working with fintech is always a huge responsibility, because the cost of any mistake is measured in the trust of millions of users. The main challenge was that the product had grown quickly, and over time it had accumulated a fair amount of legacy code with tangled dependencies. Some suboptimal architectural decisions had lingered for years, slowing the app down.”
His team approached the problem from two directions: a targeted rewrite of the heaviest, most tangled sections of code, and the creation of a shared design system — a library of tested, reusable UI components other teams could simply plug into their own screens instead of rebuilding buttons, forms, and lists from scratch each time.
“That targeted, almost surgical intervention is what let us raise interface performance by that 15% — the app became noticeably faster and more responsive. The shared design system radically changed the rules of the game: developers no longer had to re-implement the same components over and over. Time-to-market for new features went up, and interface maintenance costs dropped by a third, because maintaining one shared component is far cheaper than maintaining a dozen scattered copies of it.”
Augmented Reality as a Cost-Saving Tool, Not Just a Gimmick
For global cosmetics retailer ELF Cosmetics, Siarhei Krupenich’s team went beyond a standard e-commerce build, integrating augmented reality for virtual try-on alongside analytics platforms AppsFlyer and Braze. He describes the AR feature not as a flashy add-on, but as a direct answer to one of retail’s most expensive problems: returns.
“AR try-on isn’t just a nice engagement feature — it’s a powerful cost-optimization tool. A customer can try on lipstick or eyeshadow right through their smartphone camera, instantly removing the uncertainty of ‘will this shade suit me?’ As a result, order confirmation rates rise, and the return rate — along with the associated logistics costs — drops sharply. That’s pure budget savings.”
He explains that the try-on feature only delivers value when paired with deep behavioral analytics: understanding exactly where in the funnel users hesitate or drop off, testing hypotheses through A/B experiments, and using retention platforms to deliver personalized, well-timed messages that bring shoppers back to complete a purchase.
“The synergy of AR technology and smart analytics turns an app from a simple storefront into a self-learning system. We’re not guessing what the customer wants — we know it from the data, and we improve conversion metrics and business results in a targeted way.”
A 14% Performance Gain, Delivered Without a Single Outage
Siarhei Krupenich has also conducted architecture audits for financial institutions, including for a major Azerbaijani bank — engagements that companies typically reserve for their most sensitive systems. He describes what such an audit actually involves.
“An architecture audit of a large fintech product is a comprehensive review against strict quality criteria. We analyze architectural patterns, data security, error-handling scenarios, test coverage, maintainability, and of course performance. Our audit showed the application had originally been designed to a good standard — but even in the most mature systems, blind spots and hidden bottlenecks accumulate over time.”
Rather than a single breakthrough fix, the 14% performance improvement came from identifying and resolving a cluster of small but critical inefficiencies — from redundant database calls on the client side to suboptimal rendering of heavy UI elements — and rolling out the changes gradually, so the live banking system never had to stop.
“We eliminated these micro-problems methodically, ‘under anesthesia’ — rolling out optimizations invisibly to the end user through staged releases, measuring the effect of each change with profilers and monitoring against real traffic. In the end, the synergy of dozens of small improvements gave us a real 14% gain in interface response speed, while keeping banking operations completely stable.”
Leading Without Micromanaging
Beyond architecture, Siarhei Krupenich has led a team of seven engineers, conducted more than 300 technical interviews, and mentored over 20 junior developers. His management philosophy draws on Management 3.0 principles and a deliberate rejection of top-down control.
“My main secret is that I don’t ‘raise’ anyone. I’m deeply convinced that micromanagement and directive leadership are long dead. You can’t force someone to become a great engineer — a person needs strong internal motivation to grow on their own. My job as a leader isn’t to hand out instructions, but to build the right ecosystem: choose people who genuinely care about our problems, set up processes that run smoothly on their own, and gently guide the team.”
He is equally direct about the harder calls a leader has to make — including when to part ways with a technically strong engineer who doesn’t fit the team’s culture.
“One toxic developer can destroy a team’s microclimate and demotivate the other six. So for the health of the whole team, you need to be able to make that difficult choice quickly and professionally.”
Mentorship, Talks, and Building a Public Track Record
Siarhei Krupenich’s YouTube talks on Flutter and Android TV development have drawn tens and even hundreds of thousands of views, and he serves as a judge for the international Technovation Girls competition, supporting young women entering software development. He sees public engagement as inseparable from technical growth rather than a side activity.
“Sharing knowledge isn’t charity for me — it’s an integral part of professional growth. When you speak publicly or write an article, you have to rethink your own experience, structure it, and translate it from complex engineering language into something a normal person can understand. Tricky questions from an audience or in the comments often force you to look at familiar architectural decisions from a completely unexpected angle.”
He also points to the value of visibility for young women in tech, an industry where gender bias still shapes early-career motivation, and is candid that a public track record — talks, articles, community involvement — has become an important differentiator in his own career.
Where AI Fits — and Where It Doesn’t
Siarhei Krupenich has integrated AI tools into his own development workflow, but he pushes back on the idea that traditional engineering is becoming obsolete.
“AI has freed us from routine — endless searching on Stack Overflow, digging through hundreds of pages of documentation. But it won’t replace the engineer, for one fundamental reason: generative AI is built on a probabilistic model. AI works with data and statistical likelihood, while building mission-critical systems requires absolute precision and determinism. Where the cost of a mistake is high, a ‘probable’ answer isn’t good enough.”
Looking five years ahead, he expects the architect’s role to shift from writing code toward strategic system design, favoring engineers with strong fundamentals in computer science and deep domain knowledge over those chasing the framework of the moment.
“The architect of the future is a conductor who uses AI tools to automate the routine work, but who still makes the key decisions on architecture, security, and integration. Fields with ultra-sensitive data and an extremely high cost of error — fintech, healthcare — will keep AI tightly limited for a long time to come. And there, human expertise will remain irreplaceable.”
Working Across Belarus, New York, Europe, and Beyond
Having worked in Belarus, collaborated with a New York office, and built products for European and Asian markets, Siarhei Krupenich has a firsthand view of how digital product development actually differs — or doesn’t — across regions.
“Technically speaking, technology really has erased borders. Wherever you are in the world, you’ll find similar processes — Agile methodologies, the same bug trackers, version control systems, architectural patterns. The code is written in the same language everywhere. The difference isn’t in the technology, it’s in the business models and corporate cultures.”
He describes European teams as more focused on work-life balance and preventing burnout, American and Eastern European cultures as more result- and speed-driven, and Asian management styles as marked by high discipline — though not always translating into proportional gains in productivity or creativity. The ideal product, he argues, emerges where speed and discipline meet a healthy approach to the team’s wellbeing.
The Project That Taught Him What Actually Matters
Asked to reflect on a moment when a project nearly fell apart, Siarhei Krupenich recalls a large advertising project at a European company with strong technical talent but a toxic internal culture.
“The team was technically incredibly strong. But there was a complete absence of a healthy culture or normal communication, and management practiced hard pressure on employees. On top of that came chaotic processes, no onboarding, and constantly shifting business requirements. After about a month in that atmosphere, I made the difficult decision to leave the project to protect my mental health and preserve a healthy working environment. A year later, I learned the whole team had fallen apart and the project was never finished.”
The experience, he says, became one of his most important professional lessons: no amount of technical expertise guarantees a project’s success if the team’s culture is broken.
“If people don’t work well together, the project is doomed in the long run. And the reverse is also true: a tight-knit team will always back each other up, work through technical difficulties together, and pull a project out of any crisis. What matters most in IT is people — their values, and the chemistry within the team.”
Asked what advice he would give his 20-year-old self, his answer has nothing to do with technology stacks.
“Invest in soft skills, and learn to understand people as deeply as you understand code. Technologies change every year, frameworks become obsolete — but the ability to build trust, listen to your colleagues, and create a safe, supportive atmosphere around you is what will make you a truly strong leader and architect, in any era.”
