the crew

six people. no office. no titles that matter.

vøiddo is a small crew working remote from a handful of cities across Israel and Estonia. Nobody commutes. Nobody shares a postcode with a colleague. The studio keeps a mailing address in Estonia and no office; the work happens wherever each person actually opens a laptop in the morning.

There is a founder who still writes production code, a backend lead who treats Postgres like a personal grievance, a frontend lead who has rewritten the design system four times this year, an infra lead who would rather hand-roll bash than touch a vendor dashboard, a design lead who paints the wordmark by hand before digitising it, and a QA lead whose job description is "break it before it ships." Six people and a lot of automation. There is no marketing team, no growth team, no head of people.

egor michurin portrait
egor michurin
founder // ceo · israel
em@voiddo.com

Writes the code, pays the server bills, replies to support email at 2am.

Egor started vøiddo as a place to put the tools he kept writing for himself, and he still writes production code. He owns the deploy pipeline, the server, the mail rails and the watchdogs that wake him when something is on fire, plus most of the things nobody else wants to debug late at night. Writes Python and TypeScript in roughly equal measure, sleeps less than a doctor would recommend. Owns the studio because nobody else wanted to.

Once shipped a critical hotfix at 2am from the bathroom of a wedding reception in Caesarea. The bug was a stale cache; the fix was a one-line invalidation; the laptop had three percent battery. Nobody at the wedding noticed he was gone for nine minutes.

"Just deploy it and see what breaks."

PythonTypeScriptbashnginx
dmitri orlov portrait
dmitri orlov
backend // data · tallinn, estonia
do@voiddo.com

Makes the database queries run faster; calls your ORM a war crime in writing.

Dmitri spent ten years tuning Postgres for payment and commerce systems, the kind of job where a forty-millisecond regression on a hot query is a conference call and a thousand-millisecond one is a resignation. He moved to Estonia in 2023 for the residency programme and the weather, in that order. At vøiddo he owns the data layer: the schemas, the queries and the ledgers that record what every run and every trade did. Believes most performance problems are bad indexes, most bad indexes are bad ORMs, and most bad ORMs are written by people who never opened an EXPLAIN ANALYZE window.

Once spent four hours optimising a query that runs twice a year and saved the studio $0.83 in monthly compute. He framed the metering receipt and pinned it above his desk as a reminder that some optimisations are about principle, not money.

"Your ORM is hiding a terrible query."

PostgreSQLPythonSQLbash
ido ferenczi portrait
ido ferenczi
frontend // ui · tel aviv, israel
if@voiddo.com

Makes the buttons actually work; rewrites the spacing scale when nobody asked.

Ido grew up in a Hungarian-speaking household in Jerusalem, did a year in military intelligence learning that nothing is ever as urgent as someone tells you it is, then spent two years at a small design agency in Budapest before Tel Aviv pulled him back in 2022. At vøiddo he owns everything you see in a browser: this site, the blog and the code blocks in it. Mild opinions about accessibility (we follow them anyway), strong opinions about bundle size, nuclear opinions about CSS-in-JS. Rewrites the design system whenever the spacing scale starts to bother him.

Once redesigned an entire settings page in Budapest airport while waiting on a delayed connection. The redesign shipped from terminal 2 on hotel-tier wifi, and the connection never did. Nobody filed a bug.

"We do not need another JavaScript framework."

TypeScriptcsshtmlfigma
tal sheleg portrait
tal sheleg
infrastructure // ops · tel aviv, israel
ts@voiddo.com

Keeps the lights on; treats vendor dashboards like a personal insult.

Tal grew up in Tel Aviv and cut his teeth on security infrastructure for a mid-size fintech that slowly became the kind of place where compliance memos replaced engineering decisions. At vøiddo he runs everything we deploy: the nginx configs, the systemd units, the monitoring and the watchdogs that keep the services coherent on one rented server. Trusts bash scripts more than vendor dashboards because bash scripts have never silently changed pricing on him, and has never met a YAML file he could not shorten.

Once fell asleep on the last train from Tel Aviv and woke up at the Be'er Sheva central station at four in the morning with no way back and a phone on three percent. Spent the night on a bench arguing with a stray cat about whose station it was. Refuses to discuss the outcome.

"It works on my machine is not a deployment strategy."

nginxlinuxbashsystemd
roman brodsky portrait
roman brodsky
design // brand · tartu, estonia
rb@voiddo.com

Maintains the visual language; will lose an afternoon to one comma in the wordmark.

Roman studied industrial design in Saint Petersburg in a programme that still made students cut foamcore by hand, spent eight years in agency rooms in Moscow and then Warsaw making the same bold deck for a different bank every quarter, then moved to Tartu in 2022 because the quieter rhythm made the work sharper. At vøiddo he owns the visual identity end to end: the wordmark, the sigil, the typography, the stylised portraits on this page (yes, those are illustrations, and there is no real photo of any of us here on purpose) and the editorial system that keeps every public surface looking like it came from the same studio. Still paints on real paper before he digitises anything.

Once kerned a single word in the wordmark four times in one afternoon. Only the third version shipped; the other three he printed at home, framed at A5 and hung in the hallway as a reminder that almost right is not right.

"Make it darker."

figmaillustratortypographybranding
lev vaintroub portrait
lev vaintroub
ops // qa · haifa, israel
lv@voiddo.com

Breaks things intentionally; will file a bug against the bug tracker.

Lev moved from Saint Petersburg to Haifa as a teenager, studied applied mathematics at the Technion because his mother thought applied sounded employable, and ended up in quality engineering almost by accident: a friend asked him to look at a flaky test suite over a weekend, the suite stopped flaking, and the company offered him a job on Monday. At vøiddo he writes the tests that run against every change, designs the fuzzers that feed malformed input and weird Unicode into our parsers, and maintains the fixtures that let the rest of the team ship late at night without breaking things. Keeps a running list of the worst bugs he has ever shipped, and reads it before every release.

Once filed a bug report against the bug tracker itself. The report broke the tracker. The workaround was a shared Google Doc, and the Google Doc is still where some teams report bugs. He is unrepentant.

"I found another unhandled exception."

pytestplaywrightpythonci
how we coordinate

a remote crew, in practice

There is no office, and there has never been one. We coordinate over a few chat channels, one weekly call that nobody has to attend if they have nothing to say, and the merge log, which is the real standup. When something needs a real conversation, two people get on a call; when something needs a real argument, it is written down first, so the call stays short.

Twice a year the people in Israel meet at a small bar in Jaffa whose name we will not print, and the people in Estonia do the same in Tallinn, then send photos. There is a house rule that nobody brings up deploys, bugs or the blog in the bar. Whoever does buys the next round. The rule survives because the fines pay for the round.

Nobody here is hiring. If you want to say hello anyway, support@voiddo.com reaches all six of us.