Sr. 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 that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like cookie/navigation/legal/EEO etc. Must not include duplicated lines. Must not include sections with placeholder like "N/A". Must not create Pay/Schedule/Benefits unless posting actually states them. Here we have Pay Range Transparency with a range $219,100—$301,300 USD. So we can include Pay section. Benefits: there is a Benefits paragraph describing comprehensive benefits and perks, with link to details. So we can include Benefits section. Schedule: not mentioned. So no Schedule. We need sections: About the role (maybe from role snapshot? Actually there is "Role snapshot" but that's metadata; we can treat "About the role" as description of role. The posting includes a "Job Description" paragraph describing mission and role. So we can put that under About the role. Responsibilities: The "Impact You Will Have" bullet list (though not bullet but sentences). We can extract responsibilities as list items. Requirements/Qualifications/Skills: The "What We Look For" list includes experience, programming, etc. Could be Requirements. Also there is "Bachelor's degree..." etc. Could be Qualifications. We need to decide sections: maybe combine Requirements and Qualifications? But we need to follow instruction: use headings for those categories if content exists. We can split: Requirements (experience, programming, etc.) and Qualifications (education). Or Skills (programming languages). However we must not create thin sections. Let's see content: "What We Look For" bullet list: - 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 Thus we have experience, programming, etc. Could be Requirements. Education could be Qualifications. Travel maybe part of Requirements. We also have "Technologies PythonSQL" in role snapshot but that's minor. We also have "Compensation N/A" earlier but we have actual pay range later, so we ignore N/A. We need to avoid duplication: The "Role snapshot" repeated later; we ignore. We need to output only HTML fragment. Structure:

About the role

... (the job description paragraph(s) )

Responsibilities

• ... each responsibility from Impact You Will Have

Requirements

• ... items except education and maybe travel? We'll include all except Bachelor's degree and travel? Travel could be a requirement but we can include.

Qualifications

• Bachelor's degree in Computer Science, Information Systems, Engineering, or equivalent experience through work experience
• Can travel up to 30% when needed

Alternatively we could combine education and travel under Requirements and not have Qualifications. But we need to avoid thin sections. Having Qualifications with two items is okay. Benefits:

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.

Pay:

Pay

The pay range for this role is $219,100—$301,300 USD. 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 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.

We must not include boilerplate like "For more information regarding which range your location is in visit our page here." That's part of Pay Range Transparency; we could include that sentence but it's maybe boilerplate? It's still part of the posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The sentence about "For more information regarding which range your location is in visit our page here." is not exactly boilerplate but could be considered navigation? It's a link to internal page. Might be okay to keep? Safer to keep? The instruction says remove duplicated lines and application instructions. That sentence is not application instruction. It's about pay range location. I'd keep it as part of Pay section. But we already have a sentence about actual compensation etc. We could combine. Let's extract the Pay Range Transparency paragraph: "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 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 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 can keep that as a paragraph under Pay. Now Benefits paragraph: "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." plus maybe the "Our Commitment to Diversity and Inclusion" etc is EEO boilerplate, should be removed. Also "Compliance" paragraph about export-controlled technology is legal boilerplate, remove. Also "About Databricks" paragraph is company description; could be considered part of About the role? Might be extra but not required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The About Databricks paragraph is substantive but maybe not needed for role? It's about company. Could be included under About the role? But we already have About the role description. The instruction says prefer a few substantive sections over many thin ones. Including About Databricks might be extra but still substantive. However the heading "About the role" is for role description; company description could be separate but we don't have a heading for Company. Could we add a section "About Databricks"? Not in allowed headings list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not create other headings. So we should incorporate that info maybe under About the role as additional paragraph? But it's not about the role; it's about company. However we could still put it under About the role as extra context; it's not violating. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says use those for section headings. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; we could also use other headings? Probably safer to stick to those. So we can include company description under About the role as extra paragraph. Thus About the role will contain: the job description paragraph(s) plus the About Databricks paragraph. Now we need to ensure we don't include duplicated lines: The "Role snapshot" repeated later; we ignore. Now produce HTML. Let's craft:

About the role

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 Sr. 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 maximize 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 organization. You will report directly to a DSA Manager within the Field Engineering organization.

The Impact You Will Have: 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.

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