Senior Frontend Engineer
Job description
About the role
This role focuses on designing and building rich, performant web applications for wholesale distribution workflows. The position owns major frontend architecture while collaborating with product and design. It targets experienced engineers who turn complex supply-chain operations into elegant, reliable interfaces.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Core frontend capabilities advance through Svelte, TypeScript, and modern web tooling to serve distributor needs. Large, complex user interfaces move from architecture and implementation to polished performance through end-to-end ownership. Business logic from product designers and backend engineers becomes intuitive interfaces that streamline order processing and purchasing. Design systems and component libraries evolve to deliver consistency and speed across customer-facing tools. Performance, accessibility, and reliability improve across browsers and devices for operations in electrical supplies, plumbing, roofing, and HVAC segments. Teammates receive code review and mentorship that raises the frontend technical bar for robust, maintainable experiences.
Requirements
Professional frontend or full-stack engineering experience typically spans 5+ years in production settings. Expert-level knowledge of TypeScript and modern JavaScript, HTML, and CSS comes with a record of shipping complex, data-driven web applications. Deep understanding of frontend architecture, state management, and API integration patterns supports complex data-driven applications. Design sense and user empathy shape interfaces that are both functional and pleasant. Clear communication in remote, async environments coordinates work with distributors that move real economy materials. Frontend performance optimization experience benefits high-traffic operations dashboards.
Practical notes
Colombia appears as a listed location for this position. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Roles in this field commonly involve strong collaboration between frontend, backend, and product teams. Modern JavaScript ecosystems rely heavily on TypeScript, component libraries, and automated tooling. Performance, accessibility, and cross-browser compatibility are essential for business-critical applications. Remote, async workflows require clear communication and documented decisions. Building for wholesale distribution means working with real operational data and strict reliability expectations.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
About the company
Canals or artificial waterways are waterways or engineered channels built for drainage management or for conveyancing water transport vehicles. They carry free, calm surface flow under atmospheric pressure, and can be thought of as artificial rivers.