Delivery Solutions Architect - Digital Native Business

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 if posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like navigation, EEO, etc. Also remove duplicated lines, application instructions, etc. We need to parse the job posting content. Let's extract relevant sections. The posting includes: - Role snapshot: Compensation N/A, Location Remote Work from anywhere, Technologies PythonSQL (maybe Python, SQL). But we should not include Compensation N/A as a heading because it's not specific. Also "Compensation N/A" is placeholder; we should not create Pay section unless actual pay range is given. However later there is a Pay Range Transparency section with actual range: Local Pay Range $180,000—$247,500 USD. So we should include Pay section with that info. - About the role: The job description paragraphs: "At Databricks, we are on a mission..." etc. That's about the role. Could be "About the role" heading. - Responsibilities: The bullet list of impact items: "Engage with Solutions Architects..." etc. Those are responsibilities. Could be under Responsibilities. - Requirements/Qualifications/Skills: The "What We Look For" list includes experience, programming, etc. Could be split into Requirements and Skills. But we need to decide based on content. The list includes: 5+ years experience, programming experience in Python, SQL or Scala, experience in customer-facing pre-sales..., understanding of solution architecture..., understanding of how to attribute business value..., technical program or project management..., experience resolving complex escalation..., experience conducting open-ended discovery workshops..., track record of overachievement..., Bachelor's degree..., Can travel up to 30% when needed. These are qualifications/requirements. Could be under Requirements. Skills could be separate but we can combine. - Benefits: There's a Benefits section: "At Databricks, we strive to provide comprehensive benefits..." plus link. No specific benefits listed, just generic statement. The rule: do NOT create Benefits section unless posting actually states them. It says "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 generic. Should we include? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states benefits exist but not specifics. Likely we should not include Benefits section because no specific benefits listed. However there is a Benefits heading in the original; but we need to decide if it's considered stating them. It says "At Databricks, we strive to provide comprehensive benefits and perks that meet the needs of all of our employees." That's a statement but not enumerated. Might be considered stating benefits exist but not details. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not list them. I'd lean to not include Benefits section because it's not specific. However we could include a short paragraph under Benefits with the statement? The rule: "Prefer a few substantive sections over many thin ones." So maybe skip Benefits. - Pay: we have actual range, so include Pay section. - Schedule: Not mentioned besides travel up to 30% when needed. That's not schedule. No schedule info. So skip Schedule. - About Databricks: Could be "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add About Databricks as a heading; maybe incorporate into About the role? The "About Databricks" paragraph is more about company. Could be placed under About the role? Might be considered part of role description. But we could keep it as a paragraph under About the role or maybe under a separate section not allowed. Since only allowed headings are those, we should not create other headings. So we can incorporate that info into About the role paragraph. - Also there is "Role snapshot" repeated; we should drop metadata like Job ID etc. Not needed. - Also there is "Compensation N/A" in role snapshot; we ignore because we have actual pay later. - Also there is "Location Remote Work from anywhere" - we could include location info maybe under About the role? Not a heading. Could be a short paragraph under About the role: "Location: Remote (Work from anywhere)". But we need to preserve all substantive information. So we should include location somewhere. Since we cannot create a heading for Location (not allowed), we can put it in a paragraph under About the role or maybe under Responsibilities? Better under About the role as a short sentence. - Technologies PythonSQL: could be mentioned under Skills or Requirements. We'll include in Skills. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not repeat the job title as a heading. The title is "Delivery Solutions Architect - Digital Native Business". Not to be used. We must not include Job ID/requisition numbers. We must remove boilerplate: navigation, EEO, etc. The EEO paragraph at end: "Individuals looking for employment at Databricks are considered without regard to..." etc. That's boilerplate; remove. Also remove "Compliance" paragraph. Also remove "About Databricks" maybe we keep as part of About the role but not as heading. Also remove "Ready to apply? Review the details above and continue to the employer's site to start your application." etc. Also remove "← Back to job listings" etc. Also remove "Role snapshot" repeated. Now craft sections. Section 1: About the role (h3). Content: combine mission statement, role description, location, maybe technologies. Paragraph: "At Databricks, we are on a mission to empower our customers to solve the world's toughest data problems by utilizing 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. Location: Remote (Work from anywhere)." We could also mention technologies: Python, SQL (maybe Scala). Could add a sentence: "Required technologies include Python, SQL (and optionally Scala)." But we might put under Skills. Section 2: Responsibilities (h3). List the impact bullet points. We need to convert each bullet into

• . The bullet points: - 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 preserve the nested list under "Develop an execution plan...". So we can have a
• for that heading, then a nested
  for the subitems. We must keep the exact wording. Section 3: Requirements (or Qualifications/Skills). The "What We Look For" list. We could split into Requirements and Skills. But we have limited headings; we can use Requirements for experience/education, and Skills for technical skills like Python, SQL, Scala, etc. However the list includes both. Let's decide: Use Requirements for the experience/education/qualifications, and Skills for technical skills (Python, SQL, Scala). But the list also includes "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", etc. Those could be Requirements. We'll create Requirements (

  ) with a

  of items: - 5+ 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 - 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 Then Skills (

  ) with list: - Programming experience in Python, SQL or Scala Maybe also include "Understanding of solution architecture..." but that's more requirement. We could also include "Experience resolving complex and important escalation..." as requirement. Now Pay section (

  ) with paragraph: "Local Pay Range $180,000—$247,500 USD". Also maybe note that Databricks is committed to fair compensation etc. But we should preserve substantive info; we can include the paragraph about pay range transparency? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the Pay Range Transparency paragraph as well, but we must not create a heading for it besides Pay. The paragraph includes details about compensation practices. We can include that as a

  under Pay heading. Thus Pay section:

  Pay