Recibe más respuestas de empleadores
Envía un currículum específico para el puesto de trabajo en cuestión de minutos.
Tech Pipeline in Madrid is looking for an Associate Frontend Engineer to enhance user interfaces that streamline operations. You will work closely with logistics operators, using a hybrid model to develop UI components and conduct testing to ensure smooth functionality.
The ideal candidate should have a solid foundation in HTML, CSS, and JavaScript, along with an eagerness to learn in a supportive environment. The role offers mentoring and clear paths for career development in frontend engineering.
We are looking for an Associate Frontend Engineer to help us build and refine the user interfaces that keep business operations moving smoothly. At Tech Pipeline, we resolve the friction in operational processes, fixing the UI layout bugs and broken data forms that slow client teams down. For this project, our partner is a central European logistics business, and you will help build interface tools that make their daily routing and exception handling straightforward.
Our partner is currently facing daily challenges where internal operators are stuck reconciling transport data using spreadsheets and slow, legacy admin screens. We do not do abstract design theory or build heavy, slow dashboards. Instead, we look at the exact places where the interface lags, why input forms fail silently, and why the team is forced to copy‑paste data between tools. As an Associate Frontend Engineer, you will work within a hybrid model: you will work from home for part of the week and join us in person at our partner's workspace during scheduled collaboration days to sit directly with the operators. You will help write clean, component‑based frontend code to replace clunky forms, design clear validation cues, and ensure that when a routing rule fails, the operator sees a clear error message instead of a generic system crash. This role is built for someone starting their development career who values direct, useful solutions.
We value direct, low-overhead communication over long alignment meetings. Most of our coordination happens asynchronously using written weekly updates and detailed internal documentation. Since we operate in a hybrid pattern, we use our in-person sessions to sit with client operators, map out system blockages, and test our code, while dedicating remote days to focused coding times. We believe that a great system is one that can be easily run by the client team after we leave, which is why everything we write: from routing tools to frontend scripts: is clearly explained and fully documented.