Senior Data Architect
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must not emit a heading followed by filler/placeholder text. So each section must have real content.
We need to decide which sections to include.
Potential sections:
- About the role (description of group, projects, location, hybrid model)
- Responsibilities (list of duties)
- Requirements (required qualifications: BS degree + 10+ years, etc)
- Qualifications (desired qualifications/non essential skills: Bachelor's Degree and 8-10 years directly related work experience, meeting with client in Baltimore, Medicare/Medicaid domain knowledge, AI models, etc)
- Skills (technical skills list)
- Benefits (list)
- Pay (compensation range)
We should not include Schedule.
Now we need to ensure we don't duplicate content across sections. The required qualifications and desired qualifications overlap somewhat; we need to preserve all info but can split.
Let's extract required qualifications bullet points:
From "Required Qualifications To Be Successful In This Role":
- Possesses a BS degree and 10+ years of work experience.
- Demonstrate an advanced ability to manage large data sets, cloud computing, open source tools, and optimization techniques.
- 8+ years of proven experience in application architecture, Cloud Solutions with emerging technologies, Big Data, Data Modeling, Data Architecture, Data Warehousing and Business Intelligence.
- Understanding of modern data architecture and experience with core data services like maintaining data lakes, data warehouses, data marts as well as relational and dimensional modeling, data quality and master data management.
- Excellent data management and data governance skills and analytical thinking capabilities.
- Experience in designing data architectures that will define and deliver data as an asset
- Experience in Dimensional Modeling (Star Schema, OLAP Cubes, and Bus Matrix Mapping)
- Skilled in the design, deployment, and evaluation of tools, frameworks, and patterns to build scalable data platforms
- Experienced with industry leading data infrastructure technologies and end user tools
- Experience with troubleshooting data issues and identifying root causes of performance bottlenecks.
- Experience with AWS, Oracle and Postgres databases, Analysis services, ETL tools, etc.
- Strong SQL development skills using SQL, PL/SQL, stored procedures etc.
- Knowledge of creating and delivering modern data platforms that will provide advanced analytical capabilities
- Proficiency in Visualization and Reporting Tools.
- Experience in reporting tools like Quicksight, Cognos, etc
- Experienced with AWS public cloud platform.
- Good Working knowledge of AWS data platform – S3, Iceberg tables, data catalogs, data lake, analytics, AWS storage options, Athena, Glue, Redshift, AWS Lake formation, etc.
- Experience with Agile software development.
- Experience with Confluence and Jira
- Good to have Medicare/Medicaid data domain knowledge.
- Good experience in using AI models like Bedrock, Co-Pilot, etc.
Then "Desired qualifications/non essential skills required:":
- Education: Bachelor's Degree and 8 -10 years directly related work experience is required.
- This position requires meeting with the client in Baltimore, Maryland.
Also earlier: "CGI is required by law in some jurisdictions to include a reasonable estimate of the compensation range for this role." etc.
Also benefits list.
Also location/hybrid.
Now we need to avoid duplication: For example, "BS degree and 10+ years work experience" appears both in required qualifications and desired qualifications (8-10 years). We'll keep both but maybe we can combine? But we must preserve all substantive information; we can keep both but maybe we can note that required is BS + 10+ years, desired is Bachelor's Degree and 8-10 years directly related work experience (some overlap). We'll keep both as separate bullet points under appropriate sections.
Now we need to decide which section each bullet goes.
We could put required qualifications under "Requirements". Desired qualifications under "Qualifications". Skills under "Skills". However many of the required qualifications are also skills. But we can separate: Requirements = education/experience baseline; Skills = technical proficiencies.
But the instruction: Use
- for any list of duties/requirements/benefits. So we can have lists for duties, requirements, benefits. For skills we could also use list.
We need to avoid creating thin sections. So maybe combine Requirements and Qualifications into one? But they said prefer a few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Requirements (including both required and desired qualifications), Skills, Benefits, Pay. That's 6 sections.
But we need to ensure we don't create a section with filler. Each will have content.
Let's draft:
About the role
The Health and Compliance group at CGI Federal is seeking a Senior Data Architect to join a large team in a dynamic, changing environment. The role involves software solution development and maintenance for mission‑critical applications in the federal healthcare space, using rapid design and development techniques to meet client demands driven by healthcare reform and open‑government directives. CGI Federal provides deep functional and technical expertise to help federal health organizations become more productive, cost‑effective, secure, and service‑oriented. The position is based in either the Fairfax, VA or Lafayette, LA office, with a hybrid working model available.
That captures description and location/hybrid.
Responsibilities
- Provides expertise in designing, creating, deploying and managing an organization's data architecture.
- Able to define how data should be stored, consumed, integrated and managed by different data entities and IT systems, as well as any applications using or processing that data.
- Designs and implements industry best Data modeling solutions to satisfy client requirements.
- Good experience in converting the relational model to de‑normalized data model.
- Documents data object relationships and understands how these objects form business transactions within a large transaction processing system.
- Diagnoses data‑related production issues by understanding existing data object relationships and performing required data updates.
- Expresses strategic data requirements, outlines high‑level integrated designs to meet these requirements, and aligns with enterprise strategy and related business architecture.
- Provides guidance for infrastructure and software architecture and planning.
- Identifies and guides development of data standards.
- Develops data architecture principles, creates models of data that enable the implementation of the intended business architecture, creates ER diagrams showing key data entities, and creates an inventory of the data needed to implement the architecture vision.
Note: Some sentences were split; we need to ensure we preserve all info. Let's verify we captured all duties from the "Your future duties and responsibilities" paragraph.
Original paragraph:
"Provides expertise in designing, creating, deploying and managing an organization's data architecture.
Able to define how data should be stored, consumed, integrated and managed by different data entities and IT systems, as well as any applications using or processing that data.
Designs and implements industry best Data modeling solutions to satisfy client requirements
Good experience in converting the relational model to de-normalized data model.
Document data object relationships and understand how these objects form business transactions within a large transaction processing system.
Diagnosing data related production issues by understanding existing data object relationships and performing required data updates.
Expresses strategic data requirements, outlines high level integrated designs to meet these requirements, and aligns with enterprise strategy and related business architecture.
Provides guidance for infrastructure and software architecture and planning.
Identifies and guides development
for prose. We must not emit a heading followed by filler/placeholder text. So each section must have real content. We need to decide which sections to include. Potential sections: - About the role (description of group, projects, location, hybrid model) - Responsibilities (list of duties) - Requirements (required qualifications: BS degree + 10+ years, etc) - Qualifications (desired qualifications/non essential skills: Bachelor's Degree and 8-10 years directly related work experience, meeting with client in Baltimore, Medicare/Medicaid domain knowledge, AI models, etc) - Skills (technical skills list) - Benefits (list) - Pay (compensation range) We should not include Schedule. Now we need to ensure we don't duplicate content across sections. The required qualifications and desired qualifications overlap somewhat; we need to preserve all info but can split. Let's extract required qualifications bullet points: From "Required Qualifications To Be Successful In This Role": - Possesses a BS degree and 10+ years of work experience. - Demonstrate an advanced ability to manage large data sets, cloud computing, open source tools, and optimization techniques. - 8+ years of proven experience in application architecture, Cloud Solutions with emerging technologies, Big Data, Data Modeling, Data Architecture, Data Warehousing and Business Intelligence. - Understanding of modern data architecture and experience with core data services like maintaining data lakes, data warehouses, data marts as well as relational and dimensional modeling, data quality and master data management. - Excellent data management and data governance skills and analytical thinking capabilities. - Experience in designing data architectures that will define and deliver data as an asset - Experience in Dimensional Modeling (Star Schema, OLAP Cubes, and Bus Matrix Mapping) - Skilled in the design, deployment, and evaluation of tools, frameworks, and patterns to build scalable data platforms - Experienced with industry leading data infrastructure technologies and end user tools - Experience with troubleshooting data issues and identifying root causes of performance bottlenecks. - Experience with AWS, Oracle and Postgres databases, Analysis services, ETL tools, etc. - Strong SQL development skills using SQL, PL/SQL, stored procedures etc. - Knowledge of creating and delivering modern data platforms that will provide advanced analytical capabilities - Proficiency in Visualization and Reporting Tools. - Experience in reporting tools like Quicksight, Cognos, etc - Experienced with AWS public cloud platform. - Good Working knowledge of AWS data platform – S3, Iceberg tables, data catalogs, data lake, analytics, AWS storage options, Athena, Glue, Redshift, AWS Lake formation, etc. - Experience with Agile software development. - Experience with Confluence and Jira - Good to have Medicare/Medicaid data domain knowledge. - Good experience in using AI models like Bedrock, Co-Pilot, etc. Then "Desired qualifications/non essential skills required:": - Education: Bachelor's Degree and 8 -10 years directly related work experience is required. - This position requires meeting with the client in Baltimore, Maryland. Also earlier: "CGI is required by law in some jurisdictions to include a reasonable estimate of the compensation range for this role." etc. Also benefits list. Also location/hybrid. Now we need to avoid duplication: For example, "BS degree and 10+ years work experience" appears both in required qualifications and desired qualifications (8-10 years). We'll keep both but maybe we can combine? But we must preserve all substantive information; we can keep both but maybe we can note that required is BS + 10+ years, desired is Bachelor's Degree and 8-10 years directly related work experience (some overlap). We'll keep both as separate bullet points under appropriate sections. Now we need to decide which section each bullet goes. We could put required qualifications under "Requirements". Desired qualifications under "Qualifications". Skills under "Skills". However many of the required qualifications are also skills. But we can separate: Requirements = education/experience baseline; Skills = technical proficiencies. But the instruction: Use
- for any list of duties/requirements/benefits. So we can have lists for duties, requirements, benefits. For skills we could also use list.
We need to avoid creating thin sections. So maybe combine Requirements and Qualifications into one? But they said prefer a few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Requirements (including both required and desired qualifications), Skills, Benefits, Pay. That's 6 sections.
But we need to ensure we don't create a section with filler. Each will have content.
Let's draft:
About the role
The Health and Compliance group at CGI Federal is seeking a Senior Data Architect to join a large team in a dynamic, changing environment. The role involves software solution development and maintenance for mission‑critical applications in the federal healthcare space, using rapid design and development techniques to meet client demands driven by healthcare reform and open‑government directives. CGI Federal provides deep functional and technical expertise to help federal health organizations become more productive, cost‑effective, secure, and service‑oriented. The position is based in either the Fairfax, VA or Lafayette, LA office, with a hybrid working model available.
That captures description and location/hybrid.Responsibilities
- Provides expertise in designing, creating, deploying and managing an organization's data architecture.
- Able to define how data should be stored, consumed, integrated and managed by different data entities and IT systems, as well as any applications using or processing that data.
- Designs and implements industry best Data modeling solutions to satisfy client requirements.
- Good experience in converting the relational model to de‑normalized data model.
- Documents data object relationships and understands how these objects form business transactions within a large transaction processing system.
- Diagnoses data‑related production issues by understanding existing data object relationships and performing required data updates.
- Expresses strategic data requirements, outlines high‑level integrated designs to meet these requirements, and aligns with enterprise strategy and related business architecture.
- Provides guidance for infrastructure and software architecture and planning.
- Identifies and guides development of data standards.
- Develops data architecture principles, creates models of data that enable the implementation of the intended business architecture, creates ER diagrams showing key data entities, and creates an inventory of the data needed to implement the architecture vision.