Databricks Architect
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from job description.
We have many sections: Role Purpose, Area of Responsibility, etc. We need to map to headings.
We should not repeat job title as heading. No Job ID.
We need to preserve all substantive info, no boilerplate.
We need to remove cookie/navigation/legal/EEO etc. So remove equal opportunity statements, etc.
We need to include sections only when posting has real specific content.
Let's parse content:
- Role Purpose: "The purpose of this role is to design solution architecture for cross-system interactions and business logic integration, ensuring seamless interoperability across multiple applications."
- Area of Responsibility: bullet list items: Requirement Analysis, Designing, Integration assessment and support, Troubleshooting, Risk Analysis and Assessment.
- Job Description: Databricks Architect - Drilling & Energy Domain Location - Tulsa, Onsite Experience- 12+ Years of IT Experience with 5+ Years in Databricks Architecture ... etc.
- Role Overview: description.
- Success Criteria: bullet list.
- Key Responsibilities: with subheadings Architecture & Technology Leadership, Business & Domain Engagement, Delivery & Governance, Leadership & Stakeholder Management, Technology Focus, Reporting To, Target Industry Experience.
- Required Qualifications: Technical Skills, Domain Expertise, Leadership Skills.
- Preferred Qualifications: list.
- Mandatory Skills: Databricks Experience: 8-10 Years
- Compensation: expected compensation range $80,000 to $158,000. Also mention benefits: Wipro's standard benefits including a full range of medical and dental benefits options, disability insurance, paid time off (inclusive of sick leave), other paid and unpaid leave options.
- Also mention drug screening etc (legal) - we should remove that as boilerplate? It's about post-offer drug screening; might be considered legal/EEO? Probably remove.
- Also equal opportunity statement - remove.
- Also "Reinvent your world..." etc - that's marketing fluff; maybe consider boilerplate? It's not specific to role; could be removed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The marketing fluff might be considered boilerplate? It's not legal but it's generic corporate marketing. Might be considered not substantive? Probably remove.
Thus we need to keep substantive info: role purpose, responsibilities, qualifications, skills, benefits, pay.
We need to decide headings: About the role (could combine role purpose and overview). Responsibilities (key responsibilities). Requirements (maybe mandatory skills). Qualifications (required qualifications). Skills (technical skills). Benefits (benefits). Pay (compensation). Schedule (maybe not present; location Tulsa, Onsite indicates schedule? Not explicit schedule; we might omit Schedule section if no specific schedule info.
We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive info; not invent.
Let's extract details:
Role Purpose: design solution architecture for cross-system interactions and business logic integration, ensuring seamless interoperability across multiple applications.
Area of Responsibility bullet list:
- Participate in requirement discussions with client stakeholders to define solution and implementation level needs based on business requirements.
- Create solution architecture designs to meet cross-system interactions and business logic integration requirements, ensuring system cohesion across multiple applications.
- Assess and evaluate interactions across multiple applications by evaluating implementation dependencies and integration requirements.
- Support validation of solution components during implementation and ensures the solution functions as designed.
- Assist in identifying potential risks by evaluating system performance of implemented architectural solutions, to ensure efficient system landscape.
Role Overview: We are seeking a highly experienced Databricks Architect with strong expertise in modern data platforms and a deep understanding of the Oil & Gas Drilling business. The ideal candidate will serve as a trusted advisor to business and technology stakeholders, driving data strategy, architecture, and solution delivery while enabling business transformation through data-driven insights. This role requires a combination of technical leadership, industry domain expertise, stakeholder management, and consulting skills to design and implement scalable data solutions aligned with business objectives.
Success Criteria bullet list:
- Bring industry best practices and architectural leadership to the engagement.
- Act as a strategic partner to business stakeholders.
- Drive scalable, secure, and future-ready data solutions.
- Accelerate business value realization through effective use of the Databricks platform.
- Improve collaboration between business and technology teams while ensuring successful solution adoption.
Key Responsibilities (with subheadings):
Architecture & Technology Leadership:
- Design and implement enterprise-scale data platforms using Databricks, Azure/AWS cloud technologies, and modern data architectures.
- Define end-to-end data architecture, data models, integration patterns, security, governance, and performance optimization strategies.
- Establish architectural standards, best practices, and implementation frameworks across projects.
- Lead modernization initiatives involving data lakes, lakehouse architecture, real-time analytics, AI/ML enablement, and cloud migration programs.
Business & Domain Engagement:
- Work directly with business stakeholders, drilling engineers, operations teams, and leadership to understand business challenges and translate them into technology solutions.
- Provide thought leadership on leveraging data and analytics to improve drilling performance, operational efficiency, asset utilization, and decision-making.
- Drive business workshops, solution reviews, and architecture discussions with customer leadership.
Delivery & Governance:
- Provide technical oversight throughout the solution lifecycle from discovery through deployment.
- Ensure compliance with enterprise architecture, security, data governance, and quality standards.
- Mentor engineering teams and provide technical guidance on Databricks implementations.
- Review solution designs and ensure adherence to best practices.
Leadership & Stakeholder Management:
- Act as a trusted advisor for business and IT stakeholders.
- Collaborate with project managers, product owners, data engineers, data scientists, and business users.
- Influence strategic decisions regarding data and analytics investments.
- Drive adoption of industry-leading practices and innovation.
Technology Focus: Azure Databricks, Azure Data Platform, Lakehouse Architecture, Advanced Analytics, AI/ML.
Reporting To: Account Delivery Leadership
Target Industry Experience: Oil & Gas, Drilling, Energy Services, Upstream Operations.
Required Qualifications:
Technical Skills:
- Strong expertise in Databricks Lakehouse Platform.
- Hands-on experience with: Apache Spark, Delta Lake, Unity Catalog, Databricks Workflows, MLflow, Structured Streaming.
- Strong experience with Azure Data Services and/or AWS Data Analytics services.
- Expertise in Data Warehousing, Data Lakes, ETL/ELT, Data Modeling, and Analytics platforms.
- Experience implementing scalable enterprise data architectures.
- Strong knowledge of SQL, Python, Spark, and cloud-native solutions.
Domain Expertise:
- Strong understanding of Oil & Gas Drilling Operations.
- Experience working with drilling, well planning, rig performance, production, operational analytics, and drilling data management.
- Ability to engage effectively with drilling business stakeholders and translate business needs into technical solutions.
Leadership Skills:
- Excellent stakeholder management and communication skills.
- Experience leading architecture discussions with senior business and technology leaders.
- Proven ability to influence decisions and drive consensus across teams.
- Strong mentoring and coaching capabilities.
Preferred Qualifications:
- Experience with Energy, Oil & Gas, or Drilling industry clients.
- Databricks Certified Professional Certification.
- Azure Solutions Architect / Data Engineer certification.
- Experience with AI/ML, Generative AI, and advanced analytics initiatives.
- Experience working in global delivery models.
Mandatory Skills: Databricks Experience: 8-10 Years
Compensation: The expected compensation for this role ranges from $80,000 to $158,000. Final compensation will depend on various factors, including your geographical location, minimum wage obligations, skills, and relevant experience.
Benefits: Based on the position, the role is also eligible for Wipro's standard benefits including a full range of medical and dental benefits options, disability insurance, paid time off (inclusive of sick leave), other paid and unpaid leave options.
We might also include location: Tulsa, Onsite. Could be part of About the role.
Schedule: Not specified; we should not create Schedule section.
Now produce HTML with headings for each section we include.
We need to decide which sections to include: About the role (combining role purpose, overview, location). Responsibilities (key responsibilities). Requirements (maybe mandatory skills + required qualifications?). Qualifications (required qualifications). Skills (technical skills). Benefits. Pay.
But we must avoid duplication. The instructions: Prefer a few substantive sections over many thin ones. So we could combine some.
We could have:
- About the role (role purpose, overview, location, target industry experience)
- Responsibilities (key responsibilities bullet list)
- Qualifications (required qualifications + preferred qualifications + mandatory skills)
- Skills (technical skills + domain expertise + leadership skills)
- Benefits
- Pay
But that may be many sections. Could combine Qualifications and Skills into Requirements? However headings list includes Requirements, Qualifications, Skills. We can use them as separate if we have content.
We need to include section only when posting has real specific content. We have content for all.
Thus we can output:
About the role
About the role
... role purpose, overview, location, target industry experience ...
Responsibilities
- ... list items ...
Requirements
... mandatory skills (Databricks Experience: 8-10 Years) ... maybe also required qualifications? But we have Qualifications heading. Better to follow the given headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll assign content accordingly. About the role: role purpose, overview, location, target industry experience. Responsibilities: key responsibilities (the bullet list under Architecture & Technology Leadership etc). Could also include area of responsibility bullet list? But that's similar. We'll combine. Requirements: mandatory skills (Databricks Experience: 8-10 Years) maybe also required qualifications? But we have Qualifications heading for required qualifications. Qualifications: required qualifications (technical skills, domain expertise, leadership skills) maybe also preferred qualifications? Could include both. Skills: maybe technical skills? But we already used technical skills in Qualifications. Could separate: Qualifications = required qualifications (including preferred?), Skills = technical skills? Might be redundant. Given instruction to prefer few substantive sections, maybe we combine Qualifications and Skills into one section called Qualifications. But we must use headings exactly as given if we include them. We could include only those headings we have content for, and skip others. Thus we could include: About the role, Responsibilities, Qualifications, Benefits, Pay. Skip Requirements, Skills, Schedule if no specific content. But we have mandatory skills (Databricks Experience: 8-10 Years) which could go under Qualifications. Thus:
About the role
... role purpose, overview, location, target industry experience ...
Responsibilities
- ... list of responsibilities ...
Qualifications
- ... required qualifications (technical skills, domain expertise, leadership skills) ... plus preferred qualifications and mandatory skills? Could be separate list items.
Benefits
... benefits ...
Pay
... compensation range ...
We should not include Schedule. Now we need to format lists properly. Let's craft About the role paragraph: "The purpose of this role is to design solution architecture for cross-system interactions and business logic integration, ensuring seamless interoperability across multiple applications. We are seeking a highly experienced Databricks Architect with strong expertise in modern data platforms and a deep understanding of the Oil & Gas Drilling business. The ideal candidate will serve as a trusted advisor to business and technology stakeholders, driving data strategy, architecture, and solution delivery while enabling business transformation through data-driven insights. This role requires a combination of technical leadership, industry domain expertise, stakeholder management