PERSONAL INTERFACEPractice

What is claimed
and what is shown

A record of working as a front-end engineer. This page splits it into two axes — what is claimed and what can be shown — so it can print the case a résumé is built to hide.

In practice
13 years

Where the years went

No employer is named. Three already-published entries open by promising the reader that the organisation, the hosts and the member data are excluded, and they carry aggregate figures on the strength of that promise — naming a company here would revoke it retroactively. The role and the scope are stated in full.

  1. 2022.03present

    Frontend part lead

    Proptech · internal platform and customer-facing services

    Owned

    Built and ran the design system — React components and an icon library as packages, automated publishing to a private registry, foundations and tokens designed together with the design team. Stood up a new service on a monorepo, rebuilt the mobile web, and built an external CRM from scratch. The deployment pipeline was set up in this era too.

    What this era changed

    The work moved from getting it right alone to keeping several people from getting it wrong. The habit of writing conventions into a document and pinning them with a gate started here — because things that fail silently kept getting through review.

    What you can read

  2. 2021.072022.02

    Tech lead

    Early-stage startup · mobile app and API

    Owned

    Owned a React Native app from screen design through store release, and built a React admin and a NestJS REST API alongside it. Designed the OAuth flow and JWT authorisation directly, and ran CI/CD and the servers from the same seat.

    What this era changed

    Learned that almost no decision ends at the front end. Only after writing the auth flow through to the server did it become clear what token expiry actually costs the screen.

  3. 2020.052020.12

    IT team lead

    Logistics B2B2C · warehouse management

    Owned

    Developed a B2B2C platform while analysing the existing warehouse management system and doing the up-front design for its rebuild. The real deliverable was the handover and the technical write-up at an early stage of the service.

    What this era changed

    Eight months, and what was left behind was documents rather than code. It was the first time the deliverable in a role built around handover turned out to be a record someone else could read.

  4. 2013.012020.04

    Frontend · app development

    Agency and early-stage startups (summarised)

    Owned

    Built a React Native car-sharing service, and maintained admin tools and services on Vue 2 and Angular. Took over and worked in legacy environments across a number of agency projects.

    What this era changed

    Most of it was inherited work. The habit of reading someone else's code first was formed here, and it is also why the tool being built now is one that reads other people's changes.


What can be shown

The number is a count of entries you can open on this site, not a rating. The zeros are not hidden — a zero means the CV asserts it and this site has not proven it yet, which also makes it the list of what to write next.

Interface

Architecture

Verification

Platform

Knowledge


Study

  • 2024.07present

    Computer science · data statistics, double major — in progress

  • 2004.032012.12

    BEng — mechatronics

Contact

GitHub profile →

One channel: GitHub. It is the only identity this site publishes. There is deliberately no phone number, address or email address, and a gate fails the build if any of the three appears on this page.