Global Aid Account Manager

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, there is "About Flexport:" paragraph describing company. That's not a section heading but could be "About the role"? Actually "About Flexport:" is about company, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if appropriate. We have sections: "The Opportunity" describing role. Could be "About the role". Then bullet list of responsibilities under "You Will Own ..." etc. That's responsibilities. Then "You Should Have" etc is qualifications/requirements. Then "You Will Get" includes ownership, etc maybe benefits? Actually "You Will Get Ownership..." includes some benefits like ownership, role, etc. Then "Competitive compensation, comprehensive benefits, and a vibrant company culture." Then salary range details. Then "Commitment to Equal Opportunity" etc is EEO boilerplate to remove. Then "Global Data Privacy Notice..." also boilerplate to remove. Then "per year" at end maybe leftover. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should strip out the EEO paragraph and data privacy notice. We need to preserve all substantive information. We need to decide which sections to output. Potential sections: - About the role: could include "About Flexport:" and "The Opportunity" description. But "About Flexport:" is about company, not role. However we could still put under About the role? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow that pattern. Likely they expect About the role to contain description of role and maybe company context. We'll include both About Flexport and The Opportunity under About the role. - Responsibilities: the bullet list under "You Will Own ..." etc. We'll extract each responsibility as

. - Requirements / Qualifications: The "You Should Have" list. Could be Requirements. Also maybe Qualifications separate? The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. Could combine? They said prefer a few substantive sections over many thin ones. So we could have one section for Requirements/Qualifications combined. But we have both headings available; we could use Requirements for the "You Should Have" list, and Qualifications maybe for something else? There's no separate qualifications list besides that. So we could just use Requirements. - Skills: maybe we could extract skills from the requirements list (like "Deep understanding of global trade..." etc). But we could also put under Skills. However we already have Requirements covering those. To avoid thin sections, maybe we combine Requirements and Skills into one Requirements section. But instruction says we can use Skills heading if we have specific skill content. The posting includes skills like "speak fluently about ocean, air, trucking, and customs", "Strong commercial instincts", etc. Those are skills. Could make a Skills section. - Benefits: The posting mentions "Competitive compensation, comprehensive benefits, and a vibrant company culture." Also earlier "You Will Get Ownership..." includes some intangible benefits. But we need specific benefits: they mention comprehensive benefits but not details. The instruction says never create Benefits section unless posting actually states them. It does state "comprehensive benefits" but not specific. Is that enough? It says "comprehensive benefits" is a statement but not specific detail. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Comprehensive benefits" is vague but it's a statement that benefits exist. Is that considered filler? It's not a specific benefit like medical, dental, etc. However later they detail compensation and mention bonus, equity, and comprehensive benefit offerings such as medical, dental, and flexible time off. Actually later in the text: "Base salary is just one part of our total rewards package at Flexport, which also includes bonus, equity, and comprehensive benefit offerings such as medical, dental, and flexible time off." That is specific benefits: medical, dental, flexible time off. So we have specific benefits mentioned. So we can create Benefits section with those. - Pay: The posting includes salary range: "The US base salary range for this position (this does not include bonus, equity and benefits): $83,600 - $104,500 USD". Also mentions bonus, equity. So we can create Pay section with that. - Schedule: No mention of schedule (full-time, part-time, remote). Not present, so omit Schedule. We also need to include any other metadata like Job ID etc - drop. We need to preserve all substantive information: include the description about Flexport, the opportunity, responsibilities, requirements, qualifications, skills, benefits, pay. We need to format using

headings,

• for lists,

  for prose. We must not repeat the job title as a heading (the page already shows it). No job title given in snippet, but we avoid. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's extract content. About Flexport paragraph: "At Flexport, we believe global trade can move the human race forward. That’s why it’s our mission to make global commerce so easy there will be more of it. We’re shaping the future of a $10T industry with solutions powered by innovative technology and exceptional people. Today, companies of all sizes - from emerging brands to Fortune 500s - use Flexport technology to move more than $19B of merchandise across 112 countries a year. The recent global supply chain crisis has put Flexport center stage as we continue to play a pivotal role in how goods move around the world. We are proud to have the support of the best investors in the game who believe in our mission, solutions and people. Ready to tackle global challenges that impact business, society, and the environment? Come join us." Then "The Opportunity Flexport.org is the humanitarian arm of Flexport. We serve nonprofits, NGOs, and mission-driven organizations that need to move impactful cargo reliably, often into some of the hardest environments to reach. As humanitarian and development needs keep climbing, the supply chain expertise our partners can count on matters more than ever. You'll own some of Flexport.org's most complex and highest-impact partner relationships. Your accounts span multiple shipping modes and trade lanes: ocean, air, trucking, and customs, and demand real supply chain fluency to navigate well. You won't just manage these relationships, you'll shape them. You bring a strategic point of view to every partner engagement, lead business reviews that drive real decisions, and connect the dots across Flexport's full product suite to help partners do more with what they have. You'll operate with full autonomy, hold a high bar on program growth and retention, and become someone junior teammates turn to for guidance." That's the role description. Now responsibilities bullet list under "You Will Own ...": - Own end-to-end success for a portfolio of complex, multi-modal Flexport.org partner accounts, including partners with significant program growth potential and high operational intensity. - Lead RFP bids and contract renewals end-to-end. - Serve as a true strategic partner to nonprofits, NGOs, and mission-driven organizations, going deep on their supply chain operations to find where Flexport can cut cost, add capability, or move faster. - Lead high-impact business reviews (QBRs/MBRs) that go beyond reporting. Bring market context, multi-modal insight, and recommendations tailored to each partner's mission and constraints. - Drive expansion across Flexport's full product suite, consistently meeting or exceeding program growth and retention targets. - Collaborate with Operations, Pricing, Legal, Trade Lane Management, and other Flexport.org teams on solutions that need internal alignment and creative problem-solving. - Mentor account teammates: share playbooks, join key partner calls, and help the team raise its game. - Use AI-enabled tools to automate and improve internal and partner-facing processes where it makes the work faster or better. Now "You Should Have" list: - 5+ years in account management, business development, or a similar partner-facing role. - A background in logistics, supply chain, humanitarian aid, or international development is strongly preferred. - A track record of independently managing and growing a complex, multi-product book of business. - Deep understanding of global trade and supply chain operations across multiple modes. - You can speak fluently about ocean, air, trucking, and customs. - Comfort operating without a playbook in ambiguous or novel situations, and the judgment to write the playbook for others once you've solved it. - Strong commercial instincts: you spot growth opportunities before partners ask, and you close them. - Genuine curiosity about the humanitarian and development space. You want to become an expert in aid logistics, not just move freight. - A natural tendency to develop others. Peers and junior teammates get better from working alongside you. - A compliance-first mindset. We operate in a heavily regulated industry, and our partners and regulators need to trust us. Now "You Will Get" section: - Ownership of Flexport.org's most complex and meaningful partner relationships, the accounts where the impact is biggest. - A visible role in shaping how the Flexport.org account team operates. Your judgment and approach set the standard. - Opportunities to contribute to team playbooks, onboarding content, and process improvements. - A front-row seat on Flexport.org's mission: getting aid to the people who need it, on time. - Competitive compensation, comprehensive benefits, and a vibrant company culture. Then compensation details: "The range displayed on each job posting reflects the minimum and maximum target for new hire base salary for the position in the posting's respective region. Our salary ranges are determined by role, level, and location. Within the range displayed, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education and / or training. Base salary is just one part of our total rewards package at Flexport, which also includes bonus, equity, and comprehensive benefit offerings such as medical, dental, and flexible time off. The US base salary range for this position (this does not include bonus, equity and benefits): $83,600 - $104,500 USD" We need to capture that as Pay section. Now Benefits: we have "comprehensive benefit offerings such as medical, dental, and flexible time off." Also earlier "competitive compensation, comprehensive benefits, and a vibrant company culture." So we can list benefits: medical, dental, flexible time off. Also maybe "vibrant company culture" is not a benefit but could be included. We'll stick to specific benefits. Now we need to decide sections. Potential sections: - About the role: combine About Flexport and The Opportunity paragraphs. - Responsibilities: list of duties. - Requirements: maybe combine You Should Have (requirements) and maybe also include some of the "You Will Get" as benefits? No. - Skills: maybe extract skills from You Should Have: e.g., "speak fluently about ocean, air, trucking, and customs", "Strong commercial instincts", etc. But we could also put those under Requirements. To avoid many thin sections, we could have one Requirements section that includes both qualifications and skills. But the instruction allows us to use Skills heading if we have specific skill content. However they say prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section called Requirements (or Qualifications). But we need to pick one heading. The list of allowed headings includes Requirements and Qualifications. We could use Requirements for