Jobs · Management · New York

Director, Martech Operations

GEICO · New York, NY · 1 mo ago
HybridManagementFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: "Why Join GEICO?" (intro), "Director, MarTech Operations Location: Hybrid — 3 days per week onsite at our NYC or Bethesda office. Reports To: Senior Director, Marketing Transformation & Operations". Then repeated intro paragraph. Then "Role Purpose". Then "Key Responsibilities". Then "Who You Are". Then "Qualifications". Then "Annual Salary $0.00 - $0.00" (but that is placeholder; we should not create Pay section if it's just placeholder? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states Annual Salary $0.00 - $0.00 but says it's a general guideline. It's still stating a salary range, albeit zero. It's still a statement. However they said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "$0.00 - $0.00". That is placeholder? Probably they intend it's not real. It's likely they want us to not create Pay section because it's placeholder zero. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "$0.00 - $0.00" is placeholder. So we should not create Pay section. Schedule: they gave location hybrid 3 days per week onsite. That's schedule info? It's location/hybrid schedule. Could be considered Schedule. The posting says "Location: Hybrid — 3 days per week onsite at our NYC or Bethesda office." That's schedule info. We could include a Schedule section with that content. However they said only include section when posting has real, specific content for it. It does have schedule: hybrid 3 days per week onsite. So we can include Schedule. Benefits: they mention GEICO Pledge with Great Rewards: Competitive pay, benefits, and flexibility. That's vague. Not specific benefits listed. So we should not create Benefits section because no specific benefits listed. Skills: not explicitly listed; maybe implied in Qualifications. We could skip Skills. About the role: we have Role Purpose paragraph. Could be About the role. Responsibilities: Key Responsibilities. Requirements: maybe Qualifications? They have Qualifications section. Could treat as Requirements. We need to use

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

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment. Let's extract content: Intro: "Why Join GEICO? At GEICO, we offer a rewarding career where your ambitions are met with endless possibilities. Every day we honor our iconic brand by offering quality coverage to millions of customers and being there when they need us most. We thrive on relentless innovation to exceed our customers' expectations while making a real impact on local communities nationwide. Founded in 1936, GEICO is a member of the Berkshire Hathaway family of companies and one of the largest auto insurers in the United States. When you join our company, we want you to feel valued, supported, and proud to work here. That's why we offer the GEICO Pledge: Great Company, Great Culture, Great Rewards, and Great Careers." Then repeated similar paragraph after location. We should not duplicate. We'll keep one version. Location line: "Location: Hybrid — 3 days per week onsite at our NYC or Bethesda office. Reports To: Senior Director, Marketing Transformation & Operations" Role Purpose paragraph: "The Director, MarTech Operations reimagines what technical program management looks like inside a marketing organization where the most important initiatives don’t arrive on an annual roadmap — they show up every week, often with no plan yet attached. This role is the delivery engine behind GEICO Marketing’s most important technical and data-driven programs: turning ambiguity into team design and clear delivery plans, partnering with the Marketing Systems Design and Technology teams on marketing use cases and roadmaps, and keeping a fast-moving portfolio of programs on track to their key dates. This is a builder’s role, not an administrator’s. We’re looking for someone who wants to reinvent program management itself — bringing the speed, tooling, and AI-native ways of working of a modern technology company into a complex enterprise environment, and creating the velocity marketing needs to keep pace with how fast AI and martech are moving." Key Responsibilities: multiple bullet-like paragraphs. We need to turn into

    • . Each bullet is a heading? The text includes headings like "Reimagining Technical Program Delivery", "Team Design & Program Momentum", "Program Planning & Systems Design Partnership", "Program Dependency & Portfolio Management", "Program Governance & Reporting". Under each there are sentences. We should preserve detail. Could treat each heading as a
    • with its content as

      inside? But instruction: Use

      • for any list of duties/requirements/benefits. So we can make each responsibility as
      • containing the description (maybe as

        ). We'll keep the heading inside

      • maybe as or just text. Who You Are: paragraph describing traits. Qualifications: list of bullet-like sentences. We'll make
        • . We also need to include Schedule section with location/hybrid info. We must not include Pay section. We must not include Benefits section (no specific). We must not include Skills section (none explicit). We need to ensure we don't repeat job title as heading. We need to output only HTML fragment. Let's craft:

          About the role

          Why Join GEICO? At GEICO, we offer a rewarding career where your ambitions are met with endless possibilities. Every day we honor our iconic brand by offering quality coverage to millions of customers and being there when they need us most. We thrive on relentless innovation to exceed our customers' expectations while making a real impact on local communities nationwide. Founded in 1936, GEICO is a member of the Berkshire Hathaway family of companies and one of the largest auto insurers in the United States. When you join our company, we want you to feel valued, supported, and proud to work here. That's why we offer the GEICO Pledge: Great Company, Great Culture, Great Rewards, and Great Careers.

          Location

          maybe Schedule? But they said use heading names like Schedule. We'll use

          Schedule

          and put location/hybrid info.

          Location: Hybrid — 3 days per week onsite at our NYC or Bethesda office. Reports To: Senior Director, Marketing Transformation & Operations

          Responsibilities

          • Reimagining Technical Program Delivery Build a new model for technical program management designed for a portfolio that changes weekly — where major AI, data, and martech initiatives emerge continuously rather than on a fixed annual cycle. Design the agile, high-velocity delivery system — rituals, tooling, and decision-making — that lets the organization move at the speed AI and martech are moving, not the speed of a traditional PMO. Treat the delivery model itself as something to continuously reinvent rather than a fixed process to administer, retiring what’s slow and scaling what creates velocity. Use AI tools and agents within program management itself to increase the speed and quality of planning, tracking, and reporting.
          • Team Design & Program Momentum Take ambiguous, newly-forming initiatives and quickly stand up the right team design — pulling together the right people, defining roles and ownership, and giving a gray-area project real shape. Create clarity of roles and decision rights within each program so teams know who owns what from day one. Build and sustain momentum across projects and teams — unblocking, re-energizing, and keeping cross-functional groups moving through ambiguity and change. Serve as the connective tissue for teams stood up quickly around emerging priorities, giving them structure without slowing them down.
          • Program Planning & Systems Design Partnership Partner deeply with the Marketing Systems Design and Technology teams to turn strategy into concrete project plans, marketing use cases, and delivery roadmaps. Own the project plan, not the technical architecture: translate what the business and systems design teams are building into milestones, sequencing, and delivery commitments. Keep every initiative optimizing toward key dates and roadmap commitments, flagging early when scope, sequencing, or resourcing puts a date at risk. Represent the marketing use case and business outcome in planning conversations with Systems Design and Technology, ensuring delivery plans reflect real marketing needs.
          • Program Dependency & Portfolio Management Manage the web of program-level dependencies across concurrent initiatives — sequencing, shared resources, overlapping teams, and competing priorities — rather than deep technical dependencies owned by engineering. Build and maintain a live view of the transformation portfolio: what’s in flight, what’s landing when, and where programs depend on each other. Identify and resolve cross-program conflicts before they become delivery risks, escalating only what truly needs executive attention.
          • Program Governance & Reporting Establish lightweight, high-velocity governance — steering touchpoints, milestone reviews, and executive reporting — that keeps sponsors aligned without slowing delivery down. Build reporting and dashboards that give leadership real-time visibility into portfolio health, key dates, and risk. Partner with the Change Management team to ensure new tools, processes, and ways of working land with real adoption, not just delivery.

          Who You Are

          An agile-native builder who reimagines how program management works rather than running the standard playbook. Deep in AI: fluent in how AI and modern martech are reshaping marketing, and energized by helping the organization move at that pace. Comfortable creating structure and team design out of ambiguity — thrives when a project shows up with no plan yet attached. A momentum-builder: rallies teams, keeps them moving, and translates energy into delivery. A fluent translator between business, marketing, and technical/systems design teams, without needing to own the technical architecture personally.

          Qualifications

          • Experience in a fast-moving technology or AI company (e.g., Google, OpenAI, or similar) leading program or project management for marketing- or product-adjacent initiatives; background in modern, high-velocity delivery environments is valued as much as traditional enterprise PMO experience.
          • Track record standing up and leading teams around ambiguous, fast-emerging initiatives, including team design and role clarity.
          • Deep fluency in AI and marketing technology, with experience evaluating and deploying new AI/martech tools quickly.
          • Experience building or reinventing program and project management ways of working, not just administering an existing methodology.
          • Strong program-level dependency and portfolio management skills across multiple concurrent, high-stakes initiatives.
          • Excellent stakeholder management; able to partner with systems design and engineering teams on delivery planning without owning technical architecture.
          • Excellent communicator, able to build momentum and confidence across technical and non-technical audiences alike.
          We should not include Pay, Benefits, Skills. Check for any leftover boilerplate: we removed EEO etc. We need to ensure we didn't include duplicated lines. We kept intro only once. Check that we didn't include "Annual Salary $0.00 - $0.00". Good. Check that we didn't include "The GEICO Pledge" repeated inside intro; we included it once.

Similar jobs