Software Engineering Manager - Commerce (100% Remote)

Hopper Technology Solutions is seeking a smart, creative, and hands-on Engineering Manager to lead a squad dedicated to high-stakes Enterprise and Corporate B2B partners. In this role, you will manage a high-performing team of engineers building complex systems while ensuring technical excellence and reliability for enterprise clients.

Responsibilities:

• Hire, mentor, and coach a multidisciplinary squad. You’ll be responsible for building a high-trust culture where engineers are empowered to act like owners
• Partner closely with product teams to translate "big-picture" partner needs into executable technical roadmaps. You’ll ensure we ship high-quality features while managing the unique complexities of B2B integrations and public-facing APIs
• While you won't be coding 100% of the time, you will stay deeply technical. You’ll lead architectural reviews, help unblock complex debugging sessions, and ensure our stack remains scalable and resilient
• Own the "run" of your team’s services. This means establishing on-call rotations, driving down technical debt strategically, and ensuring our systems meet the strict SLAs required by our enterprise corporate partners
• Act as the primary technical point of contact for external partners. You must be able to explain complex system constraints to non-technical stakeholders and advocate for the best technical path forward. There may be some travel within North America for client meetings

Requirements:

• 2+ years of experience leading engineering teams
• 7+ years in software development (ideally with JVM/Scala or React experience)
• Experience with microservices, distributed systems, and designing APIs that are robust enough for global enterprise use
• Ability to build the 'MVP' without sacrificing the long-term integrity of the system
• Preference for a 'ship and iterate' approach
• Proven track record of growing junior engineers into seniors and seniors into leads/architects
• Ability to explain complex system constraints to non-technical stakeholders
• Comfortable with ambiguity