Kiril M.

Reported directly to the CTO across two phases of work.

Phase 1 - Client project:

- Took a messy Next.js + Go codebase for one of Onli's clients, cleaned it up, built out the missing features, and shipped it to production - the company's first client to actually go live.

Phase 2 - Onli Cloud

- Onli Cloud is the developer platform on top of Onli's core asset technology - it's where developers build "Appliances" that interact with digital assets. Onli Cloud started as an early prototype the CTO had built to show shareholders. I took the concept and built the product from scratch.

- Owned UI/UX end-to-end — handed rough notes on how things should work and left to figure out the rest. This is where I started moving from full-stack to product engineer.

- Migrated the codebase to Turborepo so the product could support multiple versions of the core gRPC packages in parallel.

- Since the users were developers, I wrote a DX-friendly wrapper library on top of the painful proprietary gRPC packages they'd otherwise have to use directly.

- Built the Stripe billing flow. Webhook-heavy, since payments triggered VPS provisioning on the backend.

Local navigation mobile app launched in December 2025. Grew to 10k users and is still running in production.

- Started with a coffee and an idea from the founder. Left as the lead engineer on the project.

- Made the stack calls: React Native for the mobile app, Postgres with PostGIS for location queries, Redis, Docker.

- Brought on a mobile developer (referral from the Onli CTO) to build the React Native app. Coordinated with him throughout, designed and delivered the backend API endpoints he needed.

- Built the full backend and web admin panel myself - ElysiaJS, Vite + React

- Tight budget meant hard choices on scope, worked with the founder on what to cut and what to keep, prioritizing the features that actually needed to ship for launch.

- Set up production deployment with backups.