Senior Technical Program Manager (Contract)

We need to output HTML fragment with sections: About Drivemode, About This Role, Responsibilities, What We Are Looking For (maybe as Requirements or Qualifications). Also include Pay? The posting includes "This is the position's hourly pay. Actual compensation packages are based on a wide array of factors..." It mentions pay but not a specific amount. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "This is the position's hourly pay." but no actual number. It says actual compensation packages based on factors. That's vague, not a specific figure. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a Pay section because no specific pay given. Benefits? Not mentioned. Schedule? Not mentioned. So we omit those sections. We need headings:

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections with real content. The posting has "About Drivemode", "About This Role", "Responsibilities", "What We Are Looking For". We need to map to allowed headings. "About Drivemode" could be considered "About the role"? Actually "About the role" is a generic heading. But we have "About Drivemode" (company overview) and "About This Role". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. So we can use other headings as long as they are

. Probably we should use headings that match content: About Drivemode, About This Role, Responsibilities, What We Are Looking For (maybe as Requirements or Qualifications). The "What We Are Looking For" is essentially qualifications/requirements. Could map to "Requirements" or "Qualifications". Since we have both responsibilities and qualifications, we can use "Requirements" heading for the qualifications list. But we also have a list of bullet points under "What We Are Looking For". That's appropriate for Requirements. Thus sections: About Drivemode, About This Role, Responsibilities, Requirements. We need to use

• for any list of duties/requirements/benefits. So responsibilities list should be
  • . Also the qualifications list should be
    • . Also maybe the "About Drivemode" and "About This Role" are prose, use

      . We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEOC statement, etc. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation/legal/EEO etc. So we need to strip the EEOC Statement paragraph at end. Also remove the line "This is the position's hourly pay. Actual compensation packages are based on a wide array of factors unique to each candidate, including but not limited to demonstrated skill set, years and depth of relevant experience, and some role-dependent factors. We welcome direct conversations with each candidate about compensation in all of our initial calls." This is pay info but vague; we should not create Pay section, but we might keep that sentence? It's about pay but not a specific amount. The rule says never emit a heading followed by filler/placeholder text. It doesn't say we must remove that sentence if not under a heading. However, we should preserve ALL substantive information. Is that substantive? It's about pay but vague. It might be considered filler. The instruction: "Prefer a few substantive sections over many thin ones." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The pay statement is not boilerplate but it's vague. Might be considered filler. I'd lean to keep it as a short paragraph under maybe a heading? But we cannot create Pay heading because no specific pay. Could we include it as a paragraph under About This Role? It mentions pay but it's not specific. Might be considered not substantive. Safer to omit it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit the pay statement, we are summarizing away detail (though it's vague). But it's not a concrete detail. Might be considered not substantive. I'd keep it as a short paragraph maybe under a generic "Compensation" but we cannot create Pay heading. Could we just include it as a

      without heading? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having

      outside headings. So we could include a paragraph about pay after the sections, without a heading. That would preserve the info. However, the instruction also says "Prefer a few substantive sections over many thin ones." Adding a stray paragraph might be okay. But maybe better to incorporate it into About This Role as a sentence. However, that would change the original text. Might be okay as we are not inventing, just repositioning. But we must preserve all substantive information; moving it is fine as long as we keep the content. So we could add a sentence about pay in the About This Role paragraph. Let's extract the substantive content: About Drivemode: "Drivemode is a California-based division of Honda Motor Co., Ltd. We are a small, passionate team of software product innovators helping Honda Automotive be competitive in the Hybrid and Electric Vehicle market. We build application experiences for mobile devices. Are you passionate about creating next-generation delightful digital experiences for automotive? Maybe you have worked at some notable automotive companies in this capacity? Would you like to work on new products and product categories at Honda and help Honda invent the future of automotive? Then we would like to hear from you! Why Drivemode: Join Drivemode for an exciting startup environment and a vibrant culture that combines impactful work, competitive compensation, and excellent benefits. By becoming a part of our team, you'll contribute to a crucial mission that revolutionizes the way people engage with vehicles, addressing both business needs and the world's environmental challenges. This presents an exceptional opportunity to be at the forefront of innovation and drive Honda's success in the Automotive market." About This Role: "Drivemode is seeking a Senior Technical Program Manager, Program Intelligence to lead a critical transformation initiative focused on how complex programs are understood, governed, measured, and improved. This is not a traditional program-coordination role. The Contractor will work across Product, Engineering, QA, Architecture, and TPM/PMO to establish durable systems that connect requirements, scope changes, technical execution, validation, program economics, and business outcomes. The mission: build the operating intelligence layer that helps Drivemode answer, feature by feature and program by program: What are we building? Why? What changed? What systems are affected? What did the change cost in capacity or schedule? How was it implemented and validated? What risk remains? What outcome did the investment produce? This is an initial six-month contractor engagement. Based on business need, demonstrated performance, and measurable outcomes, Drivemode may consider a mutually agreed extension of up to six additional months. If exceptional results are demonstrated and key outcomes are achieved ahead of or by the end of the engagement, Drivemode may also separately consider the individual for a full-time opportunity. Neither an extension nor employment is guaranteed; any future engagement would be subject to separate approvals and agreement." Responsibilities: list of bullet points (the long paragraph with line breaks). We need to turn each line into

      . The responsibilities block includes multiple sentences separated by line breaks. Let's capture each bullet: - Requirements Governance & End-to-End TraceabilityDesign and establish a scalable requirements-governance model covering ownership, baseline, lifecycle, versioning, approval, and change historyCreate clear relationships among business, product, system, technical, implementation, and validation artifacts - Change Request Management & Impact IntelligenceDesign and establish a structured Change Request (CR) operating model covering intake, classification, analysis, decision, approval, and closureConnect each material CR to affected requirements, features, services, APIs, dependencies, implementation scope, validation scope, and committed milestones - Internal Program Intelligence PlatformHelp define and evolve Drivemode’s internal Program Intelligence Platform from a traceability/reporting capability into a program-intelligence and decision-support systemConnect approved data across requirements, Change Requests, Jira, source control, validation systems, release information, program milestones, quality signals, and outcome metrics - AI-Enabled Program Intelligence & AutomationDesign and build purpose-built AI-enabled tools, agents, and analytical workflows that operate on approved program data and integrate with Drivemode’s internal systemsGo beyond general-purpose AI assistants for writing or summarization; use AI as an engineering capability for program intelligence - Technical Interface & Dependency TraceabilityImprove program-level visibility into APIs, services, mobile/backend interfaces, data flows, and external-system dependencies for priority GCA scopeConnect technical interfaces and dependencies to requirements, Change Requests, and implementation scope - Program Economics, KPIs & Decision SupportDevelop practical mechanisms for understanding where engineering and QA capacity is being consumed at the feature or initiative levelMeasure or estimate the impact of requirement churn, Change Requests, rework, defects, delivery variance, and scope growth We need to separate each bullet into

      . The text currently has no punctuation between the heading and the description; we should keep as is but maybe add a space. We'll keep the exact text but ensure readability. What We Are Looking For: list of bullet points: - 8+ years of relevant experience spanning technical program management, technical product management, solution architecture, software engineering, platform programs, or similar work - Strong technical fluency in backend/distributed systems, APIs, mobile/backend integration, and cross-system dependencies - Demonstrated ability to translate business or product intent into technical structures, execution plans, interfaces, and measurable outcomes - Hands-on experience building internal tools, automation, dashboards, or analytical systems using APIs and program data - Applied AI/agent experience is strongly preferred, especially building integrated workflows or services rather than only using general-purpose assistants - Strong systems thinking: ability to connect requirements, technical execution, validation, delivery, and business impact - Excellent judgment and communication across Product, Engineering, QA, Architecture, TPM/PMO, and senior leadership - Comfort operating autonomously in an ambiguous, fast-moving environment and leaving behind durable systems We need to map this to a heading. Could use "Requirements" or "Qualifications". Since it's about what we are looking for, "Requirements" fits. We'll use

      Requirements

      and then

      • ... . We also need to include the pay statement somewhere. Could add a

        after the sections: "This is the position's hourly pay. Actual compensation packages are based on a wide array of factors unique to each candidate, including but not limited to demonstrated skill set, years and depth of relevant experience, and some role-dependent factors. We welcome direct conversations with each candidate about compensation in all of our initial calls." But that is somewhat vague; still we preserve it. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft:

        About Drivemode

        ...

        About This Role

        ...

        Responsibilities

        • Requirements Governance & End-to-End TraceabilityDesign and establish a scalable requirements-governance model covering ownership, baseline, lifecycle, versioning, approval, and change historyCreate clear relationships among business, product, system, technical, implementation, and validation artifacts
        • Change Request Management & Impact IntelligenceDesign and establish a structured Change Request (CR) operating model covering intake, classification, analysis, decision, approval, and closureConnect each material CR to affected requirements, features, services, APIs, dependencies, implementation scope