What we have taken to production.

4M rps of telemetry and terabytes of traffic a week on own hardware. Apps live in the App Store and Google Play. The service went from 1,600 to 5,000+ clients in a year (Hyundai’s public figures).

Production stable within two weeks. 0 seconds of downtime at the 10× New Year peak. A new meal-plan engine in four months. 6M+ customers.

Commit to release in 1⁠–⁠6 minutes instead of hours. Selected for the state programme on the first attempt, ranked first. Two new products for the season and an in-house launch pipeline. The team works with agents on its own: most of it at step 3 of the adoption scale.

1.4% of false-negative reports sent back for review thanks to the algorithm. A pilot in a working hospital: the tool runs inside the HIS, the clinician sees the result where they already work.

A new backend in three months, with releases shipping throughout. Production and peak marketing periods — no incidents. The project handed to a compact team assembled for it.

One codebase in production after 3.5 months. Several stable releases in a row — then handover to the in-house team.

The visual and UX logic of the car’s key interfaces is in place. The AR HUD and the yoke with a touch display are part of an HMI concept with no equivalent on the mass market. Design, engineering and production worked as one chain.

A mobile-app concept: “New In” as the first touch with a collection, product cards with video instead of photos, stylists’ trend picks as stories. Motion as the shared language of the cover, the card and the season campaign. Shipped in three weeks.

The console on the new version in 20 weeks. The new product line launched in 12 weeks — the core stayed with the core team.

Production, service points and logistics run as one loop. Routes and load are planned by forecast, not after the fact. The platform handed over to the in-house support team.