AQTech
AQTech builds software for predictive maintenance of wind farms: it turns vibration and operational data from wind turbines into actionable information for engineers and managers, so equipment failures can be anticipated instead of discovered. I joined as a Frontend Intern, my first job on a professional software team after working only as a freelance developer, expecting to learn how engineering teams operate. Within a few months I became the team's frontend reference, and most new screens passed through me.
Predictive maintenance for renewable energy. Wind turbines are heavily instrumented; the platform ingests their vibration and operational signals and transforms raw data into decisions about which asset needs attention, and before which failure. The frontend's job is to make dense, high-volume time-series and condition data legible to the engineers and managers who act on it, which put data visualization and information design at the center of the work.
- —Frontend feature delivery on the wind-farm monitoring platform, building new features and improving existing ones (Vue 2 and Vue 3, Nuxt, Vuex/Pinia, TypeScript/JavaScript, Vuetify, Tailwind, Axios, ECharts).
- —Building reusable components and maintaining the frontend architecture as the product's UI surface grew.
- —Collaborating with the backend services (.NET / C#) that fed the frontend.
- —Contributing to a new Vue 3 product built alongside the existing Vue 2 platform.
- —Acting as the team's frontend reference, reviewing and guiding new screens, and advising on architecture, Design Systems, Figma, accessibility, UX, and reusable components.
- +Introduced frontend engineering standards where none existed. I identified the absence of a Design System on my own initiative, proposed it, built the Figma components, validated them with product owners and engineers, implemented the reusable Vue components, and taught the team to use them until it became part of how the team built software.
- +Became the team's frontend reference. I influenced how the team built frontend software (architecture, reusable components, Figma, accessibility, UX), with most new screens passing through me.
- +Made a build-vs-buy call and shipped a reusable abstraction. I built a hierarchical (tree) selector in-house instead of pulling in an external dependency for a single screen's need, designing it as a general, lazily-loading component the team could reuse rather than a one-off. (Summarized here rather than as a standalone case study; see note below.)
- +Contributed to a greenfield Vue 3 product developed alongside the existing Vue 2 platform.