Andrew Filev and the trouble with getting things done

Five people in a room are reasonably easy to coordinate. Someone asks a question; someone answers it. Then the company succeeds. Offices appear in other countries. Projects multiply. The founder discovers that an expanding portion of his job involves asking what everyone else is doing. Andrew Filev’s first software business reached more than 100 engineers. His reward was an increasingly intimate relationship with emails, spreadsheets and meetings.

Wrike began in that gap between having capable people and knowing how their work fitted together. Filev wanted a business to remain understandable as it grew. He had experienced the smaller version, where information could travel across a room. He wanted software that would help it travel across an ocean without requiring him to conduct the journey personally.

The idea would become a company acquired by Citrix for approximately $2.25 billion in 2021. But start with the room. It explains more about Filev than the price does. He tends to notice the machinery around productive work: the searching, the checking, the handoffs, the information someone needs before they can begin. His career has been spent trying to give those hours back.

The company that outgrew the room

A consulting business teaches a young engineer something that a programming exercise rarely does. Working code must arrive alongside a promise kept to another person. Filev started his first software company in his late teens. It grew across countries and involved more than 20 projects. The challenge became keeping a collection of moving commitments visible.

He understood the attraction of a tool that could serve people outside software engineering. Developers already had their own systems. Other teams needed a way to plan and collaborate without adopting an engineer’s habits. Wrike’s ambition was to make shared work accessible to the people actually responsible for it, including those whose job descriptions did not contain the word “technical.”

There is a pleasingly circular quality to the origin. The company’s growth supplied both the problem and the education needed to tackle it. Filev had already watched useful processes become awkward at a different scale. That gave him a concrete test for his next product: would a team spend less time assembling an account of its work?

A textbook, a staircase, a duffel bag

Filev was born in St. Petersburg. His childhood included computers, science competitions, books and chess with his grandfather. He recalls reading a whole chemistry textbook over one weekend. The attraction was partly the material and partly the absence of much competing entertainment. A textbook had the considerable advantage of already being there.

At a school focused on mathematics and physics, a board on the staircase displayed the names of pupils who had won international competitions. He remembered looking at it every day. His own beginning was less decorative: an early grade translated to an American F. He later became a strong student. The memory stayed with him as an argument for judging progress, rather than a starting position.

He credits his mother with giving him independence as well as support. She worked while completing her own degree. He chose his school and made a long daily commute. Good results earned him room to organize his time. His later description of management follows a similar bargain: give people freedom when things are working, and offer practical help when they need it.

Silicon Valley had interested him since his teenage years, partly through science-magazine articles about a Russian immigrant’s experience there. He delayed moving while his first company was young. Around 2006, he arrived with a laptop and a duffel bag. The journey had been imagined for years; the luggage was comparatively uncomplicated.

“I’m not the kind of guy who drops things midway.”Andrew Filev, on delaying his move while building his first company

He had studied computer science at Saint Petersburg State University, earning a master’s degree. His education also included the Stockholm School of Economics. Engineering and business would remain closely joined in his work: an idea needed to function, but it also needed to find people willing to use it.

Customers before the cheque

Wrike was founded in 2006 and launched publicly in 2007. An early prototype appeared at a conference in Paris. The subsequent launch put Filev in Silicon Valley, a place he had wanted to join but where his previous business did not automatically make him a familiar figure.

The early years required a founder to perform several jobs. Product development, support and finding customers all competed for his time. He remembers a Canadian company dealing in physical storage as Wrike’s first customer. Containers, rather than computer files: a small reminder that software designed by an engineer can solve problems in places the engineer has never worked.

By a 2014 interview, Wrike had more than 6,000 paying customers across over 50 countries. That variety mattered. A work management product had to be useful to businesses with different routines and different kinds of output. Its customers could not all be expected to think like the people who built it.

Customer revenue supported the business for years before the 2013 Series A led by Bain Capital Ventures. An earlier, smaller investment came from TMT in 2012. The distinction matters to the chronology: Filev built a paying audience before the larger institutional round, rather than beginning with a large venture-funded organization.

He also took Wrike to small regional project management gatherings. His recollection includes flying to Texas to speak to a room of around 30 people. The scale sounds almost quaint beside a billion-dollar transaction. Yet it is an appropriate scale for finding out whether someone understands what you are selling. Thirty project managers can ask thirty very practical questions.

During the 2008 downturn, he responded to slower customer acquisition by spending more on advertising. Then he watched Rogue Trader, with Ewan McGregor playing a trader trying to spend his way out of trouble. Filev recognized an uncomfortable resemblance. He cut back and concentrated on efficiency, recalling that the same results soon cost half as much. A film about a bank’s collapse had supplied a useful lesson for a small software company. The ticket price was presumably kinder than the advertising bill.

Authority has to show its working

Filev’s management philosophy reflects the experience of running a company before age alone could lend him authority. He had to earn respect by contributing. He has described wanting decisions explained on their merits, whoever proposes them. A title may get someone into the meeting; the reasoning still has to survive it.

That principle suits a founder whose product promises to make work visible. If the point is to give people enough information to act, a manager who keeps every decision to himself becomes an expensive obstruction. Filev’s preference for helping when needed, then stepping back, asks something difficult of a capable engineer: resist the temptation to fix everything personally.

His hiring questions include asking what a candidate most recently learned at work. It is a small question with a useful reach. A polished account of an old success can be rehearsed. Recent learning requires someone to describe how their understanding changed. The textbook has, in a sense, become an interview question.

The public picture also has room for activities that do not require a spreadsheet. Speaking to a San Jose audience, he described tinkering with robots, competing in Brazilian jiu-jitsu and following the Sharks and Barracuda hockey teams. He spoke about his two boys, too. These details make the engineer recognizable beyond the organizational chart.

He has invested in other founders, including becoming a seed investor in Miro. That connection belongs naturally beside Wrike: both businesses concern how people work together. His writing has addressed project management and software development, giving the practical interests behind his companies a life beyond the products.

The sale, and the unfinished ideas

Citrix announced completion of its Wrike acquisition on March 1, 2021. Filev continued leading the business within Citrix as a senior vice president and Wrike general manager. In July 2023, another ownership transition brought Wrike under Symphony Technology Group. Filev moved to Board Advisor; chief financial officer Thomas Scott became interim CEO.

The next company returned him to an earlier interest. For his university thesis, he recalls building a tool that automated refactoring in C#. Long before today’s coding agents, he had been interested in software that could help an engineer change software. Wrike occupied his attention for years, but the attraction remained.

He also carried a founder’s backlog. Even with a substantial engineering organization, he had more product ideas than the team could implement. Some never appeared; others took years. A large company can afford many engineers and still ration its capacity to build. For someone who enjoys making things, success brings a rather sophisticated waiting list.

Zencoder was founded in 2023 and publicly launched its AI coding products in October 2024. Its tools were designed to fit into developers’ existing editors and support tasks including code generation, repair and testing. Filev’s university experiment had acquired a much larger context: software capable of assisting through several steps of a development task.

The inbox returns, with agents

In April 2026, Filev introduced Zenflow Work, extending Zencoder’s orchestration platform toward planning, reporting and coordination. The examples included preparing standup summaries and compiling release notes. His explanation returned to a familiar observation: a tool can be powerful and still be awkward for people outside the group it was originally designed to serve.

He wants agent workflows to become accessible beyond engineering. That means simplifying interfaces and giving recurring work a structure people can trust. The aspiration sits comfortably beside Wrike’s original purpose. The technologies differ, but an employee waiting for information still has the same question: can I get on with the job?

Filev’s career keeps coming back to that interruption. First he tried to help people see and coordinate their work. Now he is trying to help them carry more of it through. The most revealing measure of the next chapter may be a person reaching the end of a working day with something finished, and a little less time spent asking where it went.