Before Vlad Yatsenko built software that could move money around the world, he sometimes wrote programs where no program could run: on paper. Computers were scarce in his adolescence, so the teenager from southern Ukraine rehearsed logic by hand. It is a charming origin story only if one ignores how maddening it must have been. Code is designed to answer back. Paper merely accepts your confidence.
The workaround suited him. Yatsenko's career has been a long exercise in treating constraints as engineering material. He became an administrator in his university's computer lab partly to secure access to the machines and the internet. He graduated with honours in computer science, then chose experience over the obvious route. A better-paid job in Kyiv was available; he went to Poland instead, where the work promised unfamiliar problems.
His route to that classroom had already crossed borders. He was born in East Germany into the family of a Soviet military officer. After the Soviet Union dissolved, the family settled in Yuzhne, now called Pivdenne, near Odesa. In his final school years he attended the town's Ukrainian-language school. He later recalled how Ukrainian could feel almost hidden there: spoken inside homes, then dropped outside for fear of ridicule. The experience sharpened a national identity that would become public only much later, when events gave privacy no useful place to hide.
That decision took him through real-time telecom billing at Comarch and booking engines at Sabre Airline Solutions. Both are useful apprenticeships for a future fintech founder. A billing system must remember everything. A booking engine must act before the seat, room or fare vanishes. Neither is allowed an artistic temperament.
The long route to a simple app
The city he meant to leave
In 2010, Yatsenko moved from Krakow to London. The plan was agreeably temporary: spend a year or two inside investment banking, improve his English, then continue to Sydney. He had also considered a small startup in Frankfurt. London won, partly because UBS offered the chance to see finance from within.
He went on to work at Deutsche Bank and Credit Suisse. The biography is often compressed into “former bank engineer,” which makes the period sound tidier than it was. He was also running a part-time startup aimed at Britain's peculiar technology-recruitment market. It frustrated him. Then a mutual acquaintance connected him with Nik Storonsky, a Credit Suisse colleague who had an idea about foreign exchange.
The irritation was easy to recognize. Britain travelled constantly, yet crossing the Channel meant crossing into another currency, with fees and clumsy travel cards waiting at the border. Storonsky needed a technical partner. Yatsenko had seen the infrastructure, understood the software, and was ready for a better problem.
The point was never to abolish banks. It was to question why their useful services had to feel so inefficient.Yatsenko's recurring argument, distilled
They began at Level39, the fintech community in Canary Wharf, with a few desks and almost no ceremony. Revolut's early proposition was narrow enough to explain over lunch: hold and exchange currencies in an app, then spend from a card without the usual foreign-exchange punishment. Underneath that pleasant sentence sat licensing, ledgers, security, card networks, local payment rails and the stubborn fact that money is most noticeable when it goes missing.
When success arrived as a support ticket
The first beta went to 100 people. For a week, the tiny team could do little except answer them. The users had waited and had opinions. Fixing the product and explaining it became the same job. When Revolut opened to everyone in July 2015, roughly 2,000 new customers arrived on each of the first days. There were four people in the core team and two support interns. Summer travellers wanted their cards immediately, a charming vote of confidence with the operational manners of a fire alarm.
The business plan expected 30,000 users after a year. It got 300,000. Yatsenko later delivered the post-mortem in six economical words: growth created problems, but they survived. The gap between forecast and fact became the central engineering problem. A product built by a handful of people had to become an organization capable of absorbing customers, countries and colleagues at speed.
By 2018, the company had millions of users and hundreds of staff. Yatsenko's days were no longer dominated by writing code. They were dominated by people: hiring engineers, dividing teams, transferring knowledge and trying to prevent a growing company from becoming a museum of incompatible habits. He compared rapid hiring to a child outgrowing a school uniform before the parent has time to buy another. The metaphor is homely; the wardrobe bill was considerable.
He rejected the convenient stereotype that engineers could be brilliant in silence. Technical skill was necessary but insufficient because no single person could anticipate every case. Communication and collaboration were part of the engineering method, not decorations added by human resources. He wanted decisions accompanied by reasons. An instruction without its “why” might produce compliance, but it would not give a team enough context to make the next decision alone.
Nor was he sentimental about process. Rituals were suspect precisely because repetition can survive after purpose has died. One team might borrow from Scrum, another use something else; the governing principle was to deliver value quickly and adapt the method to the people doing the work. This was less a doctrine than an anti-doctrine. At a company expanding as quickly as Revolut, a fixed ceremony could become obsolete before everyone learned its name.
The art of moving difficulty backstage
Revolut expanded far beyond its travel-card beginning. Payments, transfers, savings, trading, credit and business accounts accumulated inside one app. Every market brought its own methods and rules. The product risk was obvious: a financial supermarket could become as exhausting as an actual supermarket on a Saturday.
Yatsenko's answer was to conceal, not deny, the complexity. He wanted payments to feel closer to sending a message. The app should present a feature when it was useful and get out of the way when it was not. This is the quiet bargain of consumer technology. The difficult work does not disappear; engineers volunteer to suffer it on the customer's behalf.
He was equally firm about what the company should own. Critical systems, he argued, belonged in-house. A licensed partner might get a product to market, but every later decision would require negotiation with an institution carrying the regulatory responsibility. For a company with larger ambitions than its partner, dependence would eventually become a speed limit.
“If you don't know, then you are less scared.”On the useful ignorance of starting a company
There is no romance in his explanation of why he chose fintech. The ground was fertile after the financial crisis. Regulation had tightened for incumbents while simpler electronic-money products created openings for newcomers. It was pragmatic, he said. Even his appraisal of billionaire status was dry: he had not dreamed of it, and the public number did not matter to him.
Pragmatism did not mean detachment. When Russia launched its full-scale invasion of Ukraine in 2022, Revolut teams had already been trying to move employees to safety. The company adapted its onboarding for displaced Ukrainians within weeks. Yatsenko, a British-Ukrainian citizen whose father remained in Ukraine, described his response without euphemism. He also backed large charitable campaigns, including a personal contribution and matching pledge worth up to €1.1 million for an Irish children's appeal.
A handoff, engineered
By 2026, Revolut was no longer the hopeful object on two desks in Canary Wharf. It served more than 75 million customers worldwide. Yatsenko had spent over a decade as one of the core architects of the platform, carrying it from a traveller's card to a global financial company. On 1 July, he left the CTO role and became a non-executive director.
His successor, Donato Lucia, was not imported for dramatic effect. Lucia had spent eight years inside Revolut and knew its core architecture. The choice suggested continuity: the technology organization Yatsenko had helped assemble could promote someone who already understood the load-bearing walls.
Yatsenko said he felt content with the decision. The young, ambitious startup had become a mature global company. Founders are routinely celebrated for beginning things; fewer are admired for recognizing when their creation can be run by somebody else. Yet succession is also a systems problem. Authority must move without the service going down.
The teenager writing code on paper could not test whether his programs worked. The director in the boardroom faces a more consequential version of the same uncertainty. He has built the logic, handed over the keyboard and kept a seat close enough to observe the output. Somewhere in that distance between control and trust sits the final achievement of an engineer: a machine that no longer needs him at the console.