Director, Projects Business Development

We need to output HTML fragment with sections: About the role (but we should not repeat job title as heading; we have "About the Role" heading from posting). Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include: About the role (the description), Responsibilities (Key Responsibilities), Qualifications (Required and Preferred), maybe Benefits, Compensation (Pay). Also maybe "What Makes You Successful" and "Key Performance Indicators" could be part of responsibilities or separate? But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. We have: - About the Role: paragraph describing role. - Key Responsibilities: bullet list under subheadings: Business Growth & Opportunity Development, Customer & Industry Engagement, Pursuit & Capture Management, Commercial Leadership. Each subheading has bullet points. - Qualifications: Required (list) and Preferred (list). Also maybe "What Makes You Successful" could be considered Skills? But we have a Skills heading optional. Could include Skills as a section summarizing traits: strategic business developer, hunter mentality, etc. But we need to only include sections if posting has real specific content. The "What Makes You Successful" is a paragraph describing traits; could be placed under Skills or maybe under About the role? But we already have About the role. Could create a Skills section with bullet points of traits. - Key Performance Indicators: could be considered under Responsibilities or maybe a separate section like "Performance Metrics". Not in allowed headings list; but we could incorporate into Responsibilities or maybe omit if not needed. However we need to preserve ALL substantive information; we cannot drop KPIs. So we need to include them somewhere. Could create a section "Key Performance Indicators" but not in allowed headings list; but instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings; but we could also add other headings if needed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. We need to fit KPIs somewhere; maybe under Responsibilities as a subsection? Could add a

  under Responsibilities after the list. Or we could create a separate section "Key Performance Indicators" but that is not in the list; risk of being considered not following instruction. However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exhaustive. So we can add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So maybe we can combine KPIs into Responsibilities or Qualifications. Better: create a section "Key Performance Indicators" as its own

  . It's substantive. I'd lean to include it. Now Benefits: we have detailed benefits list. So include Benefits section. Pay: we have compensation range and bonus. So include Pay section. Schedule: not mentioned; we should not create Schedule section. Now we need to remove boilerplate: "How to Apply", "Drug Free Workplace", "Equal Opportunity Employer". Also remove "About Foss Maritime" maybe? That's company description; could be considered part of About the role? But we have "About Foss Maritime" at top; it's company overview. Should we keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive but not about the role. However the instruction about headings includes "About the role". The company overview could be placed under a heading like "About the Company" but not in allowed list. Could we drop it? It's not about the role; but it's substantive. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The company overview might be considered minor metadata? Not sure. Usually they'd want to keep it. But the instruction about sections: "include a section ONLY when the posting has real, specific content for it". The company overview is real content. But we don't have a heading for it in allowed list; we could use

  About Foss Maritime? Not in examples but could be okay. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are typical sections; but we could still add others. I'd keep it as a section maybe "About the Company". But to be safe, maybe we can incorporate it into a short

  under About the role? But that would mix company info with role description. Might be okay. Better to keep a section "About the Company" as

  . It's substantive. Now we need to output only HTML fragment. Structure:

  About the Company

  Foss Maritime is one of the most recognized and respected maritime brands in the U.S., combining a rich legacy with a forward-thinking approach to industry innovation. While deeply rooted in tradition, Foss is evolving at a fast pace, continuously setting new standards for operational excellence and sustainability. With operations spanning all U.S. coasts and global transportation projects, Foss is a leader in harbor and terminal towage, tug and barge transportation, and offshore energy solutions, including traditional energy and offshore wind projects. Our primary operations are on the U.S. West Coast, Alaska, and Hawaii. As part of the Saltchuk family of companies, Foss is a values-driven organization that takes pride in its exceptional team, commitment to safety, and dedication to customer success. With a culture built on integrity, innovation, and collaboration, Foss Maritime remains a trusted leader in the maritime industry.

  About the Role

  Foss Maritime is seeking an experienced and results-driven Director, Project Business Development to lead strategic growth initiatives across marine transportation, marine infrastructure, offshore energy, government, and industrial project markets. This role serves as a senior commercial leader responsible for identifying, pursuing, and securing complex, high-value projects throughout North America and select international markets. The successful candidate will build executive-level relationships, drive capture strategies, and position the company to win innovative and profitable marine solutions. The Director, Project Business Development will play a critical role in expanding our presence across offshore energy, government and defense, marine construction, infrastructure development, heavy lift transportation, dredging support, renewable energy, and industrial project sectors.

  Responsibilities

  • Business Growth & Opportunity Development
    • Identify, qualify, and pursue new business opportunities aligned with company growth objectives.
    • Develop and maintain a robust pipeline of strategic project opportunities.
    • Evaluate market trends, customer needs, and competitive dynamics to identify emerging opportunities.
    • Create and execute business development strategies that drive sustainable revenue growth.
  • Customer & Industry Engagement
    • Establish and maintain strong relationships with project owners, EPC contractors, engineering firms, government agencies, offshore developers, marine construction companies, and industrial operators.
    • Serve as a trusted advisor to customers by developing innovative transportation and project solutions.
    • Represent the company at industry conferences, trade associations, customer meetings, and networking events.
  • Pursuit & Capture Management
    • Lead capture planning, opportunity pursuit, negotiation strategy, and proposal development for major projects.
    • Coordinate responses to RFQs, RFPs, tenders, and negotiated opportunities.
    • Collaborate closely with Operations, Project Management, Finance, Legal, and Executive Leadership to develop competitive project solutions and commercial structures.
    • Support opportunities from initial identification through contract award and project implementation.
  • Commercial Leadership
    • Develop pricing and commercial strategies that balance risk and profitability.
    • Negotiate commercial and contractual terms with customers and partners.
    • Maintain accurate forecasting, CRM updates, and business performance reporting.
  We could flatten nested lists? The instruction: Use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists. But maybe better to keep flat list with each duty as a
  • . Could combine subheadings inside
  • using . That's okay. Alternatively we could make each responsibility as a
  • with sub-bullets as nested
    . That's fine. Now Qualifications:

    Qualifications

    Required

    • Bachelor's degree in Business, Engineering, Transportation, Maritime Studies, or a related field.
    • 10+ years of business development, commercial leadership, project sales, or related experience.
    • Demonstrated success securing large-scale, multimillion-dollar project contracts.
    • Proven experience leading complex pursuits from opportunity identification through contract award.
    • Strong negotiation, relationship management, and consultative selling skills.
    • Strong financial and commercial acumen, including project economics, pricing strategy, and contract structures.

    Preferred

    • Experience in one or more of the following industries is highly desirable:
    • Marine transportation
    • Offshore energy and offshore wind
    • Oil & gas and LNG
    • Marine construction and dredging support
    • Government and defense contracting
    • Infrastructure development
    • Heavy lift and specialized transportation projects
    But we have nested list inside
    • . Could flatten: just list each as separate
    • under Preferred. That's okay. Now Skills: we have "What Makes You Successful" paragraph. Could make a Skills section.

      Skills

      You are a strategic business developer with a strong hunter mentality who thrives on identifying new opportunities and building long-term customer partnerships. You are equally comfortable engaging with executives, negotiating complex contracts, and collaborating cross-functionally to deliver project success. You bring an entrepreneurial approach, strong commercial judgment, and a proven ability to turn relationships and