Sr. Engagement Manager, Forward Deployed Engineering - Financial Services

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse posting. Content: - Title: CSQ227R220 The Senior Engagement Manager ... (job title). We should not repeat job title as heading. - The posting includes description: "The Senior Engagement Manager is a trusted advisor within the Forward Deployed Engineering organization to account teams and customers in the Financial Services sector for successful implementation and value realization. You will independently lead large, complex, cross-functional programs with minimal oversight, navigating ambiguous scenarios to drive significant impact on your assigned accounts." Then "The Impact You Will Have" with bullet points (actually sentences). Those are responsibilities. Then "What We Look For" with bullet list of qualifications. Then "Pay Range Transparency" with pay ranges. Then "About Databricks" description (company overview) – not required but could be part of About the role? Might be considered "About the role"? Actually "About Databricks" is company overview; we could include under "About the role"? But guidelines: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have: - About the role: maybe the initial paragraph describing role. - Responsibilities: The Impact You Will Have bullet points. - Requirements/Qualifications: What We Look For bullet points (7-10 years etc). Could be Requirements. - Skills: maybe not separate; could combine with Requirements. - Benefits: There's a Benefits section: "Benefits At Databricks, we strive to provide comprehensive benefits and perks..." but it's generic and refers to click here for specifics. It says "For specific details on the benefits offered in your region click here." That's not specific benefit details; it's generic. According to rule: do NOT create Benefits section unless posting actually states them. It does state benefits exist but not specifics. It says "For specific details on the benefits offered in your region click here." That's not substantive benefit details. Likely we should not include Benefits section because no concrete benefits listed. - Pay: Yes we have pay ranges with zones. So include Pay section. - Schedule: Not mentioned. - About Databricks: Could be considered "About the role"? Not exactly. Could be separate "About the company" but not in allowed headings. Probably we can omit or incorporate into About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exhaustive. But we should only include sections when posting has real, specific content. The "About Databricks" is company overview, could be considered "About the role"? Might be okay to include as "About the role" or maybe we can include a section "About Databricks" but not in list; but safer to include as "About the role" (the role description). However we already have an initial paragraph describing role; we could combine with About Databricks? Might be better to have "About the role" containing the initial paragraph and maybe the company overview? But the company overview is not about the role. However we could still include it under "About the role" as extra context; but risk of being irrelevant. The instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (initial paragraph), Responsibilities, Requirements, Pay. Possibly also Qualifications separate? But Requirements and Qualifications are similar; we could combine. Let's extract content precisely. About the role paragraph: "The Senior Engagement Manager is a trusted advisor within the Forward Deployed Engineering organization to account teams and customers in the Financial Services sector for successful implementation and value realization. You will independently lead large, complex, cross-functional programs with minimal oversight, navigating ambiguous scenarios to drive significant impact on your assigned accounts." That's it. Responsibilities (The Impact You Will Have): - Strategic Leadership: Independently scope and lead large, complex initiatives with multiple workstreams and diverse stakeholders. - Advanced Selling: Drive the full-cycle sales of standard and customized Professional Services & Training (PS&T) programs, pulling in best practices for Centers of Excellence (CoEs) and migrations. - Account Growth: Identify and pursue upsell and cross-sell opportunities within existing customers to meet or exceed revenue targets. - Cross-Functional Alignment: Partner with Sales and GTM teams to prioritize regional PS&T targets aligned with growth goals. - Customer Sentiment: Proactively monitor customer sentiment and take corrective actions or escalate to ensure high satisfaction. We need to format as

• each. What We Look For (Qualifications/Requirements): - 7-10 years running a Professional Services line of business. - 10+ years in senior customer-facing roles with a mix of influencing and execution. - Deep understanding of PS&T offerings, including Partner funding programs (Microsoft, AWS, Google). - Strong knowledge of Databricks architecture, competitors, and migration benefits. - Proven track record of managing large-scale program plans and service delivery. - Ability to travel up to 25-50% as required. We could put under Requirements or Qualifications. Since both headings allowed, we could choose Requirements (or Qualifications). Let's use Requirements. Pay section: Provide the pay ranges. We need to include the pay range text: "Pay Range Transparency Databricks is committed to fair and equitable compensation practices. The pay range(s) for this role is listed below and represents the expected base salary range for non-commissionable roles or on-target earnings for commissionable roles. Actual compensation packages are based on several factors that are unique to each candidate, including but not limited to job-related skills, depth of experience, relevant certifications and training, and specific work location. Based on the factors above, Databricks anticipated utilizing the full width of the range. The total compensation package for this position may also include eligibility for annual performance bonus, equity, and the benefits listed above. For more information regarding which range your location is in visit our page here. Zone 1 Pay Range $144,800—$199,100 USD Zone 2 Pay Range $130,300—$179,200 USD Zone 3 Pay Range $123,100—$169,300 USD Zone 4 Pay Range $115,800—$159,300 USD" We should preserve all substantive information. Could we condense? We must not invent or summarize away detail. We need to keep the info. Could present as

  with the explanatory text and then a

  for zones? The rule: Use
  • for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but could be presented as

    . However we could also use

    for pay ranges if we want, but not required. Safer to use

    for prose. We'll include the explanatory sentences as

    and then maybe a

    for zones? The zones are a list; could be
    . The rule says use
    • for any list of duties/requirements/benefits. Pay ranges are not exactly those categories, but still a list. It's okay to use
      for clarity. But we must not deviate from instruction? It says use
      • for any list of duties/requirements/benefits. It doesn't forbid using
        for other lists, but we could just use

        with line breaks. Simpler: put all in

        . We'll include the pay section heading

        Pay

        then a

        containing the pay transparency paragraph and the zones. We should not include Schedule (no content). Benefits: we have a Benefits section but it's vague; we should not include because no specific benefits listed. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits section exists but content is generic: "Benefits At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees. For specific details on the benefits offered in your region click here." That's not specific benefits; it's a statement that benefits exist but no detail. Likely we should not include Benefits section because no concrete benefits listed. So omit. About Databricks: Could be considered "About the role"? Not exactly. Might be okay to include as a separate section "About Databricks" but not in allowed headings. Safer to omit or incorporate into About the role? The initial paragraph already describes role; we could add a second paragraph about company under same heading? Might be okay to have About the role include both role description and company overview. But the instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role is a heading; we can put role description there. The company overview could be considered part of About the role? Not really, but we could still include it as extra context under same heading; it's not prohibited. However we must not invent or summarize away detail; we can include it as is. Thus About the role

        About the role

        then

        containing both paragraphs: the role description and the About Databricks paragraph. Let's extract About Databricks paragraph: "Databricks is the Data and AI company. More than 20,000 organizations worldwide — including adidas, AT&T, Bayer, Block, Mastercard, Rivian, Unilever, and 70% of the Fortune 500 — rely on the Databricks Data + AI Platform to build and scale data and AI apps, analytics and agents. Headquartered in San Francisco with 30+ offices around the globe, Databricks offers a unified platform that includes Genie, Lakebase, Agent Bricks, Lakeflow, Lakehouse, and Unity Catalog. To learn more, follow Databricks on LinkedIn, X, YouTube, and Instagram." We'll include that. Now ensure we removed boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We have removed those. Now produce HTML fragment. Structure:

        About the role

        ... role description ...

        ... About Databricks ...

        Responsibilities

        • Strategic Leadership: Independently scope and lead large, complex initiatives with multiple workstreams and diverse stakeholders.
        • Advanced Selling: Drive the full-cycle sales of standard and customized Professional Services & Training (PS&T) programs, pulling in best practices for Centers of Excellence (CoEs) and migrations.
        • Account Growth: Identify and pursue upsell and cross-sell opportunities within existing customers to meet or exceed revenue targets.
        • Cross-Functional Alignment: Partner with Sales and GTM teams to prioritize regional PS&T targets aligned with growth goals.
        • Customer Sentiment: Proactively monitor customer sentiment and take corrective actions or escalate to ensure high satisfaction.

        Requirements

        • 7-10 years running a Professional Services line of business.
        • 10+ years in senior customer-facing roles with a mix of influencing and execution.
        • Deep understanding of PS&T offerings, including Partner funding programs (Microsoft, AWS, Google).
        • Strong knowledge of Databricks architecture, competitors, and migration benefits.
        • Proven track record of managing large-scale program plans and service delivery.
        • Ability to travel up to 25-50% as required.

        Pay