2025
Project One
Product · WebA product engineering case study covering problem, constraints, and what shipped. Stack: TypeScript, React, Postgres.
01 / About
A short introduction
I design and ship software end-to-end. My work sits between product design, front-end engineering, and systems thinking — wherever the seam is messiest.
For the past few years I have been focused on tools that feel direct: less chrome, more substance. I care about typography, motion that earns its keep, and interfaces that respect the reader's attention.
Outside of client work I write small utilities, sketch in code, and read about the history of computing. Some of those experiments live on GitHub; the fastest channel for everything else is Telegram.
Recent client engagements have focused on tools for thought, local-first applications, and ambient AI interfaces — areas where the seam between product design and front-end engineering matters most. I work asynchronously across timezones, lean on strong written documentation, and prefer typed languages everywhere: TypeScript on the web, Swift on iOS, and Postgres for state.
02 / Work
Selected product engineering work
Three recent product engineering projects, spanning web, iOS, and open-source tooling. Each entry covers role, stack, year, and a short narrative of what shipped.
Three slots, each with role, stack, year, and a short narrative. See the full write-ups on request or browse the public projects on GitHub.
03 / Languages
Languages I work in
- 01 Russian Native
- 02 English Professional working
04 / FAQ
Frequently asked questions
Are you available for new work?
Yes. I take on product engineering, design partnerships, and small consulting engagements. The fastest way to reach me is email or Telegram.
Where are you based?
Yakutsk, Russia (GMT+9). I work remotely with teams worldwide and have lived with eight-to-twelve-hour timezone gaps for years.
What is your stack?
TypeScript and React for the web; Swift and SwiftUI for iOS; Figma for design. I lean toward small, sharp tools — Postgres, Node, plain CSS — over heavy frameworks.
Do you work full-time, contract, or both?
Independent practice since 2019, primarily on contract. Open to longer engagements when the problem and the team are a good fit.
What kind of projects do you take on?
Product engineering at the design-and-code seam: shipping new surfaces, redesigning existing ones, and the systems work underneath. Particularly interested in tools for thought, local-first software, and ambient interfaces.
How do you typically engage?
Two shapes work best: a focused product engineering sprint (four to eight weeks) for a specific surface or feature, or an ongoing retainer for a few days a week alongside an in-house team. Discovery and scoping are always part of the first conversation.
How do you handle remote work and timezones?
I work from Yakutsk (GMT+9), which gives a meaningful overlap window with both Europe and the US West Coast. Default mode is asynchronous — written specs, recorded walkthroughs, and clear PRs — with a couple of live calls per week when the team needs them.
05 / Contact
Let's talk
Open to product engineering work, design partnerships, and small consulting engagements. The fastest way to reach me:
- Email [email protected]
- Telegram @mikakostoev
- Phone +7 (993) 601-99-35
- GitHub github.com/mikakostoev
- Location Yakutsk, Sakha Republic, GMT+9