fig. 03 / employment
Burt
Production engineering on an advertising analytics platform, across an Angular frontend and a Rails backend, with a team in Sweden.
- Client
- Burt Intelligence · AdTech SaaS
- Role
- Frontend Engineer
- Stack
- Angular · TypeScript · Ruby on Rails · Tailwind · AWS
No screenshots: the product lives behind auth. Written record only.
Context
Burt Intelligence builds analytics software for the advertising industry. My title is frontend engineer; in practice the work runs across the whole production codebase, an Angular frontend and a Rails backend. I’m based in the Philippines, with a team in Sweden.
Problem space
AdTech analytics is dense by nature: large volumes of campaign and revenue data that have to be legible to the people whose job depends on reading them correctly. The frontend work is mostly about making data-heavy interfaces fast and trustworthy; the backend work is about getting the right data to them reliably.
What shipped
Over thirty features and bugfixes across the platform so far, from new functionality to high-priority production defects, including the quick, careful changes that emergency cases demand.
I also aid the big lifts: major Angular version updates and other platform-wide changes that have to land without breaking what is already in production.
How I work
I work from 3 pm to midnight to share my team's working day in Sweden, so collaboration happens live. Distance still makes writing the backbone: clear pull requests, honest code review, and changes scoped so anyone can pick them up.
Owning changes across both halves of the stack is the norm here, not the exception. A feature is done when it ships end to end, not when one layer of it does.
Scale
This is a production platform in daily use by paying customers, the kind of codebase where changes are reviewed, releases are deliberate, and the cost of being wrong is real.