Principal Systems Data Architect

We need to output only HTML fragment, with sections as per content. No markdown fences. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse posting: - Intro about Qorvo (company description) maybe "About the role"? Actually it's about company, not role. Could be "About the role" but we have no explicit role description aside from duties. Could treat company description as "About the role"? Might be okay but they said do NOT repeat job title as heading. The page already shows it. We can include a short paragraph about company as prose under maybe "About the role"? Or we could skip that heading and just put intro as

before any heading? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if we have content. We have duties (responsibilities). We have minimum requirements, alternative requirements (qualifications). We have hybrid work schedule info (schedule). No explicit pay or benefits. No skills separate (maybe we can include skills under responsibilities). We'll include sections: Responsibilities, Requirements (maybe combine minimum and alternative as Requirements), Schedule (Hybrid work). Possibly also "About the role" for company overview. We must preserve all substantive information, not invent. Remove boilerplate: EEO, visa sponsorship note? The visa sponsorship line "This position is not eligible for visa sponsorship by the Company." That's substantive? It's a condition, maybe keep under Requirements? Could be a note. But it's not a heading; we can include as a

under Requirements or separate note. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship might be considered legal? Not sure. It's a condition; maybe keep. But safer to keep as it's substantive about eligibility. However it's not EEO. I'd keep it. We must not include duplicated lines. There are repeated Hybrid Work Permitted lines multiple times; we should include only once. We need to preserve all substantive info: duties list, requirements details, alternative requirements, hybrid schedule. Let's extract: Company description: "Qorvo (Nasdaq: QRVO) supplies innovative semiconductor solutions that make a better world possible. We combine product and technology leadership, systems-level expertise and global manufacturing scale to quickly solve our customers' most complex technical challenges. Qorvo serves multiple high-growth segments of large global markets, including consumer electronics, smart home/IoT, automotive, EVs, battery-powered appliances, network infrastructure, healthcare and aerospace/defense. Visit www.qorvo.com to learn how our innovative team is helping connect, protect and power our planet." That's about company; could be under "About the role" or maybe we just put as a

before any heading. The instruction says use

for section headings (e.g. About the role...). It doesn't forbid having a paragraph before first heading. We'll include a

for company overview. Then duties: list of duties. We'll put under

Responsibilities

with

• items. Duties text: "Build end-to-end solutions in Databricks. Build various AI features. Participate in various design and solution discussions. Migrate ERP to Enterprise Data warehouse. Migrate the data from various legacy systems to Data warehouse. This includes working with: integrations between various technologies and upgrade ERPs; build end-to-end solutions in Databricks or Snowflake or similar Data Warehouse; migrate ERP to Enterprise Data warehouse; migrate the data from various legacy systems to Data warehouse to include working with MapReduce, Spark, or Airflow; ERP development and End to end integrations; and migration of data, build end to end pipelines, set up the design and framework. Additionally, will use business requirements to drive the design of data solutions/applications and technical architecture; provide overall project management and administration activities for the data engineering organization; work with other developers, designers, and architects to ensure data applications meet requirements and performance, data security, and analytics goals, and anticipate, identify, track, and resolve issues and risks affecting delivery." We need to break into list items. Could combine similar but preserve all info. We'll create list items each distinct duty. Let's parse: - Build end-to-end solutions in Databricks. - Build various AI features. - Participate in various design and solution discussions. - Migrate ERP to Enterprise Data warehouse. - Migrate the data from various legacy systems to Data warehouse. - Working with integrations between various technologies and upgrade ERPs. - Build end-to-end solutions in Databricks or Snowflake or similar Data Warehouse. - Migrate ERP to Enterprise Data warehouse (duplicate? but we keep maybe once) - Migrate the data from various legacy systems to Data warehouse to include working with MapReduce, Spark, or Airflow. - ERP development and End to end integrations. - Migration of data, build end to end pipelines, set up the design and framework. - Use business requirements to drive the design of data solutions/applications and technical architecture. - Provide overall project management and administration activities for the data engineering organization. - Work with other developers, designers, and architects to ensure data applications meet requirements and performance, data security, and analytics goals. - Anticipate, identify, track, and resolve issues and risks affecting delivery. We can deduplicate some duplicates: "Migrate ERP to Enterprise Data warehouse" appears twice; we can keep one. "Build end-to-end solutions in Databricks" and "Build end-to-end solutions in Databricks or Snowflake or similar Data Warehouse" similar; we can keep both as they add nuance. Might be okay. Now requirements: Minimum requirements: Bachelor’s degree in Computer Science, Computer Engineering, or Applied Computer Science, or related field and 12 years of work experience. Additionally, 5 years of experience stated herein to involve integrations between various technologies and upgrade ERPs. Further, 4 years of experience stated herein to involve: (1) build end-to-end solutions in Databricks or Snowflake or similar Data Warehouse; (2) migrate ERP to Enterprise Data warehouse; and (3) migrate the data from various legacy systems to Data warehouse to include working with MapReduce, Spark, or Airflow. Finally, 2 years of experience stated herein to involve: (a) ERP development and end to end integrations; and (b) migration of data, build end to end pipelines, set up the design and framework. Alternative requirements: In lieu of a Bachelor’s degree, employer will accept a Master’s degree in Computer Science, Computer Engineering, or Applied Computer Science, or related field and 10 years of work experience. Additionally, 5 years of experience stated herein to involve integrations between various technologies and upgrade ERPs. Further, 4 years of experience stated herein to involve: (1) build end-to-end solutions in Databricks or Snowflake or similar Data Warehouse; (2) migrate ERP to Enterprise Data warehouse; (3) migrate the data from various legacy systems to Data warehouse to include working with MapReduce, Spark, or Airflow. Finally, 2 years of experience stated herein to involve: (a) ERP development and end to end integrations; and (b) migration of data, build end to end pipelines, set up the design and framework. We can combine into a Requirements section with both minimum and alternative as bullet points or paragraphs. Schedule: Hybrid Work Permitted: 3 days in the office and 2 days work from home optional within a reasonable commuting distance from the office. We'll put under

  Schedule

  with a

  . We should not include Pay or Benefits sections as not present. We should not include Skills separate; maybe we can incorporate skills within responsibilities. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO statement, visa sponsorship? The visa sponsorship line maybe considered legal; but it's a condition. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is legal; maybe remove. However it's substantive about eligibility. I'd lean to remove as it's legal boilerplate. But it's not exactly EEO; still legal. Safer to remove. Also remove "MAKE A DIFFERENCE AT QORVO" and following paragraphs about culture? That's maybe boilerplate? It's promotional but could be considered substantive about company. Might be okay to keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture paragraph is not explicitly boilerplate; it's about company values. Might keep as part of About the role. But we already have company description; we could combine. Let's decide to include a short About the role paragraph combining company overview and culture. We'll output:

  Qorvo (Nasdaq: QRVO) supplies innovative semiconductor solutions that make a better world possible. We combine product and technology leadership, systems-level expertise and global manufacturing scale to quickly solve our customers' most complex technical challenges. Qorvo serves multiple high-growth segments of large global markets, including consumer electronics, smart home/IoT, automotive, EVs, battery-powered appliances, network infrastructure, healthcare and aerospace/defense. Visit www.qorvo.com to learn how our innovative team is helping connect, protect and power our planet. As a unified global team, we bring a commitment to excellence, growth and a passion for creating what's next.

  Then

  Responsibilities

  with
  list. Then

  Requirements

  with maybe two paragraphs: Minimum and Alternative. We could also split into Minimum Requirements and Alternative Requirements as separate headings? The instruction list includes Qualifications, Skills etc. Could use Requirements for both. We'll include a

  for minimum, then

  for alternative. Then

  Schedule

  with

  . Make sure no extra whitespace? It's fine. Now produce HTML fragment. Let's craft list items precisely. Responsibilities list: - Build end-to-end solutions in Databricks. - Build various AI features. - Participate in various design and solution discussions. - Migrate ERP to Enterprise Data warehouse. - Migrate data from various legacy systems to the data warehouse. - Work with integrations between various technologies and upgrade ERPs. - Build end-to-end solutions in Databricks, Snowflake, or similar data warehouse. - Migrate data from various legacy systems to the data warehouse using MapReduce, Spark, or Airflow. - Perform ERP development and end-to-end integrations. - Migrate data, build end-to-end pipelines, and set up the design and framework. - Use business requirements to drive the design of data solutions/applications and technical architecture. - Provide overall project management and administration activities for the data engineering organization. - Collaborate with developers, designers, and architects to ensure data applications meet requirements, performance, data security, and analytics goals. - Anticipate, identify, track, and resolve issues and risks affecting delivery. We need to preserve all info; we may have omitted some nuance like "provide overall project management and administration activities for the data engineering organization" we have. Now Requirements: Minimum:

  Minimum Requirements: Bachelor’s degree in Computer Science, Computer Engineering, or Applied Computer Science, or related field and 12 years of work experience. Additionally, 5 years of experience in integrations between various technologies and upgrade ERPs. Further, 4 years of experience in: (1) building end-to-end solutions in Databricks or Snowflake or similar data warehouse; (2) migrating ERP to an enterprise data warehouse; and (3) migrating data from various legacy systems to the data warehouse, including work with MapReduce, Spark, or Airflow. Finally, 2 years of experience in: (a) ERP development and end-to-end integrations