Senior Product Engineer

Role Purpose The Product Owner / Senior Business Analyst is responsible for defining and delivering innovative supply chain solutions that solve real customer problems and contribute to the evolution of the Cargoo platform. This role leads the development team through the entire product development lifecycle, ensuring timely delivery of high-quality products aligned with company goals and customer needs. The successful candidate will own product decisions, balancing customer value, technical feasibility, business priorities, and delivery timelines. This role reports to the Head of Product (Christina Chapialevich). Key Responsibilities Product Vision & Strategy * Collaborate closely with stakeholders to define and refine the product vision and strategy, ensuring alignment with company goals and customer needs. * Take ownership of product decisions, balancing customer value, technical feasibility, business priorities, and delivery timelines. Leadership & Delivery * Lead the development team through the entire product development lifecycle, ensuring timely delivery of high-quality products that comply with internal policies and standards. * Make decisions on the product's scope, schedule, and quality to ensure the team stays on track and delivers value. Product Management & Requirements * Build innovative supply chain solutions that solve real customer problems while contributing to the evolution of the Cargoo platform. * Create detailed Use Cases, Requirements, and Business Rules to guide development, ensuring clarity and alignment with business objectives. * Work closely with stakeholders to develop and manage User Stories and Acceptance Criteria that accurately reflect business needs. * Own and continuously refine the Product Backlog, ensuring the team always works on the highest-value opportunities. Candidate Profile Education & Experience * 5+ years of experience managing software development projects, with a strong preference for experience as a Product Owner. * Proven track record of strong managerial skills, including team leadership, decision-making, and conflict resolution. * Degree or Diploma in Information Technology, Informatics, or a related field. Technical Skills (Must Have) * In-depth understanding of Agile values, principles, and frameworks (Scrum, Kanban, Lean) with the ability to implement them effectively. * Strong analytical skills. * Experience in logistics solutions or a logistics background is a strong plus. * Fluency in English, both verbal and written, is required. Behavioural Traits * Excellent verbal and written communication skills, with the ability to interact with both technical and non-technical audiences, including customers, executives, managers, and subject matter experts. * Strong leadership and decision-making capabilities, with the ability to guide teams and resolve conflicts. * Analytical mindset with a structured, value-driven approach to prioritization.

ROLE OVERVIEW: At Cargoo we are building the infrastructure that makes Freight reliable and scalable. Real-time logistics systems, built in .NET. PROBLEM SPACE:  Logistics operations today are still largely:  * manual  * reactive  * fragmented across tools  * incomplete / late data  * conflicting constraints  * real-time decision pressure  * evolving business rules  * legacy + new system coexistence  WE’RE BUILDING A SYSTEM THAT:  * ingests real-time operational data  * supports planning & execution decisions  * adapts to constantly changing constraints  DESIGN PRINCIPLES: * keep things simple before scalable * prefer explicit logic over magic abstractions * optimize for change, not perfection * avoid “framework-driven architecture” * accept that some parts will be ugly — temporarily  TECH STACK: * .NET  * Vue.JS * service-oriented architecture * relational + operational data storage * cloud-based infrastructure  WHAT WE EXPECT FROM ENGINEERS: * Ability to navigate uncertainty and work in ambiguity * Willingness to challenge decisions * Focus on outcomes, not just code * Understanding of trade-offs and complex systems * Preferring ownership over comfort  WHAT YOU WONT FIND HERE:  * over-engineering everything upfront * unnecessary microservices * “clean architecture” for the sake of it * process-heavy development  If this resonates with you – lets talk!  Send us:  * your LinkedIn / GitHub * OR a short message explaining what you’ve built and why it matters