Sr Consultant - Technical lead

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. The posting includes: description about company (maybe About the role? Actually "About the role" could be the introductory paragraph about Vantive mission). Then "Key Responsibilities" list. Then "Required Qualifications" includes Education, Experience. Also there is a "We understand compensation..." paragraph about pay range. Then "US Benefits At Vantive" details benefits. No explicit Skills section separate; maybe we can include skills within Responsibilities or Qualifications. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content. We have: - About the role: The introductory paragraph describing Vantive mission and team. That's substantive. - Responsibilities: The "Key Responsibilities" bullet list (multiple paragraphs). Should be a

• . - Requirements: Could be "Required Qualifications" maybe split into Education and Experience. Could treat as Requirements (or Qualifications). The instruction includes both Requirements and Qualifications as possible headings. We need to decide: The posting has "Required Qualifications" with Education and Experience. That could be under Qualifications. Requirements maybe not separate. Could combine Education and Experience under Qualifications. Or we could have Requirements (maybe none) and Qualifications (Education + Experience). Since we should prefer few substantive sections over many thin ones, we could combine Education and Experience into Qualifications. Or we could have Requirements (maybe none) and skip. Better to have Qualifications section with Education and Experience subpoints? But we must use
  • for any list of duties/requirements/benefits. So under Qualifications we can have two sublists? Could just list items. - Skills: Not explicitly listed separate; maybe we could infer from responsibilities but better not to invent. So skip Skills section. - Benefits: The "US Benefits At Vantive" paragraph with details. That's substantive. - Pay: The compensation paragraph with salary range. That's substantive. - Schedule: Not mentioned. So skip. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading (page already shows it). Do not put Job ID/requisition numbers as headings (none present). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out the EEO paragraph, Reasonable Accommodation, Recruitment Fraud Notice, etc. Also remove the "For additional information regarding Vantive’s US Benefits, please speak with your recruiter or visit our Benefits site: Benefits | Vantive" maybe that's part of benefits but it's a referral; still it's substantive? It's a link to benefits site; maybe we keep it as part of benefits? It's not boilerplate; it's a reference. Might keep. We must not include the "Equal Employment Opportunity" etc. Also remove "Know Your Rights: Workplace Discrimination is Illegal Reasonable Accommodation ..." and "Recruitment Fraud Notice". Also remove "For questions about this, our pay philosophy, and available benefits, please speak to the recruiter if you decide to apply and are selected for an interview." That's application instruction; remove. Also remove "We understand compensation is an important factor as you consider the next step in your career..." Actually that's part of pay discussion; we need to keep the salary range but maybe we can keep the paragraph that includes the range but remove the invitation to speak to recruiter. The instruction says remove application instructions. The sentence about speaking to recruiter is application instruction; we should remove that. Keep the rest about pay range. Similarly for benefits: remove "For additional information regarding Vantive’s US Benefits, please speak with your recruiter or visit our Benefits site: Benefits | Vantive". That's also application instruction; remove. Now we need to format. Let's extract content. About the role: The introductory paragraph(s) before "Key Responsibilities". Let's copy: "Vantive is a vital organ therapy company on a mission to extend lives and expand possibilities for patients and care teams everywhere. For 70 years, our team has driven meaningful innovations in kidney care. As we build on our legacy, we are deepening our commitment to elevating the dialysis experience through digital solutions and advanced services, while looking beyond kidney care and investing in transforming vital organ therapies. Greater flexibility and efficiency in therapy administration for care teams, and longer, fuller lives for patients— that is what Vantive aspires to deliver. We believe Vantive will not only build our leadership in the kidney care space, it will also offer meaningful work to those who join us. At Vantive, you will become part of a community of people who are focused, courageous and don’t settle for the mediocre. Each of us is driven to help improve patients’ lives worldwide. Join us in advancing our mission to extend lives and expand possibilities." That's the About the role. Responsibilities: The bullet list under "Key Responsibilities". It includes several headings: Data Platform Leadership, Pipeline Development & ETL/ELT Engineering, Snowflake Engineering, Technical Delivery Leadership, Data Quality, Governance & Operations, Stakeholder Collaboration. Each has paragraphs. We need to turn into
    • items. Should we preserve the subheadings inside li? Probably each bullet can contain the heading as bold or just text. Since we cannot use markdown, we can include the heading as plain text inside li. We'll keep the content. We need to ensure we preserve all substantive information: each paragraph under each heading. Let's extract each: Data Platform Leadership: - Provide technical leadership for EDH, AWS S3 ingestion patterns, Snowflake, and enterprise data engineering delivery. - Own end-to-end technical design for data ingestion, transformation, orchestration, and curated data product delivery. - Establish reusable engineering standards, development patterns, naming conventions, code quality expectations, and operational best practices. - Lead technical design reviews and partner with architecture teams to ensure scalable, secure, and maintainable solutions. - Drive modernization toward domain-driven data architecture and trusted data products. Pipeline Development & ETL/ELT Engineering: - Design, develop, and maintain scalable ETL and ELT pipelines across batch, incremental, CDC, and file-based ingestion patterns. - Build and enhance pipelines from source systems into AWS S3 and downstream Snowflake layers. - Implement transformation logic, business rules, validations, enrichment, data harmonization, and audit controls. - Support common EDH layers and patterns such as collect, translate, curate, and Snowflake consumption layers. - Partner with application and BI teams to ensure data pipelines meet business reporting and analytics requirements. Snowflake Engineering: - Lead Snowflake development activities including schemas, tables, views, stages, tasks, stored procedures, streams, and secure data access patterns. - Optimize Snowflake performance, compute utilization, storage design, query execution, and cost efficiency. - Implement role-based access controls, data sharing patterns, security standards, and platform governance expectations. - Enable curated datasets and reusable data products for reporting, analytics, AI, and advanced analytics use cases. Technical Delivery Leadership: - Lead and mentor data engineers, consultants, and technical delivery teams across design, build, test, deployment, and production support. - Review technical designs, code, data models, and deployment packages to ensure quality and adherence to standards. - Manage technical dependencies across infrastructure, security, platform, application, and business teams. - Drive issue resolution, root-cause analysis, and operational readiness for production releases. - Provide hands-on technical guidance when complex pipeline, integration, performance, or data quality issues arise. Data Quality, Governance & Operations: - Implement data quality checks, reconciliation controls, observability, lineage, and monitoring across critical data pipelines. - Partner with data governance teams to support metadata, cataloging, ownership, access management, and compliance expectations. - Ensure pipelines are reliable, supportable, secure, and aligned with enterprise standards for privacy, security, and regulatory needs. - Create operational runbooks, support documentation, and transition materials for steady-state operations. Stakeholder Collaboration: - Translate business and product requirements into scalable technical solutions and delivery plans. - Collaborate with data architects, product owners, business SMEs, BI teams, AI/ML teams, and platform engineering groups. - Communicate complex technical topics clearly to both engineering teams and business stakeholders. - Proactively identify risks, dependencies, and design tradeoffs, and recommend practical options for resolution. Now Qualifications: Under "Required Qualifications". Contains Education and Experience. Education: - Bachelor's degree in Computer Science, Information Systems, Engineering, Data Analytics, or a related discipline. - Master's degree preferred. Experience: - 10+ years of experience in data engineering, ETL/ELT, data warehousing, or enterprise data platform development. - 5+ years of experience leading technical teams or enterprise-scale data delivery initiatives. - 5+ years of hands-on experience with Snowflake development, optimization, and secure data design. - Strong experience with AWS data services, especially S3-based data ingestion and processing patterns. - Proven experience designing pipelines for large-scale enterprise reporting, analytics, and data product use cases. We could combine into one list under Qualifications. Now Benefits: The paragraph under "US Benefits At Vantive". Let's extract: "This is where your well-being matters. Vantive offers comprehensive compensation and benefits packages for eligible roles. Our health and well-being benefits include medical, dental and vision coverage that start on day one, as well as insurance coverage for basic life, accident, short-term and long-term disability, and business travel accident insurance. Financial and retirement benefits include the Aon Pooled Employer Plan (“Aon PEP”), Vantive’s 401(k) retirement savings plan, to help you prepare for your future. The Aon PEP is designed to help improve retirement outcomes by providing retirement resources more efficiently. The plan offers a robust set of investment options, financial education, and a suite of resources to support your retirement goals. We also offer Flexible Spending Accounts, educational assistance programs, and time-off benefits such as paid holidays, paid time off ranging from 20 to 35 days based on length of service, family and medical leaves of absence, and paid parental leave. Additional benefits include commuting benefits, the Employee Discount Program, the Employee Assistance Program (EAP), and childcare benefits." We should remove the sentence about speaking to recruiter or visiting benefits site. So we stop before that. Now Pay: The paragraph under "We understand compensation is an important factor...". Keep the salary range description but remove the invitation to speak to recruiter. Let's extract: "We understand compensation is an important factor as you consider the next step in your career. At Vantive, we are committed to equitable pay for all employees, and we strive to be more transparent with our pay practices. The estimated base salary for this position is $152,000 - $190,000 annually. The estimated range is meant to reflect an anticipated salary range for the position. We may pay more or less than of the anticipated range based upon market data and other factors, all of which are subject to change. Individual pay is based upon location, skills and expertise, experience, and other relevant factors." We need to remove the sentence: "For questions about this, our pay philosophy, and available benefits, please speak to the recruiter if you decide to apply and are selected for an interview." So we stop before that. Now we need to output HTML fragment with

      headings and

      for prose,

      • for lists. We must not include any extra text outside HTML. Let's construct:

        About the role

        Vantive is a vital organ therapy company on a mission to extend lives and expand possibilities for patients and care teams everywhere. For 70 years, our team has driven meaningful innovations in kidney care. As we build on our legacy, we