Full-Stack Software Developer
Software announces itself when it fails — 3 a.m. pages, mystery bugs, services nobody dares touch. I build products end to end, one hand from database to last pixel, and hand them over quiet enough to forget about.
The Craft
Most software fails at the seams — where the frontend team's assumptions meet the backend team's reality. Working full-stack means there are no seams to fail: the person shaping the API is the same person consuming it.
Eight years in, my work spans fintech platforms moving real money, developer tools with demanding users, and consumer products where 200 ms of delay is a design flaw. Different domains, one standard: restraint everywhere, precision where it counts.
The best infrastructure is the kind nobody has to think about.
One cut in the right place beats ten in the wrong ones.
The same standard on line one and on line ten thousand.
Selected Work
Each ran from the first schema sketch to production monitoring — one continuous line of responsibility, with no handoffs for things to fall through.
Multi-currency treasury platform for mid-size exporters. I built the double-entry core, the reconciliation engine, and the dashboard the CFO actually opens every morning. Idempotent by design: replaying a day of webhooks changes nothing.
Developer tool that traces flaky tests back to the commits that made them flaky. A Go ingestion pipeline chewing through 40 GB of test logs daily, a query layer over ClickHouse, and a frontend where every chart answers exactly one question.
Storefront and workshop-management suite for independent furniture makers. Inventory, commissions and payments in one system that a two-person workshop can run without a manual.
The Kit
What people touch
What holds it up
What keeps it standing
The Way
A short discovery sprint: the real constraint, the real user, the real deadline. You get a written plan with costs before any code exists.
Schema, API contracts and infrastructure sketched together, so the parts are designed to fit instead of forced to.
Weekly working software, not weekly slide decks. You click a staging URL every Friday, from week one.
Load tests, monitoring, and a handover your team can actually run with. Then I disappear — and stay reachable through the first month of weather.
Artur is the only engineer we've worked with who argued against building something we asked for — and was right. The system he did build hasn't paged anyone in fourteen months.
Most visitors never type a thing. Since you did: there is no secret technique — only short feedback loops and a refusal to ship what I don't understand. Mention the shuriken when you write.