Twelve years as the remote engineer for a Sydney studio's client work

Webbed Studio (Sydney, Australia) Apr 2014 – present Full-stack engineer, web & mobile · remote

A browser window showing a marketing page, with booking and checkout cards layered in front

The situation

Webbed Studio is a small Sydney studio serving Australian clients. Its projects run from marketing sites to e-commerce and booking systems, which means the same engagement covers both a brochure that has to look right and a checkout that has to be correct. I have been their remote engineer since April 2014.

What made it hard

A studio this size has no bench: whoever builds a project also maintains it, sometimes years later, so the cost of a clever shortcut lands on the person who took it. Client budgets are real, the brief often arrives as a design rather than a specification, and I work from Kathmandu against Sydney hours, so decisions have to survive a night without me.

My part in it

Design and full-stack build, working directly with the studio's principals rather than through a project layer. On most engagements I am the only engineer. The studio owns the client relationship and the brand direction; I own how it is built and, on many projects, how the interface resolves once it meets real content and real data.

What I built, and why

E-commerce and booking flows

The parts clients actually get judged on: choosing something, paying for it, and getting a confirmation that matches what the business will honour. Laravel on the back end with Vue.js or React on the front, and the state kept somewhere a refresh cannot corrupt.

Marketing sites that survive their content

Responsive builds from studio designs, structured so the client can edit them later without a call. The recurring lesson over twelve years is that a layout is only finished once someone who did not design it has typed a paragraph twice as long as the placeholder.

Long maintenance, on purpose

Several of these projects I have now maintained for years: framework upgrades, payment and integration changes, and features added to a codebase whose original decisions I am accountable for. It is the least glamorous part of the work and the part that most decides whether a client is well served.

Where it stands

Twelve years with the same studio, across a series of Australian client projects, working async from a different hemisphere the whole time.

  • Laravel
  • Vue.js
  • React
  • PHP
  • MySQL
  • Tailwind CSS
  • Figma

Some organisations in this case study are described rather than named, and internal products are described by what they do. Client names appear here only where the work is publicly credited or the studio has agreed to it.

Back to selected work