Associate Frontend Engineer

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.

About the role
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.

What you will be doing

• Build and update modular UI components using HTML, CSS, and basic JavaScript.
• Sit alongside logistics operators during hybrid collaboration days to observe where current interfaces cause friction.
• Trace frontend error logs to identify why specific forms or input fields are rejecting user data.
• Update internal documentation and user guides so operators understand interface changes.
• Conduct regular tests between our frontend interfaces and partner APIs to make sure data renders correctly.
• Write simple utility scripts to automate layout adjustments across our key internal toolsets.
• Test validation rules on different devices to make sure forms work correctly on warehouse handheld units.

What we need from you

• A solid initial understanding of HTML, CSS, and core JavaScript logic.
• The ability to use browser diagnostic tools to inspect elements and track network errors.
• Strong attention to detail, specifically when matching code layouts with layout drafts.
• Clear written communication skills for writing change logs and interface documentation.
• Comfort asking questions when a system error or operational procedure is unclear.
• Willingness to work in a hybrid setup, participating in local collaboration sessions during the week.
• Basic familiarity with Git for managing and pushing code changes.

Helpful background

• Exposure to JavaScript libraries like React, Vue, or Svelte through school projects or personal practice.
• Experience working in an operational environment, such as retail, warehouse management, or customer support.
• Basic understanding of client-server request methods and structured JSON web tokens.
• Prior exposure to CSS frameworks like Tailwind or Sass.

What the role offers

• Attractive pay that is highly competitive for entry-level positions in the current market.
• Direct mentoring from seasoned engineers who prioritize writing clean, maintainable code over complex meetings.
• Flexible hybrid work structure, balancing quiet coding days at home with focused local syncs.
• Clear development pathways with defined checkpoints to help you build your software engineering career.
• Up-to-date hardware, including a dedicated testing workspace setup.
• The opportunity to see your work directly validated in real-time by operators running essential logistics.

Working at Tech Pipeline
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.