The 90-day product engineer
My mandate was simple: ship code and build fast. I had exactly three months to deliver, and balancing that intense, part-time sprint with the rest of my life was a monumental task.
But the most defining part of this experience wasn't the building itself. It was the context. I was hired by an early-stage startup with a fully remote team scattered around the world. The time zone differences, the asynchronous communication, and the pressure to move quickly all compounded into one of the most unique engineering challenges I've faced.
From SWE to product whisperer
Working at that stage meant there were no neatly packaged tasks. There was no time for hand-holding or a long ramp-up — I had to adapt instantly. From the first week I was submitting PRs and making impactful changes.
I started from my strengths as a frontend engineer, but the product quickly pushed me into unfamiliar backend support work. That forced me outside my comfort zone and into full-stack territory.
I evolved from a typical software engineer into a product engineer. The role wasn't just coding against a spec — I was joining product discussions, doing research, and working with design to move concepts into prototypes and then into the main build. Having a seat at the table where the what and why were decided, not just the how, was the most rewarding shift.
The time zone tango
The rest of the engineering team were absolute superstars. They operated at a level that was genuinely admirable, and I did my best to match that velocity and quality.
That high bar also amplified communication hurdles. How do you get quick answers when teammates are eight hours ahead or behind? I had to be precise, predictive, and detailed in asynchronous messages — knowing a simple question could cost a full day of productivity.
It was a strange feeling being the youngest person at the startup, surrounded by people whose professional experience was longer than my actual life. I wasn't treated as a kid. Being sharp with tools like Cursor and Claude Code let me accelerate understanding of the codebase and ship faster — proof that the modern engineer's toolkit matters as much as years of experience.
The pressure of the double life
All of this ran parallel to a separate full-time role as design engineer / head of product design / only designer. The startup contract was a three-month sprint beside another marathon.
That double life added relentless pressure — debugging failing builds while juggling design reviews elsewhere. I had to be relentlessly productive during contracted hours.
In the end it paid off. Everything I worked on went live with the product release: frontend integration, UI work, migrations across codebases. I may not have learned a new framework, but I learned how to move, adapt, and ship under pressure.
An accelerated trajectory
The difference between how I started and how I ended that contract was night and day. It wasn't just a contract — it was an avenue to grow in an accelerated amount of time.
I wouldn't trade it. Ownership, communication, and high-velocity shipping travel with me. If you want market insights and community conversations, check out the work at swiirl.io — I'm excited for what they build next.
Originally on Substack