THE PROFILE
Alex Vasylyk · StartupSoftTernopil → TorontoThe work after the hire

Founders / Across borders

Alex Vasylyk and the People Who Stay

From Ternopil to Toronto, Alex Vasylyk built a career across borders. At StartupSoft, the enduring question is how to make people on the other side of a screen feel like part of the same company.

Advertisement

A company can hire someone on another continent in considerably less time than it takes to decide whether that person belongs. The contract has a date. Belonging has a slower clock. Alex Vasylyk’s career sits between those two events: the formal beginning of a working relationship and the point when people start treating the work as their own.

Vasylyk is the Toronto-based CEO and co-founder of StartupSoft, a software engineering business with Ukrainian roots. Its proposition sounds straightforward: help companies build remote teams. Yet the interesting part of his story concerns what happens after the introductions. An available engineer and a functioning team are different achievements. Anyone who has attended a meeting containing twelve people and no owner can appreciate the distinction.

A border crossed, a hometown kept

Alex and his brother Andrew moved to Canada in 2004. His public education history places him at York University from 2007 to 2011. By 2012, the brothers had entered entrepreneurship together. The chronology carries two places forward: Canada, where they had moved, and Ternopil, their hometown in western Ukraine.

In 2016, they launched StartupSoft in Ternopil with a team of eight. Greg Yanchak joined the founding group. Alex became chief executive. The arrangement put a North American commercial perspective alongside an engineering base in Ukraine. Geography supplied the shape of the business, while the work of making that arrangement useful still had to be done.

Seen this way, the move to Canada and the launch in Ukraine form one continuing story. Neither place is merely background scenery. One is his publicly listed base; the other supplied the hometown and early team around which the company began. The business makes sense through the connection between them.

His earlier founder listings include WatchRecruit and Safari Juice. Those entries give the career some texture: StartupSoft came after other entrepreneurial activity. It belongs to a sequence of attempts, rather than a biography in which the eventual business arrives fully explained on page one.

A collage of StartupSoft office interiors and people at work
Across the desks: StartupSoft’s office imagery. The meeting invite still has to get the time zone right. Photo: StartupSoft.

The network that could not keep its crowd

In 2017, an abrupt change in Ukraine’s internet landscape created another opening. The country blocked Russian online services, including the social network VKontakte. Alex became a co-founder of Ukrainians.co, a proposed alternative. StartupSoft supplied development for the project.

The early response was quick. A first version appeared on June 3. Within five days, the network announced more than 100,000 registrations. For a new platform, that is an attention-grabbing entrance. It also poses a deceptively difficult question: what, exactly, has a registration proved?

In an account of the venture that summer, Alex described the opportunity as a gap that might close before users moved elsewhere. The network offered familiar design and music sharing. He also acknowledged the established market leader, Facebook. The available opening was real; so was the competitor already standing beside it.

Andrew later recalled that the project reached roughly 400,000 users but struggled with retention and closed. That recollection makes the distinction between arrival and attachment unusually concrete. People could sign up quickly. A reason to return was harder to manufacture. A counter can rise while the underlying habit remains elsewhere.

The episode offers a useful lens for reading Alex’s later work, without pretending to know what private lesson he took from it. Social networks and engineering businesses both depend on continued participation. Their economics differ enormously. Still, an introduction has limited value if the relationship never develops beyond it.

Two different measures
JoiningRegistration · offer accepted · first day
ReturningHabit · responsibility · shared context
A conceptual distinction running through the story. This diagram illustrates an idea; it does not plot measured results.

Five seats at the same table

StartupSoft’s work with Madefire provides a more tangible picture of its engineering model. Madefire made digital comics with movement, sound and interaction. Its Motion Books required software to do part of the storytelling. The pictures had to move properly; enthusiasm alone was unlikely to debug them.

The client engagement began in 2018. Madefire faced a competitive San Francisco hiring market and wanted engineers who would work as part of its central operation. StartupSoft says it assembled five front-end and graphics engineers within six months. The Ukrainian team worked on core elements of the platform.

The company reports a 40 percent saving against local engineering costs. That figure describes one engagement. It should stay attached to the circumstances that produced it. The more revealing detail is the work itself: these engineers contributed to the product customers used, with collaboration across the distance.

It is easy to imagine distance as the main obstacle in an arrangement like this. The case points toward a more precise issue: access to consequential work. An engineer who understands the product and contributes to its central features has a different relationship to the client from someone handed an isolated assignment.

For Alex’s business, that is a practical standard to meet. Recruiting creates the introduction. Integration determines whether the introduction becomes useful. A client can count the people on a roster, but the product eventually exposes how well they understand one another.

5engineers hired
6months to assemble
40%reported cost saving
Madefire engagement · company-reported figures

The family business, without the family script

Much of StartupSoft’s public conversation comes through Andrew, whose interviews describe the ventures he and Alex built together. In a 2020 conversation, Andrew said the brothers were different and complemented each other. He placed trust at the center of choosing a business partner.

It is an unusually plain explanation for an arrangement often romanticized in founder stories. Sharing a surname does not assign responsibilities, resolve a disagreement or tell a customer when something will ship. The relationship still has to function as a working partnership. In StartupSoft’s public team listing, Alex holds the CEO role while Andrew is listed as co-founder.

Their shared personal website is almost comically economical. Two names, social links, StartupSoft and Ukraine in Our Hearts. A visitor can cross it without requiring a contents page. The charity link connects to another collaboration: in 2022, the brothers created a fundraising initiative supporting Ukrainian-made body armor.

Across the commercial and fundraising work, the connection to Ukraine remains visible. The career map has expanded, yet the hometown has stayed in the picture. It is a more specific account of working internationally than the familiar portrait of a founder who could be based anywhere.

Alex Vasylyk standing in a black T-shirt with his hands in his pockets
Alex Vasylyk, between the founder title and the everyday work it entails. A separate portrait published by StartupSoft.

A second look at the people in charge

One revealing public detail concerns the leadership team itself. In a testimonial for consultant Natalia Makedonska, Alex described an outside evaluation of StartupSoft’s leaders. He credited the exercise with a clearer understanding of strengths and weaknesses and a stronger strategy.

“Natalia consulted and evaluated the leadership team at StartupSoft.”

Alex Vasylyk

That statement is modest, and useful for precisely that reason. It describes a specific intervention rather than a general claim to excellent leadership. The people responsible for assessing talent had their own capabilities assessed. For a business whose service depends on working relationships, the symmetry is hard to miss.

His public advice about customer service has a similarly practical cast. In a LinkedIn post, Alex argued that small companies should establish the visible credibility of larger ones, while larger companies should retain the approachable service associated with smaller businesses. The advice connects presentation to conduct: appearing dependable creates an expectation that someone must then fulfill.

Placed beside the leadership assessment, the customer-service advice describes two sides of the same managerial task. Look inward closely enough to see weaknesses. Stay accessible enough for someone outside the company to tell you about them. Neither action supplies a flattering slogan, though both are easier to recognize when absent.

A business can buy a polished website. Remaining available when a customer needs help involves a different expenditure. It costs time and attention. That tension gives his advice some bite as a company grows and there are more people available to pass a question along.

The service question also places a limit on how neatly this can be told as one founder’s story. StartupSoft’s results depend on recruiters, engineers, delivery staff and client teams. Alex’s role sits within those relationships. A CEO’s title identifies responsibility at the top; the daily experience of a customer is assembled by many more people.

The next customer is a model

The business Alex leads now advertises work beyond recruiting and software delivery. StartupSoft offers human-generated coding data and services for refining large language models. The vocabulary has changed, but expert judgment remains part of what the company sells.

In one published engagement with an unnamed AI research client, StartupSoft describes engineers evaluating a coding assistant’s debugging suggestions. They reviewed correctness, clarity and usefulness. The company says the five-month project included more than 250,000 annotated conversations and code-trace evaluations. These are the company’s figures for that engagement.

The work gives the old question of responsibility a new setting. A model produces an answer. A person has to decide whether the answer deserves to be trusted. Software that sounds convincing can still be wrong, which makes experienced review an actual job rather than a ceremonial final glance.

For a profile of Alex, the interesting connection is organizational. His company has spent years arranging for technical people to contribute across distance. Its newer services ask technical people to shape how an automated colleague behaves. The buyer changes, and so does the workflow. The need for people who can judge the work persists.

There is a useful restraint in ending there. A founder can announce a new service in a sentence. Making it dependable takes much longer. Alex Vasylyk’s public career keeps circling that interval: between the promise and the working relationship, between the person who joins and the person who stays.

Follow the working relationships

Explore Alex’s public profiles, the company and the conversations behind this story.