Engineering Manager, Shipping & Logistics

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes sections: About the Engineering Organization, About the Role, Our Blended Work Environment, Our Tech Stack, What You’ll Do, Your Experience, salary and bonus info, benefits, Loop Story Commerce, values, etc. We need to map to headings: About the role (maybe combine About the Engineering Organization and About the Role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings exactly those strings if content exists. We need to decide which sections have content. - About the role: we have "About the Role:" paragraph describing responsibilities. Also "About the Engineering Organization:" could be considered part of about the role? Might be separate but we can include under About the role. - Responsibilities: we have "What You’ll Do:" bullet list of duties. Also some responsibilities in About the Role paragraph. We'll combine into Responsibilities section. - Requirements: we have "Your Experience:" list of required experience. Also maybe "Experience in SaaS..." etc. That's requirements. - Qualifications: maybe overlapping with Requirements; but we can treat Requirements as qualifications. However we need to decide if we have separate Qualifications content. The posting doesn't have a separate qualifications section besides experience. Could combine. - Skills: maybe we have tech stack, AI adoption, Agile, etc. Could be Skills. - Benefits: we have benefits list. - Pay: we have salary range and bonus. - Schedule: we have Blended Work Environment description (location, remote/hybrid). That's schedule info. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title. Not include Job ID. We must output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

... combined paragraphs ...

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

... salary range and bonus ...

Schedule

... blended work environment ...

We need to preserve all substantive information. Let's extract. About the Engineering Organization paragraph: "The Engineering Team at Loop is a balance of agility, consistency, and performance. These are the pillars that allow the team to constantly and reliably deliver value that matters to customers. That customer intimacy is what allows our engineering teams to be the best in our space, and bring the best ideas to the market." About the Role paragraph: "We’re hiring an Engineering Manager to lead a cross-functional product team at Loop. In this role, you’ll be responsible for the team’s technical direction, delivery, structure, and overall health. You’ll support and grow an autonomous, self-managing, high-performing team while partnering closely with product and design to build valuable, high-quality software. You’ll balance features, tech debt, support, and innovation work, and make decisions that align with Loop’s broader vision and engineering standards. You’ll hold formal authority over your team’s roadmap, backlog, technical direction, and hiring decisions, while actively seeking input from your team and stakeholders. You’ll be expected to drive strong execution, clear communication, and a culture of trust and accountability. Above all, you’ll lead with empathy, model Loop’s values, and help your team stay focused on what matters most. You’ll serve as one-third of the product trifecta (Engineering, Product, Design), so success in this role depends on your ability to collaborate effectively, communicate proactively, and build trust with your counterparts. This role is highly autonomous, and we expect our managers to be curious, decisive, and action-oriented; someone who looks ahead, adjusts course early, and keeps the right people informed throughout." We can combine these two paragraphs under About the role. Responsibilities: "What You’ll Do:" list: - Lead and grow an autonomous, high-performing, self-managing, and inclusive engineering team through strong coaching, clear expectations, and thoughtful structure. - Own the shipping and logistics domain end-to-end, carrier integrations, rate shopping, label generation, and the systems that support them. - Own your team’s technical direction, backlog priorities, and delivery processes; balancing input from the team, stakeholders, and company strategy. - Champion AI adoption on your team, making AI agents the default starting point for project planning, issue triage, and software development. - Set clear expectations, give people the support and time to build the skill, and review AI-generated work with the same rigor you'd apply to any code. - Hold the team accountable to engineering fundamentals like test-driven development, SOLID principles, and sustainable delivery practices. This will be done through a deep inspection of the technical output of the team. - Partner closely with Product and Design to shape the roadmap, estimate confidently, and communicate decisions clearly. - Foster a culture of accountability, visibility, and healthy communication across your team and with stakeholders. - Champion Loop’s mission and values through your leadership, decision-making, and everyday interactions. Also some responsibilities from About the Role paragraph could be included but we already have them; but to preserve all info, we could include them as part of Responsibilities as well. However we might duplicate. Better to keep About the role separate (overview) and Responsibilities as the What You’ll Do list. That covers all. Requirements: "Your Experience:" list: - 3+ years of experience managing high-performing, product-focused software engineering teams, with a track record of delivering business value. - Experience in SaaS, startup, or ecommerce environments is highly desirable, and exposure to shipping, fulfillment, reverse logistics, or complex integrations is a plus, not a requirement. - Recent hands-on experience as a software engineer, with the technical depth to engage in architectural decisions, mentor developers, and drive practices like test-driven development and scalable system design. - You use AI agents as a default part of how you and your team work, and you can describe specifically how that changed your team's output. - Strong grasp of Agile software principles, including SCRUM, with a history of shipping high-quality software through iterative, incremental delivery. - Proven ability to balance competing priorities, manage stakeholder expectations, and make thoughtful tradeoffs under real-world constraints. - Known for building trust through clear communication, consistent values, and a feedback-rich culture of accountability and performance. Also maybe "Our hiring process is tech-stack agnostic." Not a requirement. Skills: Could include tech stack: PHP/Laravel, Vue.js, MySQL, DynamoDB, Kubernetes, AWS, Jira, Claude, Cursor, Datadog, Snowflake. Also AI adoption, Agile/Scrum, test-driven development, SOLID, etc. But many of those are already in requirements. However we can still list skills: technical stack, AI agents, Agile, TDD, SOLID, etc. We'll create a Skills section with bullet list of those. Benefits: list: medical, dental, and vision insurance, flexible PTO, company holidays, sick & safe leave, parental leave, 401k, monthly wellness benefit, home workstation benefit, phone/internet benefit, and equity. Pay: salary range $150,000 - $190,000 a year, plus annual performance bonus expected to be 10% of base salary. Also note about compensation strategy etc. We'll include the substantive: salary range and bonus. Also note that posted salary range is base salary, subject to change, actual based on factors. We'll keep that info. Schedule: Blended Work Environment: "Our team is based across our headquarters in Columbus, Ohio, as well as Hub and Secluded locations throughout the United States, select Canadian provinces, the United Kingdom, and select Australian states. For this role, we're looking for someone based in the United States." Also mention "Blended Working Environment". We'll include that. We must not include boilerplate like "Loop Story Commerce should feel effortless..." etc. That's not required for sections; we can drop as it's not about role, responsibilities, etc. It's company description; could be considered About the role? But it's more about company mission. The instruction says preserve ALL substantive information; but we must not invent or summarize away detail. However we can omit sections that are not requested headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must include all text; we must preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should keep all substantive info from the posting, but we can reformat into sections. The company mission paragraph is substantive; we could include it under About the role maybe as a paragraph. But the instruction about sections: use headings for those specific headings; we can still have other paragraphs not under those headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Likely they want only those headings. However they said "include a section ONLY when the posting has real, specific content for it". So we can have other paragraphs not under those headings? Probably they expect we only use those headings for sections; any other content should be placed under appropriate heading. The company mission could go under About the role as it's about the organization. But we already have About the Engineering Organization and About the Role paragraphs. The mission paragraph is more about Loop story; could be considered part of About the role or maybe we could add a separate paragraph under About the role after the existing ones. We'll include it as a paragraph under About the role. Also "Our Tech Stack:" could go under Skills. Also "Our hiring process is tech-stack agnostic." Not needed for sections. Also "Learn more about us here: ..." and privacy notice etc. That's boilerplate navigation; we should remove. Also "We may use artificial intelligence (AI) tools..." that's hiring process boilerplate; we can remove as it's not substantive about role? It's about hiring process; could be considered meta but likely to be removed as per instruction to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is about AI tools in hiring process; could be considered boilerplate; we can drop. Thus final HTML:

About the role

The Engineering Team at Loop is a balance of agility, consistency, and performance. These are the pillars that allow the team to constantly and reliably deliver value that matters to customers. That customer intimacy is what allows our engineering teams to be the best in our space, and bring the best ideas to the market.

We’re hiring an Engineering Manager to lead a cross-functional product team at Loop. In this role, you’ll be responsible for the team’s technical direction, delivery, structure, and overall health. You’ll support and grow an autonomous, self-managing, high-performing team while partnering closely with product and design to build valuable, high-quality software. You’ll balance features, tech debt, support, and innovation work, and make decisions that align with Loop’s broader vision and engineering standards. You’ll hold formal authority over your team’s roadmap, backlog, technical direction, and hiring decisions, while actively seeking input from your team and stakeholders. You’ll be expected to drive strong execution, clear communication, and a culture of trust and accountability. Above all