Loading…
the working blog
Entries from real work — decisions, dead ends, and the fixes that stuck.
We were releasing sign-in via MyID, Uzbekistan's face-recognition identity system — and found that on phones a successful face scan dropped users back on the login page as if nothing happened. Here's how we prepared the release, hunted the bug down to a single line, and fixed it.
A user's cancellation refund was approved and paid, yet their cabinet showed "in progress" forever. The bug lived between two systems that never talked to each other — here's how I found it, made the status update itself before the user's eyes, and prepared the flow for the statuses still to come.
Three improvements around our online policy cancellation: every attempt now starts with a real identity check through MyID, the page no longer asks for card details when a request already exists, and "nothing here yet" screens finally help instead of confusing.
Cancelling a policy used to mean a trip to the office. I wired our customer cabinet to a new cancellation service built by my teammate, so now a customer picks a policy, sees the exact refund, enters a card, and tracks the request — all online.
A three-day sprint on the gross.uz personal cabinet: switching it to a single trustworthy data source, finding policies users didn't know they had, and polishing the interface until it feels like an app instead of a website.
I rebuilt the logged-in area of an insurance website from the ground up — a multi-page "personal cabinet" where customers see every policy they hold across the whole company, verify their identity with the national ID system, and manage their cars, property and profile. It's live in production and I'm still adding to it.
On my first day at an insurance company, I was asked to "edit the feedback form." It grew into a feature that touched everything — a floating button on the homepage, a pop-up form, and a change deep in the database so the support team could call users back instead of emailing them.
A trucking dashboard feature that watches every load on the road, works out whether it'll hit its delivery deadline, and pings the office the moment one starts running late — so a problem becomes a phone call you make, not one you receive.