I build production software for complex, data-heavy products.

Problem

Production builds took more than 15 minutes, which slowed every release. Separately, the application became slower the longer someone used it, and no single screen explained why.

What I owned

The build and CI/CD optimization, the performance investigation and its fix, and the Angular upgrades across major versions.

Engineering challenges

• The slowdown had no single cause: it ran through component lifecycles, RxJS subscriptions, routing, and the filtering and search architecture
• Custom directive and routing abstractions kept subscriptions alive after navigation
• Each Angular major version brought breaking changes, dependency conflicts and regressions

Technical decisions

• Simplify the filter, sort and search flows rather than add fixes on top of the abstraction
• Make subscription teardown explicit, with take(1) for one-shot streams
• Shrink the application first, then tune build configuration

Key work

• Removed heavy and unnecessary dependencies
• Reworked component imports and routing
• Improved build configuration
• Corrected lifecycle handling and terminated leftover processes
• Angular major-version upgrades

Outcome

• Build pipeline: 15+ min → ~5 min, about 67% faster
• Application size: roughly 40 MB → 23 MB
• Long-session slowdown eliminated
• Application running on Angular 22

Problem

Users needed to analyze arbitrary areas, not only predefined boundaries, and MapLibre has no native freehand drawing. Search was limited to a single metro, a single state, or the whole country.

What I owned

On the frontend: the Mapbox to MapLibre migration, the freehand selection tool, and multi-market search from proposal to release.

Engineering challenges

• Building a drawing interaction the map library does not provide
• Turning a hand-drawn shape into a selection that property and rent analysis can run against
• Changing map engines without losing existing map functionality

Technical decisions

• Build the drawing tool directly on MapLibre, so selection is not limited to predefined shapes or boundaries
• Preserve existing map behaviour through the migration first, then extend it
• Let users combine markets, rather than choose between one market and a national search

Key work

• Freehand geographic selection
• Aggregated property and rent analysis for the selected area
• Survey and reporting tools around selected properties and markets
• Metro, state and national scopes
• Multi-market search

Outcome

• Users draw any area and analyze the properties and rental data inside it
• Searches are scoped to the markets needed, instead of falling back to national searches
• The platform’s maps run on MapLibre

Problem

Two kinds of accounts, customers and service providers (Hackas), each with their own experience and permissions, and a way for them to find, message and book each other.

What I owned

The whole product: architecture, the Angular application, the Firebase backend and Cloud Functions.

Engineering challenges

• Role-based access for two account types
• Keeping backend logic out of the client
• Messaging and booking workflows that involve both sides

Technical decisions

• Firebase custom claims carry each account’s role and drive role-based access
• Backend logic runs in Cloud Functions

Key work

• Customer and provider experiences
• Authentication and role-based access
• Service search
• In-app messaging
• Service booking workflows

Outcome

A complete marketplace covering both sides, from search to messaging and booking. The product has since been discontinued by its owners.

Problem

People who produce their own electricity needed a simple way to sell the surplus to neighbours, and consumers a way to buy it. Both needed to follow their energy, trades and payments in one place, in their own language.

What I owned

Frontend development in Angular, integrating with the microservices backend and working alongside backend engineers.

Key work

• Overview, energy market, analytics and history views
• Charts and visualizations for energy data
• Login, registration and access privileges
• Account settings and payment methods
• Localization across the interface
• Responsive layouts for desktop and mobile