Senior Manager, Marketing Technology

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes: Job Description (intro paragraph). Then sections: Responsibilities (with subsections). Then Qualifications (Required, Preferred). Then "What Success Looks Like" (maybe could be considered part of description but not a required heading). Then "Qualifications Disclaimer" (legal boilerplate, should be removed). Then "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's Pay and Benefits info. Then benefits list. Then other boilerplate about role acceptance, onboarding, About Us, EEO etc. We should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Qualifications Disclaimer" and "Range and benefit information provided..."? Actually that is Pay and Benefits info, we should keep Pay and Benefits sections. The benefits list is substantive. So we need a Benefits section with list. Pay section with the salary range. Schedule? Not mentioned. So we should not include Schedule heading. About the role? The intro paragraph could be considered About the role. The posting starts with "Job Description This leader owns..." That's basically about the role. So we can put that in an

About the role

with a

. Then Responsibilities section with

Responsibilities

and then maybe subheadings? The instructions say use

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

but likely we should stick to

for main sections and use

and

• for content. Within Responsibilities, there are bullet-like paragraphs each starting with a bold heading. We could keep them as

  with strong? But we should preserve content. Probably we can keep each responsibility as a

  with the heading bolded via . However we must not invent formatting beyond HTML; we can use . That's okay. Similarly Qualifications: we have Required and Preferred. Could combine into Qualifications section with subpoints. Use

  Qualifications

  then maybe

  Required:

  then
  • ... etc. But we must not create extra headings beyond allowed list? The instruction says use

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

    or

    with strong. Safer to just use

    for main sections and within them use

    and

    • . For Required and Preferred we can treat as

      Required:

      then
      etc. Skills section: not explicitly present; we could omit if no specific skills list beyond qualifications. The qualifications include skills; but we could put them under Qualifications. No separate Skills heading. Benefits: we have list. Use

      Benefits

      then
      • each benefit. Pay:

        Pay

        then

        with salary range and bonus etc. We must not include sections like Requirements (maybe not needed). The posting has "Qualifications" but not separate "Requirements". So we omit Requirements heading. We must not include "About Us" etc. Remove boilerplate. We must preserve all substantive information. Let's extract. Intro paragraph: "This leader owns the technical execution of a portfolio of marketing applications, shared services, integrations, automation, and data-enabled capabilities. The role sits at the intersection of marketing, product, data, and engineering and is responsible for translating business problems into scalable technical solutions rather than simply administering individual marketing platforms. The Senior Manager leads both people and technology: establishing engineering practices, guiding solution architecture, developing technical talent, managing the application roadmap, and ensuring the team's products are secure, reliable, interoperable, measurable, and maintainable." That's About the role. Responsibilities: we have several subsections: Technology Leadership & Strategy, Application & Platform Ownership, Engineering Leadership, Data, Integration & Automation, AI & Emerging Technology, Security, Governance & Reliability, Business Partnership. We need to preserve all bullet points under each. Let's capture each. Technology Leadership & Strategy: - Lead the MarTech engineering function and establish the technical strategy for internally developed marketing applications, integrations, automation, and shared services. - Translate marketing and demand-generation requirements into scalable application, data, integration, and workflow architectures. - Partner with business and technology leaders to determine when capabilities should be built, integrated, extended, automated, or retired. - Drive a modular architecture that enables common capabilities and data to be reused across applications rather than repeatedly implemented within individual tools. - Establish technical standards for application development, APIs, integrations, data models, identity and access, observability, release management, and documentation. - Maintain a pragmatic technical roadmap balancing business value, platform sustainability, technical debt, security, and engineering capacity. Application & Platform Ownership: - Provide technical leadership for marketing applications and operational platforms supporting demand planning, campaign execution, program and event management, customer engagement, nominations, account intelligence, workflow, reporting, and automation. - Guide the evolution of applications from isolated tools toward interoperable services and shared platform capabilities. - Ensure common business entities, including accounts, contacts, programs, events, campaigns, opportunities, users, and marketing activities, are consistently represented and reusable across systems. - Lead integration with enterprise systems and data sources including CRM, account and contact data, commercial pipeline, financial data, analytics platforms, and identity services. - Establish appropriate system-of-record boundaries and controlled read/write integration patterns. - Oversee production reliability, application lifecycle management, upgrades, technical debt remediation, and operational support. Engineering Leadership: - Recruit, develop, mentor, and manage a high-performing team of MarTech engineers. - Provide technical direction while maintaining enough technical depth to review architecture, challenge design decisions, and unblock complex engineering problems. - Establish development practices covering source control, testing, code review, deployment, monitoring, incident management, and documentation. - Improve engineering velocity through reusable patterns, frameworks, shared services, and automation. - Establish clear ownership across applications, services, integrations, and data products. - Drive disciplined prioritization and prevent one-off solutions from creating unnecessary application or integration sprawl. Data, Integration & Automation: - Lead design of reliable integrations between marketing systems and enterprise platforms. - Drive API-first and reusable integration patterns where appropriate rather than point-to-point solutions. - Partner with data teams to establish canonical objects, source mappings, identity resolution, and trustworthy data flows. - Implement automation that removes manual reconciliation, duplicate data entry, spreadsheet coordination, and unnecessary human handoffs. - Ensure integrations include appropriate validation, monitoring, failure handling, lineage, ownership, and auditability. - Support the creation of governed data services that can be reused across operational applications, reporting, analytics, and AI. AI & Emerging Technology: - Identify practical opportunities to apply AI to marketing operations, application experiences, workflow automation, decision support, and engineering productivity. - Establish patterns for permission-aware and evidence-grounded AI capabilities rather than disconnected AI experiments. - Partner with security, data, and governance teams to ensure AI solutions operate within appropriate data-access and audit controls. - Evaluate emerging technology based on measurable business value, maintainability, interoperability, and risk. Security, Governance & Reliability: - Partner with security and identity teams to implement enterprise authentication, authorization, role-based and attribute-based access, service identities, and audit controls. - Ensure applications appropriately protect customer, employee, commercial, and financial information. - Establish technical governance without creating unnecessary delivery bureaucracy. - Ensure systems include production monitoring, integration health, data freshness, error detection, and support runbooks. - Maintain clear technical documentation and architectural decision records. Business Partnership: - Serve as the senior technical partner to marketing operations, campaign services, field marketing, analytics, business architecture, and related organizations. - Translate ambiguous business problems into structured technical requirements and solution options. - Challenge requirements where simpler, reusable, or more sustainable solutions exist. - Communicate technical tradeoffs clearly to both engineering and non-technical audiences. - Partner with product and business owners to define measurable outcomes and adoption expectations for technology investments. Qualifications: Required: - 8+ years of experience in software engineering, enterprise applications, marketing technology, data platforms, or related technical disciplines. - 3+ years leading engineers or technical teams. - Demonstrated experience designing and delivering enterprise applications or platforms used by business teams. - Strong understanding of application architecture, relational data modeling, APIs, system integration, workflow automation, and software development lifecycle practices. - Experience integrating enterprise SaaS, CRM, database, analytics, and internally developed applications. - Experience managing production systems and balancing feature development with reliability, maintainability, and technical debt. - Ability to evaluate architecture and implementation decisions at meaningful technical depth. - Strong written and verbal communication skills with both technical teams and senior business stakeholders. Preferred: - Experience supporting marketing, demand generation, sales, customer engagement, or revenue operations environments. - Experience with Oracle Database, SQL, PL/SQL, Oracle APEX, JavaScript/TypeScript, Python, or comparable enterprise application technologies. - Experience with cloud services, integration platforms, API gateways, event-driven architectures, and modern data platforms. - Experience implementing enterprise identity, RBAC/ABAC, audit, and security patterns. - Experience applying generative AI, retrieval, intelligent automation, or machine-learning capabilities within enterprise workflows. - Experience establishing development standards and modernizing internally developed applications. What Success Looks Like: This is descriptive but not a required heading; we could include as part of About the role or maybe as a separate section? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This section has substantive content. However the allowed headings list does not include "What Success Looks Like". We could incorporate that content into About the role or Responsibilities? It's more about outcomes. Could be placed under About the role as additional paragraph. Probably safe to add as a paragraph under About the role after the intro. Or we could create a custom heading but that might violate instruction to use only those headings? 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 exclusive list. But safer to stick to those. We can embed the success paragraph inside About the role. Pay: we have "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." Also later: "Oracle maintains broad salary ranges..." but that's boilerplate; we should keep the range and bonus info. The rest about broad ranges maybe boilerplate; we can drop. We'll keep the specific range and bonus eligibility. Benefits: list includes many items. We'll capture all. We must remove boilerplate like "Qualifications Disclaimer", "The role will generally accept applications...", "As part of Oracle's onboarding process...", "About Us", "True innovation starts...", "We also encourage...", "We’re committed to including people with disabilities...", "Oracle is an Equal Employment Opportunity Employer..." etc. Now construct HTML. Structure:

        About the role

        Intro paragraph + maybe success paragraph.

        We need to include success paragraph: "MarTech applications operate as an increasingly coherent technology ecosystem rather than independent tools