Ashley Wong
Yeswith one reservation
Overview
Built the first version of a B2B scheduling product alone over four months, then brought on two engineers and shipped it to paying customers. The timeline held up under questioning, and two of the customers they named are on the company’s site.
Questions we asked and responses
- What did you own, end to end?
- All of the first version: the data model, the API, and the web app. Two engineers joined in month four and they handed off the front end.
- What broke first once real customers were on it?
- Calendar sync drifted after a timezone change and a customer missed a meeting. They walked us through how they found it, the patch that shipped that night, and the proper fix that took a week.
- What did you cut to ship in four months?
- Listed the cuts in order (no mobile, no permissions, a manual import instead of an integration) and said which one they regretted. The manual import. It cost them a customer.
What gave us reservations
Testing. When we asked how they knew the sync fix actually worked, the answer was “we watched it for a week.” No test, no alert. That’s fine at a hundred customers and it isn’t at ten thousand. When we pushed, they agreed rather than defended it, which is the better sign.
What to ask them
Ask them to redesign the sync so the timezone bug can’t happen again, out loud, on a whiteboard. We’d hire them if they reach for the data model before they reach for a retry loop.