Director, Marketing

We need to output HTML fragment with sections: About the role? Actually the posting includes "About ITradeNetwork" then "Job Summary", "Key Responsibilities", "Required", "Nice To Have", "Who You Are", "Why You Will Love Working Here", "Benefits", "Additional Requirements". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to appropriate headings. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. 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. Thus we need to decide which sections to include based on content. We have: - About ITradeNetwork (company description) – could be "About the role"? Actually "About the role" is typical heading for role description, but we have company description. Could use "About the role" for job summary? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content. We have: Job Summary: a paragraph describing role. Key Responsibilities: list of duties. Required: list of requirements (experience, etc.) Nice To Have: list of nice-to-have. Who You Are: traits (maybe Qualifications? Actually "Who You Are" could be "Qualifications" or "Skills". Might map to "Qualifications". Why You Will Love Working Here: benefits? Actually that's "Why You Will Love Working Here" includes benefits like competitive salary, medical, etc. That's benefits. Benefits: also listed under "Why You Will Love Working Here". There's also a separate "Benefits" bullet list? Actually after "Why You Will Love Working Here" they list benefits: Competitive salary packages, Comprehensive medical..., Flex PTO..., Paid parental leave..., 401(k) matching, Tuition reimbursement..., Great health & well-being benefits..., Benefits are only applicable to full-time employees... So that's benefits. Additional Requirements: Must be able to demonstrate lawful ability to work in the United States. Also there is EEO boilerplate which we should remove. We should not include Pay or Schedule sections unless explicitly stated. There's no explicit pay or schedule info. So we omit Pay and Schedule. We need to decide which headings to use: About the role (maybe job summary), Responsibilities (key responsibilities), Requirements (required qualifications), Qualifications (maybe nice to have or who you are), Skills (maybe not needed), Benefits (why you will love working here). Could also include "About the company" but not in list; but we could use "About the role" for job summary and maybe include company description as part of that? The instruction says use those headings as examples, not strict list; we can use other headings if needed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. So we can map: - About the role: Job Summary + maybe company description? Could include company description as part of About the role? Usually "About the role" is about the role, not company. But we have separate "About ITradeNetwork". Could we make a section "About the company"? Not in the list but maybe acceptable? The instruction says use those headings (e.g.) but not limited to them? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should stick to those. Thus we need to fit content into those headings. We have: - About the role: could contain job summary and maybe company description? But company description is about the company, not role. However we could still put it there as part of role context. Might be okay. - Responsibilities: Key Responsibilities list. - Requirements: Required list. - Qualifications: Nice To Have + Who You Are? Or maybe Qualifications for required? But we already used Requirements for required. Qualifications could be nice-to-have and personal traits. - Skills: maybe not needed; we could omit if no specific skill list beyond what's in requirements. - Benefits: Why You Will Love Working Here (benefits). - Pay: not present -> omit. - Schedule: not present -> omit. We must not create empty sections. Thus output:

  About the role

  ... (job summary + company description)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...
  (nice to have + who you are)

  Benefits

  • ...
  ...
  We need to preserve all substantive information. Let's extract. Company description paragraph: "About ITradeNetwork At iTradeNetwork, we provide advanced supply chain software and insights tailored to the food & beverage industry. Our mission is clear and ambitious: To feed the world. From the start, we’ve been dedicated to tackling the most pressing challenges within food and beverage supply chains, delivering innovative solutions and expert support that make a measurable impact. Our cutting-edge technology helps businesses streamline complex procurement and fulfillment processes, minimize food waste, optimize inventory, manage compliance risk, and scale profitably. We’re proud to serve an elite customer base, including 13 of the top 25 North American grocers, 8 of the top 10 foodservice distributors, and 8 of the top 10 global food and beverage manufacturers. Today, we're building an AI-first company — meaning AI isn't a feature we bolt on, it's the foundation for how we design products, make decisions, and ship software. Cerena is proof of that in action: powered by the most connected supply chain network in food and beverage, iTradeNetwork's Solution Suite replaces error-prone manual workflows with faster, smarter tools — driving real results for our customers, and ultimately, for the consumers who depend on them. iTradeNetwork's Leadership Principles iTradeNetwork’s purpose is to feed the world — and everything we do is guided by the principles below. Every team member is expected to embody and champion these principles across the organization. Bias for Action We value speed and avoid analysis paralysis. We develop conviction, make informed decisions quickly, and take calculated risks to maintain momentum — knowing that swift progress is essential for innovation and growth. Customer Obsession We work relentlessly to delight our customers. We work backward from their needs to solve pain points and create solutions that surprise and earn their loyalty. We obsess over customers, not competitors. Data & Metrics Driven We operate with facts, not opinions. We dive deep into data and use metrics to measure progress, ground every decision in rigorous analysis, and push for clarity and measurable outcomes. Raise the Bar We continuously push for improvement — in ourselves, our teams, and the company. We hire and develop exceptional talent, setting ever-higher standards that elevate performance and drive excellence. Operational Excellence Through Process We build lasting processes that optimize for efficiency. By developing, testing, and documenting each process, we create consistency and scale through automation, enabling continuous improvement across the business. Ownership Mindset We take responsibility for our work and aim for long-term success. We use resources wisely, stay accountable, and roll up our sleeves to get things done — no task is beneath us. Earn Trust We build trust through integrity, transparency, and mutual respect. We communicate openly, own our mistakes, listen actively, and remain open to feedback as an opportunity for growth." That's a lot. We need to preserve all substantive information. Should we include the leadership principles? Yes, they are substantive. So include them in About the role section. Job Summary paragraph: "We are seeking a Director of Marketing to build and lead a high-performing marketing organization that establishes iTradeNetwork as the clear market leader in food and beverage supply chain technology. This is a hands-on leadership role balanced evenly across three pillars: marketing strategy and brand leadership, demand generation (including account-based marketing for our top 100 accounts), and content marketing built in close partnership with Product. The role leads a team of five, directs contracted resources, and works cross-functionally with Sales, Solutions Engineering, and Customer Success to turn marketing into the company’s growth engine." We can combine that with company description. Now Responsibilities list: each bullet: - Develop and execute the overall marketing strategy, brand architecture, and market positioning to establish iTradeNetwork’s leadership position. - Shape and protect brand voice, visual identity, and messaging consistency across all channels, partnering with executive leadership to translate company strategy into a compelling narrative. - Lead the website strategy and social media presence as key assets for thought leadership, market engagement, and competitive differentiation. - Design and execute a full-funnel demand generation engine spanning email, paid media, webinars, events, and organic channels to drive pipeline growth. - Build and scale an Account-Based Marketing (ABM) program targeting top 100 strategic accounts in tight coordination with Enterprise Sales. - Own pipeline generation targets and marketing-sourced/influenced revenue metrics, optimizing channel mix and spend allocation based on ROI. - Manage marketing automation, lead scoring, and nurture workflows in partnership with RevOps, delivering regular performance analytics. - Partner with Product to translate product roadmaps, features, and capabilities into clear product marketing narratives across portfolio solutions (MarginIQ, Cerena, iTrace, OMS, AI solutions). - Oversee comprehensive content strategy and editorial calendar (blogs, white papers, case studies, collateral) directly aligned with demand generation and ABM initiatives. - Lead go-to-market execution for product launches and deliver sales enablement content in collaboration with Enterprise Sales and Solutions Engineering. Now Requirements list (Required): - 12+ years of progressive marketing experience, including 5+ years in a marketing leadership role within B2B SaaS, ideally in a network business model - Experience in positing and lead generation within the SMB, mid market and enterprise segments - Direct experience building or scaling an account-based marketing (ABM) program targeting enterprise or strategic accounts - Demonstrated success leading brand strategy, market positioning, and competitive differentiation for a B2B company - Strong content marketing background, with experience translating complex product capability into clear, compelling market-facing narrative - Experience managing and developing a team of 5+ marketers, plus external contractors or agencies - Fluency with marketing automation and CRM platforms (e.g., HubSpot, Marketo, Salesforce) and ABM tooling (e.g., 6sense, Demandbase) - Strong analytical orientation — comfortable owning pipeline, conversion, and ROI metrics and reporting to executive leadership - Excellent written and verbal communication skills; able to operate as a strategic partner to the CRO and executive team - Bachelor’s degree in Marketing, Business, Communications, or related field; MBA a plus Now Nice To Have list: - Experience in food and