Cases

A few cases from the work.

A team that scaled in a hurry. A partnership that has lasted years. A custom platform built from scratch. Different shapes of work, in case one of them is close to yours. We do not name every client, but the numbers and the shape of the work are real.

European e-commerce

Adding fifteen engineers to a thirty-five-person team in twelve weeks, before Black Friday.

Stack .NET, React, Azure, QA Automation, Performance Engineering Engagement Embedded into nine parallel roles under a multi-team client structure.

The client had a working platform and a thirty-five-person team. The product roadmap for the season called for catalogue expansion, payment and tax provider integrations, and front-end performance work, all before peak load. They needed fifteen more engineers, fast, across nine different roles, with live interviews only and no take-home tasks.

We ran hiring as a product. Standardised scorecards, competency matrices for QA, Back-End, Full-Stack, and Performance. Feedback within two to seventy-two hours. A weekly business review to catch bottlenecks. Pipelines for each role ran in parallel, with candidates rerouted between roles when their level matched a neighbouring opening better than the original one.

13 starts

within twelve weeks, against a target of fifteen

~92%

ninety-day retention of the new hires

5 days

median ramp-up to first pull request

Automotive · Volkswagen

A long-running engineering partnership inside a global manufacturer.

Engagement Dedicated team, embedded into internal product groups, multi-year. Why it works People do not rotate off the account when a quarter ends.

Large industrial clients do not need vendors that show up for a six-month sprint and disappear. They need people who learn the internal systems, the political map, the codebase, the unwritten rules, and stay long enough for that knowledge to compound. That is what this engagement has been: a small, stable group inside a much larger organisation, doing work that gets harder, not easier, the longer you are on it.

The client testimonial sums it up: "Polytech is a high quality outsourcing service provider with strong management. We hope to continue our collaboration in the future."

Salesforce ecosystem

A Salesforce practice with its own product, its own training, and its own engineers.

Shape Direct configuration for corporate clients, plus delivery work for agencies in the Salesforce ecosystem. Product The Welkin Suite, a development environment for Salesforce engineers, built by Polytech. Position One of the first Ukrainian Salesforce partners.

Most companies in the Salesforce ecosystem deliver implementation projects. We did that too, and then we built our own product on top: an IDE for Salesforce development, used by engineers and teams around the world. We are not just configuring the platform for you. We have written the tools that sit inside it.

The bench behind the work matters too. Every engineer here is trained internally, certified, and ready to ship. The training is built around Salesforce certifications, with practice and depth, and our engineers pass them cleanly.

For Salesforce service providers, that means a partner who understands what their end customers will hit on the third release, not just the first. For enterprise teams running their own org, it means engineers who know where the platform bends and where it breaks.

Mortgage technology · Acuity

A small embedded team, working as part of the product organisation.

Engagement Dedicated engineering and QA, integrated into the client's product organisation.

The client described the working pattern as "strong, dedicated team players providing engineering and QA services for several years." That is what we look for in long engagements: the line between vendor and client disappears, decisions are made together, and the work compounds.

If you cannot find your situation here

Two of our best long-running projects came from sectors we had never touched until the founder explained the problem on a call.

Start that call