Skip to content
01CareersNot currently hiring

Senior engineers
building serious
software, from Kyiv.

We're a small studio, not a body shop. The people on the project are the people who ship it, operate it, and stay with it. We don't staff-augment, we don't outsource, and we don't fill seats. If you've shipped serious software and want to build more with European founders — read on.

12People in the studio
7Live engagements · 2026
100%Same team · ships and operates
EN·UKWorking languages
02What we look forThree things · in this order

Three things, in order of weight. We do not have a fourth.

If you can show us these three things in writing, in code, or in conversation, we can almost always find a role for you. Everything else — frameworks, languages, current employer — is detail.

01

You've shipped.

Production code in real products with real users. We'd rather hear about something you put in users' hands and lived with for a year than a side project that never met the world. The bug you fixed in production at 2am counts more than the talk you gave at a conference.

02

You think before you type.

Design and architecture matter to you. The reason we still write 10-page docs before we start a sprint is the same reason you do, or want to — it's cheaper than the alternative. Show us a system you sketched out before you wrote it, and what it changed.

03

You speak directly.

Clear writing and direct disagreement, professionally. We argue in PRs and write it down. If your last team called you "intense in code review" and meant it as a compliment, we probably want to talk to you. If you can't say "I disagree" out loud, this isn't the studio.

03Open rolesNot hiring right now · updated weekly

No open seats.

Updated 12 MAY 2026NDA on request
No open roles right now. Send a portfolio anyway — we read every email.
04How we workFrom your seat · the short version

The work-week you'll actually have.

A short version of the four steps every engagement runs through — from the seat of the engineer who's on the pod, not the client paying for it. The long version is on the Approach page →.

01DISCOVER · WK 1

Think.

Spend the first week of a new project thinking, drawing, and writing — before code. You'll co-author the architecture document. That document is the contract for everything that follows.

02DESIGN · WK 2 — 3

Review.

Design with the engineers who'll build it. Review with the client every Friday. Never a big reveal. If a screen surprises the client in week three, we did it wrong.

03BUILD · ONGOING

Ship.

Production from sprint two. Friday demos to the client, no exceptions. You'll push back when something won't work, propose what will, and write it down in an ADR. That's the job.

04OPERATE · ONGOING

Stay.

You stay on the project. Same on-call rotation, same Slack channel, same roadmap. If the client wants to hire you off us when the engagement matures, that's an option we wrote into the contract on purpose.

05Don't see a fit?

Send a portfolio anyway.

If the open roles don't match but the studio sounds right, write to us. Send a portfolio, a short note about what you'd want to work on, and one piece of writing you're proud of. We read every one.

Reply within 5 business days · in EN, UK, or DE