Employment work
TEQ Fleet Management
Full-stack product engineering for a Norway-based, multi-tenant and multilingual fleet management platform.
Context
TEQ is a Norway-based fleet management and transportation platform serving multiple tenants and languages. From trainee through my earlier engineering roles at Brain Station 23, it was the product where I developed much of my full-stack foundation and fleet-management domain knowledge.
Problem
Fleet products connect operational workflows with real-world movement. Customers need current vehicle information, feedback flows, and timely responses, while each tenant needs the product to respect its own users, data, and language.
My role
I worked across Python and Django backend services, PostgreSQL, background processing with Celery, and frontend applications in Vue.js and React. I introduced customer-facing features including survey and feedback features, vehicle live tracking, driver single sign-on (SSO), and real-time response notifications. I also restructured existing components, resolved defects, and optimized backend workflows.
Constraints
A multi-tenant platform must keep tenant boundaries clear while sharing a product codebase. Live vehicle information and notifications also introduce external-system and timing concerns. I am describing the product domain and my contribution without publishing tenant data or internal topology.
Reasoning
Fleet workflows are end-to-end by nature: a backend event is useful only when the correct user sees a clear, timely update. That made API behavior, asynchronous work, frontend state, and tenant-aware data access parts of one product decision rather than separate specialties.
Outcome
The work delivered new customer-facing fleet features and improved the reliability and maintainability of existing application flows. It also gave me sustained production experience across the full stack in a multi-tenant fleet domain.
Reflection
TEQ is the clearest evidence behind my full-stack identity. It taught me to follow a feature from domain workflow and data model through API, interface, background processing, and production behavior.