Manager, Data Architect (Remote)
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Title: Manager, Workforce Intelligence (Data Architect) RTX is seeking...
- What You Will Do: list of responsibilities (design and maintain scalable HR data architecture in Snowflake, etc.)
- Qualifications You Must Have: bullet list (actually sentences). Then "Qualifications We Prefer": bullet list.
- This Position Is Classified As Remote: description.
- As part of our commitment... (hiring process) maybe not needed? It's about interview process; could be considered boilerplate? It's not EEO but still maybe not needed? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The interview process details might be considered application instructions? Possibly remove. But we need to preserve substantive information. The remote classification and salary range and benefits are substantive. The interview process details maybe not needed. The EEO statement definitely remove. The "This role is a U.S.-based role..." maybe keep? It's about location; could be considered part of role description. Might keep as prose.
- Salary range: "The salary range for this role is 107,500 USD - 204,500 USD." That's Pay.
- Benefits: list of benefits.
- Application window closing approx 40 days... maybe not needed? It's about application process; could be considered application instructions; maybe remove.
- EEO statement remove.
Thus sections:
- About the role: maybe a short paragraph summarizing role? The posting includes "What You Will Do" which is responsibilities. Could treat "About the role" as a brief description: maybe combine first paragraph? The posting starts: "Manager, Workforce Intelligence (Data Architect) RTX is seeking a skilled and experienced Manager, Workforce Intelligence (Data Architect) to join our team." That's basically role intro. Could be About the role.
- Responsibilities: list from "What You Will Do". Use
- .
- Requirements: maybe combine Qualifications You Must Have and Qualifications We Prefer? Could separate Requirements (must have) and Skills (preferred). But we have sections: Requirements, Qualifications, Skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- About the role: intro paragraph.
- Responsibilities: list of duties.
- Requirements: mandatory qualifications (You Must Have). Could be under Requirements.
- Qualifications: maybe preferred qualifications? Or we could treat Qualifications as both mandatory and preferred? But we have separate Skills section for preferred? The instruction says prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those with real content.
We have content for:
- About the role: yes.
- Responsibilities: yes.
- Requirements (mandatory qualifications): yes.
- Qualifications (maybe preferred): yes.
- Skills: maybe we could put technical skills like Snowflake, SQL Server, etc. But those are already in qualifications. Could combine.
- Benefits: yes.
- Pay: yes.
- Schedule: maybe remote work description? Could be Schedule? The posting mentions remote role, work primarily offsite, maybe occasional onsite. That's schedule info. Could put under Schedule.
Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly skip Skills if redundant.
We must not include empty sections.
Now we need to format.
Use
for each heading.
Under each heading, we need either
for prose or
- for list.
For About the role: prose paragraph.
Responsibilities: list.
Requirements: list (mandatory qualifications). Could be bullet list.
Qualifications: list (preferred qualifications). Could be bullet list.
Benefits: list.
Pay: prose (salary range).
Schedule: prose (remote work details).
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract details.
About the role: The first sentence: "Manager, Workforce Intelligence (Data Architect) RTX is seeking a skilled and experienced Manager, Workforce Intelligence (Data Architect) to join our team." That's basically the role. Could also include that it's a remote role? But that's separate. We'll keep just that sentence.
Responsibilities: list from "What You Will Do". Let's extract each bullet:
- Design and maintain scalable HR data architecture in Snowflake, including databases, schemas, data models and semantic views.
- Build and optimize ETL/ELT pipelines using Matillion and Snowflake to support reporting, analytics and operational needs.
- Define and enforce data governance, data quality, consistency, lineage, naming standards and compliance with regulatory requirements for HR data.
- Develop and maintain data controls to ensure the integrity and reliability of data across systems and workflows.
- Implement and manage security policies for user views and semantic layers, including role-based access and data protection.
- Manage SQL Server environments used for metadata management, including performance tuning and reliability.
- Establish DevOps practices (version control, deployment automation, environment promotion) for schemas, pipelines and data models.
- Partner with Product and Delivery, BU Consultants and BI development teams to translate requirements into scalable, governed data solutions.
- Provide consultation and guidance on data architecture, integration and analytics capabilities.
- Create and maintain comprehensive documentation for data architecture designs, processes, governance policies, and integrations.
- Support AI-ready and agentic use cases by organizing trusted semantics, metadata and reusable data products.
That's 12 items.
Requirements (You Must Have): The text:
"Typically requires: A University Degree or equivalent experience and minimum 8 years prior relevant experience, or an Advanced Degree in a related field and minimum 5 years experience
7+ years of experience in data architecture or data engineering.
Strong hands-on experience with Snowflake (design, modeling, performance) and cloud data services.
Experience building API Integration, ETL/ELT pipelines.
Strong SQL Server skills (design, indexing, performance tuning).
Proven experience with data governance, metadata management and data security.
Experience with version control (e.g., Git) and automated deployment for data assets.
Strong communication and stakeholder collaboration skills."
We need to preserve each as bullet.
Qualifications (We Prefer):
"Excellent communication and coordination skills to work effectively with technical and non-technical stakeholders.
Certification in Snowflake or relevant cloud data services.
Scripting skills (e.g., Python, Shell) for automation.
Familiarity with API integrations and microservices architecture.
Knowledge of cloud platforms (Preferably Azure).
Experience with HR systems such as Workday"
We'll list those.
Benefits: list from "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement."
We need to preserve all benefits listed. Also note that there may be additional: "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company's performance." That's more about incentive compensation, not benefits per se but could be considered part of compensation. Might be included under Pay? But we already have Pay section for salary range. Could include incentive info under Pay or separate? The instruction: include Pay section only if posting actually states them. It states salary range and also mentions incentive compensation programs. Could include both in Pay section as prose.
But we need to avoid filler like "not guaranteed". That's substantive though. We'll include.
Schedule: remote work description: "This Position Is Classified As Remote: Employees who are working in Remote roles will work primarily offsite (from home). If you live within a reasonable commute of an RTX site with other colleagues you interact with, your manager will discuss whether there is a degree of onsite presence associated with this role. As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote." The latter part about interview process maybe considered application instructions; we might remove that. Keep remote work description.
Also "This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and benefits will apply." That's location info; could be under Schedule or About the role. Might include under Schedule.
We need to avoid duplication.
Now we must not include boilerplate: EEO statement, etc. Remove.
Now produce HTML.
We'll structure:
About the role
Manager, Workforce Intelligence (Data Architect) RTX is seeking a skilled and experienced Manager, Workforce Intelligence (Data Architect) to join our team.
Responsibilities
- Design and maintain scalable HR data architecture in Snowflake, including databases, schemas, data models and semantic views.
...
Requirements
- A University Degree or equivalent experience and minimum 8 years prior relevant experience, or an Advanced Degree in a related field and minimum 5 years experience
- 7+ years of experience in data architecture or data engineering.
- Strong hands-on experience with Snowflake (design, modeling, performance) and cloud data services.
- Experience building API Integration, ETL/ELT pipelines.
- Strong SQL Server skills (design, indexing, performance tuning).
- Proven experience with data governance, metadata management and data security.
- Experience with version control (e.g., Git) and automated deployment for data assets.
- Strong communication and stakeholder collaboration skills.
Qualifications
- Excellent communication and coordination skills to work effectively with technical and non-technical stakeholders.
- Certification in Snowflake or relevant cloud data services.
- Scripting skills (e.g., Python, Shell) for automation.
- Familiarity with API integrations and microservices architecture.
- Knowledge of cloud platforms (Preferably Azure).
- Experience with HR systems such as Workday
Benefits
- medical
- dental
- vision
- life insurance
- short-term disability
- long-term disability
- 401(k) match
- flexible spending accounts
- flexible work schedules
- employee assistance program
- Employee Scholar Program
- parental
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Title: Manager, Workforce Intelligence (Data Architect) RTX is seeking... - What You Will Do: list of responsibilities (design and maintain scalable HR data architecture in Snowflake, etc.) - Qualifications You Must Have: bullet list (actually sentences). Then "Qualifications We Prefer": bullet list. - This Position Is Classified As Remote: description. - As part of our commitment... (hiring process) maybe not needed? It's about interview process; could be considered boilerplate? It's not EEO but still maybe not needed? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The interview process details might be considered application instructions? Possibly remove. But we need to preserve substantive information. The remote classification and salary range and benefits are substantive. The interview process details maybe not needed. The EEO statement definitely remove. The "This role is a U.S.-based role..." maybe keep? It's about location; could be considered part of role description. Might keep as prose. - Salary range: "The salary range for this role is 107,500 USD - 204,500 USD." That's Pay. - Benefits: list of benefits. - Application window closing approx 40 days... maybe not needed? It's about application process; could be considered application instructions; maybe remove. - EEO statement remove. Thus sections: - About the role: maybe a short paragraph summarizing role? The posting includes "What You Will Do" which is responsibilities. Could treat "About the role" as a brief description: maybe combine first paragraph? The posting starts: "Manager, Workforce Intelligence (Data Architect) RTX is seeking a skilled and experienced Manager, Workforce Intelligence (Data Architect) to join our team." That's basically role intro. Could be About the role. - Responsibilities: list from "What You Will Do". Use
- .
- Requirements: maybe combine Qualifications You Must Have and Qualifications We Prefer? Could separate Requirements (must have) and Skills (preferred). But we have sections: Requirements, Qualifications, Skills. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- About the role: intro paragraph.
- Responsibilities: list of duties.
- Requirements: mandatory qualifications (You Must Have). Could be under Requirements.
- Qualifications: maybe preferred qualifications? Or we could treat Qualifications as both mandatory and preferred? But we have separate Skills section for preferred? The instruction says prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those with real content.
We have content for:
- About the role: yes.
- Responsibilities: yes.
- Requirements (mandatory qualifications): yes.
- Qualifications (maybe preferred): yes.
- Skills: maybe we could put technical skills like Snowflake, SQL Server, etc. But those are already in qualifications. Could combine.
- Benefits: yes.
- Pay: yes.
- Schedule: maybe remote work description? Could be Schedule? The posting mentions remote role, work primarily offsite, maybe occasional onsite. That's schedule info. Could put under Schedule.
Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Possibly skip Skills if redundant.
We must not include empty sections.
Now we need to format.
Use
for each heading. Under each heading, we need either
for prose or
- for list.
For About the role: prose paragraph.
Responsibilities: list.
Requirements: list (mandatory qualifications). Could be bullet list.
Qualifications: list (preferred qualifications). Could be bullet list.
Benefits: list.
Pay: prose (salary range).
Schedule: prose (remote work details).
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract details.
About the role: The first sentence: "Manager, Workforce Intelligence (Data Architect) RTX is seeking a skilled and experienced Manager, Workforce Intelligence (Data Architect) to join our team." That's basically the role. Could also include that it's a remote role? But that's separate. We'll keep just that sentence.
Responsibilities: list from "What You Will Do". Let's extract each bullet:
- Design and maintain scalable HR data architecture in Snowflake, including databases, schemas, data models and semantic views.
- Build and optimize ETL/ELT pipelines using Matillion and Snowflake to support reporting, analytics and operational needs.
- Define and enforce data governance, data quality, consistency, lineage, naming standards and compliance with regulatory requirements for HR data.
- Develop and maintain data controls to ensure the integrity and reliability of data across systems and workflows.
- Implement and manage security policies for user views and semantic layers, including role-based access and data protection.
- Manage SQL Server environments used for metadata management, including performance tuning and reliability.
- Establish DevOps practices (version control, deployment automation, environment promotion) for schemas, pipelines and data models.
- Partner with Product and Delivery, BU Consultants and BI development teams to translate requirements into scalable, governed data solutions.
- Provide consultation and guidance on data architecture, integration and analytics capabilities.
- Create and maintain comprehensive documentation for data architecture designs, processes, governance policies, and integrations.
- Support AI-ready and agentic use cases by organizing trusted semantics, metadata and reusable data products.
That's 12 items.
Requirements (You Must Have): The text:
"Typically requires: A University Degree or equivalent experience and minimum 8 years prior relevant experience, or an Advanced Degree in a related field and minimum 5 years experience
7+ years of experience in data architecture or data engineering.
Strong hands-on experience with Snowflake (design, modeling, performance) and cloud data services.
Experience building API Integration, ETL/ELT pipelines.
Strong SQL Server skills (design, indexing, performance tuning).
Proven experience with data governance, metadata management and data security.
Experience with version control (e.g., Git) and automated deployment for data assets.
Strong communication and stakeholder collaboration skills."
We need to preserve each as bullet.
Qualifications (We Prefer):
"Excellent communication and coordination skills to work effectively with technical and non-technical stakeholders.
Certification in Snowflake or relevant cloud data services.
Scripting skills (e.g., Python, Shell) for automation.
Familiarity with API integrations and microservices architecture.
Knowledge of cloud platforms (Preferably Azure).
Experience with HR systems such as Workday"
We'll list those.
Benefits: list from "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement."
We need to preserve all benefits listed. Also note that there may be additional: "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company's performance." That's more about incentive compensation, not benefits per se but could be considered part of compensation. Might be included under Pay? But we already have Pay section for salary range. Could include incentive info under Pay or separate? The instruction: include Pay section only if posting actually states them. It states salary range and also mentions incentive compensation programs. Could include both in Pay section as prose.
But we need to avoid filler like "not guaranteed". That's substantive though. We'll include.
Schedule: remote work description: "This Position Is Classified As Remote: Employees who are working in Remote roles will work primarily offsite (from home). If you live within a reasonable commute of an RTX site with other colleagues you interact with, your manager will discuss whether there is a degree of onsite presence associated with this role. As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote." The latter part about interview process maybe considered application instructions; we might remove that. Keep remote work description.
Also "This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and benefits will apply." That's location info; could be under Schedule or About the role. Might include under Schedule.
We need to avoid duplication.
Now we must not include boilerplate: EEO statement, etc. Remove.
Now produce HTML.
We'll structure:
About the role
Manager, Workforce Intelligence (Data Architect) RTX is seeking a skilled and experienced Manager, Workforce Intelligence (Data Architect) to join our team.
Responsibilities
- Design and maintain scalable HR data architecture in Snowflake, including databases, schemas, data models and semantic views. ...
Requirements
- A University Degree or equivalent experience and minimum 8 years prior relevant experience, or an Advanced Degree in a related field and minimum 5 years experience
- 7+ years of experience in data architecture or data engineering.
- Strong hands-on experience with Snowflake (design, modeling, performance) and cloud data services.
- Experience building API Integration, ETL/ELT pipelines.
- Strong SQL Server skills (design, indexing, performance tuning).
- Proven experience with data governance, metadata management and data security.
- Experience with version control (e.g., Git) and automated deployment for data assets.
- Strong communication and stakeholder collaboration skills.
Qualifications
- Excellent communication and coordination skills to work effectively with technical and non-technical stakeholders.
- Certification in Snowflake or relevant cloud data services.
- Scripting skills (e.g., Python, Shell) for automation.
- Familiarity with API integrations and microservices architecture.
- Knowledge of cloud platforms (Preferably Azure).
- Experience with HR systems such as Workday
Benefits
- medical
- dental
- vision
- life insurance
- short-term disability
- long-term disability
- 401(k) match
- flexible spending accounts
- flexible work schedules
- employee assistance program
- Employee Scholar Program
- parental
- for list.
For About the role: prose paragraph.
Responsibilities: list.
Requirements: list (mandatory qualifications). Could be bullet list.
Qualifications: list (preferred qualifications). Could be bullet list.
Benefits: list.
Pay: prose (salary range).
Schedule: prose (remote work details).
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract details.
About the role: The first sentence: "Manager, Workforce Intelligence (Data Architect) RTX is seeking a skilled and experienced Manager, Workforce Intelligence (Data Architect) to join our team." That's basically the role. Could also include that it's a remote role? But that's separate. We'll keep just that sentence.
Responsibilities: list from "What You Will Do". Let's extract each bullet:
- Design and maintain scalable HR data architecture in Snowflake, including databases, schemas, data models and semantic views.
- Build and optimize ETL/ELT pipelines using Matillion and Snowflake to support reporting, analytics and operational needs.
- Define and enforce data governance, data quality, consistency, lineage, naming standards and compliance with regulatory requirements for HR data.
- Develop and maintain data controls to ensure the integrity and reliability of data across systems and workflows.
- Implement and manage security policies for user views and semantic layers, including role-based access and data protection.
- Manage SQL Server environments used for metadata management, including performance tuning and reliability.
- Establish DevOps practices (version control, deployment automation, environment promotion) for schemas, pipelines and data models.
- Partner with Product and Delivery, BU Consultants and BI development teams to translate requirements into scalable, governed data solutions.
- Provide consultation and guidance on data architecture, integration and analytics capabilities.
- Create and maintain comprehensive documentation for data architecture designs, processes, governance policies, and integrations.
- Support AI-ready and agentic use cases by organizing trusted semantics, metadata and reusable data products.
That's 12 items.
Requirements (You Must Have): The text:
"Typically requires: A University Degree or equivalent experience and minimum 8 years prior relevant experience, or an Advanced Degree in a related field and minimum 5 years experience
7+ years of experience in data architecture or data engineering.
Strong hands-on experience with Snowflake (design, modeling, performance) and cloud data services.
Experience building API Integration, ETL/ELT pipelines.
Strong SQL Server skills (design, indexing, performance tuning).
Proven experience with data governance, metadata management and data security.
Experience with version control (e.g., Git) and automated deployment for data assets.
Strong communication and stakeholder collaboration skills."
We need to preserve each as bullet.
Qualifications (We Prefer):
"Excellent communication and coordination skills to work effectively with technical and non-technical stakeholders.
Certification in Snowflake or relevant cloud data services.
Scripting skills (e.g., Python, Shell) for automation.
Familiarity with API integrations and microservices architecture.
Knowledge of cloud platforms (Preferably Azure).
Experience with HR systems such as Workday"
We'll list those.
Benefits: list from "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement."
We need to preserve all benefits listed. Also note that there may be additional: "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company's performance." That's more about incentive compensation, not benefits per se but could be considered part of compensation. Might be included under Pay? But we already have Pay section for salary range. Could include incentive info under Pay or separate? The instruction: include Pay section only if posting actually states them. It states salary range and also mentions incentive compensation programs. Could include both in Pay section as prose.
But we need to avoid filler like "not guaranteed". That's substantive though. We'll include.
Schedule: remote work description: "This Position Is Classified As Remote: Employees who are working in Remote roles will work primarily offsite (from home). If you live within a reasonable commute of an RTX site with other colleagues you interact with, your manager will discuss whether there is a degree of onsite presence associated with this role. As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote." The latter part about interview process maybe considered application instructions; we might remove that. Keep remote work description.
Also "This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and benefits will apply." That's location info; could be under Schedule or About the role. Might include under Schedule.
We need to avoid duplication.
Now we must not include boilerplate: EEO statement, etc. Remove.
Now produce HTML.
We'll structure: