Director of Product

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Bobtail" and then description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have content about role (description), responsibilities (list), requirements/qualifications/skills (combined), benefits (list). No explicit Pay or Schedule. So we should not include Pay or Schedule sections. We need to use

for each section heading. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO etc. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation/legal etc. We need to include About Bobtail? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have "About Bobtail" description: mission, values. That could go under About the role? Or maybe we treat as About the role (company overview). We'll put that in About the role section. Responsibilities: list of responsibilities bullet points. Requirements/Qualifications/Skills: we have a list of desired qualifications/experience. Could split into Requirements (experience, years), Qualifications (education? none), Skills (specific skills). But we can combine into one section? The instruction says prefer a few substantive sections over many thin ones. So we could have Requirements and Qualifications combined? But we need to follow headings exactly? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; we include only those with real content. So we can include Requirements, Qualifications, Skills as separate if they have content. But we could also merge them into one section called Requirements (or Qualifications). However the instruction says "Prefer a few substantive sections over many thin ones." So better to combine similar items into one section, maybe "Requirements and Qualifications". But the heading must be exactly one of the listed examples? It 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 strict list. So we can use those headings. We could use "Requirements" to encompass experience, qualifications, skills. Or we could have separate Requirements and Skills if we have distinct content. Let's see content: we have experience requirements (8+ years, leading product, etc). Also we have "Strong technical fluency", "Highly analytical", "Bias toward shipping", etc. Those are skills. Also we have "Experience conducting product discovery, customer research, and market analysis." That's also experience/skill. Could split but might be thin. Better to have two sections: Requirements (experience, background) and Skills (specific abilities). Qualifications maybe not needed. We have Benefits list. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. We'll output HTML fragment. Need to preserve all substantive information: include mission, values, description of role, responsibilities bullet points, requirements bullet points, skills bullet points, benefits bullet points. We must not include boilerplate like "Creating a diverse and inclusive workplace is Bobtail's nucleus. We are an equal opportunity employer..." Remove that. Also remove duplicated lines. Let's extract content. About Bobtail paragraph: "As Director of Product, your mission is to build the premier product organization in supply chain: disciplined about what you build, iterative in how you build it, obsessed with the customer, and driven by data at every decision. About Bobtail Bobtail is dedicated to increasing happiness by eliminating inefficiencies in the supply chain. We envision a supply chain without friction, fraud, waste, and abuse where companies succeed based on the value they create. We work in a unique way at Bobtail, where we value teams over individuals and encourage experimentation and iteration to constantly improve. Teams are given flexibility in working towards a shared purpose and given the freedom to decide how they will accomplish their goals. If you are an out of the box thinker that takes a proactive approach in collaborating with others to solve problems and achieve your goals - we would love to talk to you. The things we value: MissionTeams over individualsCollaborationCommunicationIterationExperimentation and failing fastInitiative and solutions oriented approachDocumentationDataMental health and work life balanceDiversityTransparency" We need to format nicely. We'll put as prose. Responsibilities: list from "You will be responsible for:" then bullet points. Let's capture each responsibility: - Decide What to Build: Develop and maintain a product strategy that clearly connects product investment to the company's broader strategic and financial objectives. Look beyond incremental feature improvements to identify opportunities for meaningful product innovation. - Process around decision making: Create a disciplined process for gathering and evaluating ideas without allowing the product roadmap to become a collection of stakeholder requests. Ensure completed functionality solves the underlying customer or business problem rather than simply meeting documented requirements. - Decide What Not to Build: Exercise real judgment about scope. Establish clear criteria for when to build, continue investing in a new product, change direction, or discontinue an initiative. - Execute at a High Level: Partner closely with engineering - and with design, go-to-market, and senior leadership - to turn the roadmap into shipped product on a predictable cadence, not just a plan. - Defend the Business Case: Build and defend the revenue potential, development cost, and opportunity cost of each major roadmap bet to the CFO, so product decisions hold up under financial scrutiny, not just strategic conviction. - Own the outcome: Ensure new products have clearly understood operational, financial, regulatory, and risk requirements before launch. Measure product success based on business outcomes - not simply whether features were delivered. - Own the Product: Take full, unbounded ownership of Bobtail's product. There are no lanes here; if it touches the customer or the platform, it's yours to shape. - Obsess Over the Customer and the Product: Establish a disciplined process for identifying and evaluating new product opportunities. Spend meaningful time talking directly with customers rather than relying exclusively on feedback filtered through Sales or Operations. Develop a strong understanding of competitors and adjacent providers within transportation finance and fintech. Live inside the carrier's day-to-day and inside the product itself. We want someone who can't walk past something broken without wanting to fix it, and who knows the product as well as the people using it. - Evidence-Driven Decision Making: Build the muscle - data, customer research, experimentation - to validate bets before committing engineering resources, while being willing to move on conviction when the data is inherently thin. - Team Building: Hire and develop the product management function at Bobtail, defining process and hiring bar as the first dedicated product leader. - Market & Competitive Judgment: Track how freight-tech and fintech infrastructure are evolving, including AI-driven disruption and industry consolidation, and stress-test Bobtail's roadmap against it. That's many bullet points. Requirements: experience etc. From "You should apply if you have:" list. Let's extract: - 8+ years of experience in product management and strategy, including experience leading product at a company of comparable size and complexity. - A track record of setting product strategy from ambiguity and defending sequencing decisions with both data and judgment. - Experience in fintech, financial services, payments, lending, factoring, transportation technology, or another transaction-heavy financial environment strongly preferred. - Experience conducting product discovery, customer research, and market analysis. - Strong commercial instincts and the ability to evaluate product opportunities based on customer value and business economics. - Comfort with compliance and risk constraints (KYC/KYB, lending, payments) is a plus. - Experience building and leading a product team, including hiring the first few members of a function. - Strong technical fluency - you don't need to write code, but you should be able to work closely with engineering on architecture trade-offs and technical feasibility. - Highly analytical and data-driven, with strong pattern-recognition and problem-solving skills. - A bias toward shipping and iterating over long planning cycles. - Comfort operating at a founder-led, profitable company rather than a venture-subsidized one. - Strong communication and cross-functional leadership skills, including the ability to clearly communicate product strategy and trade-offs to senior leadership. - The discipline to say no - comfortable deferring or killing ideas that don't earn their place on the roadmap, even when they're compelling in isolation or popular internally. - Demonstrated ability to influence across functions and challenge senior stakeholders constructively. - Financial fluency - comfortable modeling and defending the revenue potential, development cost, and opportunity cost of a roadmap bet directly to the CFO and other finance stakeholders. - A track record of measuring product success based on customer and business outcomes. - An obsession with the customer and the product - you can't walk past something broken without wanting to fix it, and you know the product as well as the people using it, not just the roadmap slide. That's many. Skills: maybe we can separate some as skills: Strong technical fluency, Highly analytical and data-driven, Strong communication and cross-functional leadership skills, Financial fluency, etc. But we already have many overlapping. Given instruction to prefer few substantive sections, maybe we combine Requirements and Skills into one section "Requirements". But we already have a Responsibilities section. Could also have Qualifications (maybe none). Let's just have About the role, Responsibilities, Requirements (covering experience/qualifications/skills), Benefits. Thus we will not have separate Skills section. We need to ensure we don't include placeholder text like "commensurate with experience". Not present. Now format. We'll output:

  About the role

  ... (the about bobtail paragraph)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • Generous PTO
  • Monthly Mental Break Day
  • Parental leave
  • Comprehensive healthcare coverage
  • Life insurance
  • 401k with company match
  • Work from home (or wherever)
  Make sure to preserve all substantive information: include the values list? The "The things we value:" list is a string without commas. We should preserve that as part of About the role paragraph. Could format as a sentence. We need to remove duplicated lines: there may be duplicate sentences like "We want someone who can't walk past something broken without wanting to fix it, and who knows the product as well as the people using it." appears twice? Actually appears in responsibilities and also later in requirements. We should keep both occurrences as they are substantive but maybe duplicate? The instruction: remove duplicated lines. If identical lines appear multiple times, we should deduplicate. Let's check. The phrase appears in responsibilities under "Obsess Over the Customer and the Product:" and also in requirements under "An obsession with the customer and the product - you can't walk past something broken without wanting to fix it, and you know the product as well as the people using it, not just the roadmap slide." Slightly different: one includes "not just the roadmap slide." Not identical, so keep both. Check other duplicates: maybe "Experience conducting product discovery, customer research, and market analysis." appears both in responsibilities? Not exactly. In responsibilities we have "Establish a disciplined process for identifying and evaluating new product opportunities." Not same. Thus fine. Now produce HTML. Be careful to escape any HTML special characters? Not needed. Let's craft the About the role paragraph: "As Director of Product, your mission is to build the premier product organization in supply chain: disciplined about what you build, iterative in how you build it, obsessed with the customer, and driven by data at every decision. About Bobtail: