Delivery Solutions Architect - Financial Services

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: description of role (impact, etc.) could be "About the role" or "Responsibilities". There's a "What We Look For" which is requirements/qualifications/skills. There's "Pay Range Transparency" with pay range. There's "Benefits" section. There's no explicit schedule. There's no explicit "Skills" separate but could be part of requirements. We'll create sections: About the role (summary), Responsibilities (impact bullet list), Requirements (experience, education), Qualifications (maybe combine), Skills (programming languages etc.), Benefits, Pay. Avoid duplicate. Ensure we don't include boilerplate like EEO, compliance, etc. Remove cookie/navigation etc. Also remove Job ID line at top "CSQ427R299". Also remove "About Databricks" maybe not needed? It's about company but could be considered "About the role"? Probably not needed as it's generic company description; but we might keep as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The "About Databricks" is substantive but not role-specific; still we could include as a separate section? Not in allowed headings list. Could we add a section like "About Databricks"? Not allowed headings list only those specific. So we should not create a heading not in list. Could we fold that info into a paragraph under About the role? Might be okay but it's not role-specific. However instruction: "Prefer a few substantive sections over many thin ones." Might be okay to include as a paragraph under About the role. But we need to preserve all substantive info; we can include it as a paragraph under About the role. We must not include "Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So drop the CSQ line. We must not include application instructions, EEO, etc. We need to use

for section headings. Use

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

  for prose. We need to output only HTML fragment. Let's extract content. About the role: first paragraph: "At Databricks, we are on a mission to empower our customers to solve the world's toughest data problems by utilizing the the Databricks Data Intelligence Platform. As a Delivery Solutions Architect (DSA), you will play an important role during this journey. You will collaborate with our sales and field engineering teams to accelerate the adoption and growth of the Databricks platform in your customers. You will also help ensure customer success by increasing focus and technical accountability to our most complex customers who need guidance to accelerate usage on Databricks workloads that they have already selected, helping them maximise the value they get of our platform and the return on investment. This is a hybrid technical and commercial role. It is commercial in the sense that you will drive growth in your assigned customers and use cases through leading your customers' stakeholders, building executive relationships, orchestration of other focused/specialized teams within Databricks, and creating and driving plans and strategies for Databricks colleagues to build upon. This is in parallel to being technical, with expectations being that you become the post-sale technical lead across all Databricks products. This requires you to use your skills and technical credibility to engage and communicate at all levels with an organisation. You will report directly to a DSA Manager within the Field Engineering organization." That's prose. Responsibilities: The "Impact You Will Have" bullet list. List items: - Engage with Solutions Architects to understand the full use case demand plan for prioritised customers - Lead the post-technical win technical account strategy and execution plan for the majority of Databricks use cases within our most strategic accounts - Be the accountable technical leader assigned to specific use cases and customer(s) across multiple selling teams and internal stakeholders, creating certainty from uncertainty and driving onboarding, enablement, success, go-live and healthy consumption of the workloads where the customer has made the decision to consume Databricks - Be the first contact for any technical issues or questions related to production/go live status of agreed upon use cases within an account, oftentimes services multiple use cases within the largest and most complex organizations - Leverage both Shared Services, User Education, Onboarding/Technical Services and Support resources, along with escalating to expert level technical experts to build the right tasks that are beyond your scope of activities or expertise - Create, own and execute a point-of-view as to how key use cases can be accelerated into production, coordinating with Professional Services (PS) resources on the delivery of PS Engagement proposals - Navigate Databricks Product and Engineering teams for new product Innovations, private previews and upgrade needs - Develop an execution plan that covers all activities of all customer-facing technical roles and teams to cover the below work streams: - Main use cases moving from ‘win’ to production - Enablement / user growth plan - Product adoption (strategy and activities to increase adoption of Databricks’ Lakehouse vision) - Organic needs for current investment (e.g. cloud cost control, tuning & optimization) - Executive and operational governance - Provide internal and external updates - KPI reporting on the status of usage and customer health, covering investment status, important risks, product adoption and use case progression - to your Technical GM We need to format as

  • . For nested list under "Develop an execution plan..." we can have sublist. Requirements/Qualifications/Skills: "What We Look For" list. Items: - 7+ years of experience where you have been accountable for technical project / program delivery within the domain of Data and AI and where you can contribute to technical debate and design choices with customers - Programming experience in Python, SQL or Scala - Experience in a customer-facing pre-sales, technical architecture, customer success, or consulting role - Understanding of solution architecture related distributed data systems - Understanding of how to attribute business value and outcomes to specific project deliverables - Technical program, or project management including account, stakeholder and resource management accountability - Experience resolving complex and important escalation with senior customer executives - Experience conducting open-ended discovery workshops, creating strategic roadmaps, conducting business analysis and managing delivery of complex programmes/projects - Track record of overachievement against quota, Goals or similar objective targets - Bachelor's degree in Computer Science, Information Systems, Engineering, or equivalent experience through work experience - Can travel up to 30% when needed We could split into Requirements (experience, education) and Skills (programming languages, etc.) but we can combine into one section "Requirements". However we need to follow allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put experience/education under Requirements, and technical skills under Skills. But we have limited time; we can put all under Requirements and omit Qualifications/Skills if not needed? But we must include sections only when posting has real specific content for it. If we put all under Requirements, we still have content for Requirements; we can omit Qualifications and Skills sections (since they'd be empty). That's acceptable. Benefits: There's a Benefits section: "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 vague; not specific benefits listed. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The Benefits section is present but contains no specific benefits; it's generic. Should we include? It says "never create Benefits sections unless the posting actually states them." It does state a Benefits section but with no specifics; it's basically a placeholder. Likely we should omit Benefits section because it's not substantive. However there is also a line "For specific details on the benefits offered in your region click here." That's not substantive. So we should omit Benefits. Pay: There's Pay Range Transparency with specific range: $180,000—$247,500 USD. Also mentions total compensation may include bonus, equity, benefits. That's substantive. So we include Pay section. Schedule: No mention of schedule/hours. So omit. Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), Pay (h3). Possibly also Skills? But we can incorporate programming experience into Requirements. We need to ensure we don't repeat job title as heading. Not using. Now produce HTML. Structure:

    About the role

    ... (the paragraph)

    Responsibilities

    • ...
    ...
    Need to handle nested list for execution plan work streams. We'll have a
  • for "Develop an execution plan that covers all activities of all customer-facing technical roles and teams to cover the below work streams:" then a
    inside. Similarly for other items. Make sure to escape any apostrophes? Not needed. Now Requirements:

    Requirements

    • 7+ years of experience where you have been accountable for technical project / program delivery within the domain of Data and AI and where you can contribute to technical debate and design choices with customers
    • Programming experience in Python, SQL or Scala
    • Experience in a customer-facing pre-sales, technical architecture, customer success, or consulting role
    • Understanding of solution architecture related distributed data systems
    • Understanding of how to attribute business value and outcomes to specific project deliverables
    • Technical program, or project management including account, stakeholder and resource management accountability
    • Experience resolving complex and important escalation with senior customer executives
    • Experience conducting open-ended discovery workshops, creating strategic roadmaps, conducting business analysis and managing delivery of complex programmes/projects
    • Track record of overachievement against quota, Goals or similar objective targets
    • Bachelor's degree in Computer Science, Information Systems, Engineering, or equivalent experience through work experience
    • Can travel up to 30% when needed
    Pay:

    Pay

    The pay range for this role is $180,000—$247,500 USD. Total compensation may also include eligibility for annual performance bonus, equity, and benefits.

    We should not include the boilerplate about "Based on the factors above..." etc. That's somewhat generic but still substantive? It's more detail about compensation determination. Could include as paragraph. But we must avoid filler. It's not filler; it's explanation. Could include. However we need to preserve ALL substantive information. The posting includes: "Based on the factors above, Databricks anticipates 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." That's substantive. We'll include that as a paragraph after the range. Thus Pay section:

    Pay

    The pay range for this role is $180,000—$247,500 USD. Based on the factors above, Databricks anticipates 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.

    We must not include the link text "visit our page here" as it's generic but okay. Now ensure we didn't include any boilerplate