Solutions Architect - Data Platform Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: "We offer a hybrid work schedule (one week in the office, one week of teleworking)" => schedule content. Also "Expected Hiring Base Salary Range: $116,300 - $151100" (typo maybe $151,100). So Pay section exists. Benefits: "At Dominion Energy, we offer excellent plans and programs for employees. Employees are rewarded with a competitive salary and comprehensive benefits package which includes: health, dental, and vision benefits with coverage for families and domestic partners, vacation, retirement plans including 401k contributions and matches, paid holidays, tuition reimbursement, bonus eligibility, sick leave, and disability insurance." So Benefits section exists. We also have "About the role" maybe from job summary? The posting includes "Job Summary" paragraph. Could treat as About the role. Also "Key Responsibilities" list. Also "Required Knowledge, Skills, Abilities & Experience" includes required experience and technical skills. Also "Preferred Qualifications". Also "Education Requirements". Also "Licenses, Certifications, or Quals Description". Also "Working Conditions". Also "Other Working Conditions". Also "Test Description". Also "Export Control". Also "What You'll Get" includes salary and benefits (we already captured). Also "Dominion Energy is an equal opportunity employer." That's boilerplate EEO, should be removed. Also "You can experience the excitement..." maybe boilerplate. We need to decide sections: About the role (Job Summary). Responsibilities (Key Responsibilities). Requirements (maybe combine Required Knowledge, Skills, Abilities & Experience). Qualifications (Preferred Qualifications). Skills (maybe technical skills? but we already have required technical skills; could be part of Requirements). However instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include those that have content. We need to avoid duplication. Let's map: - About the role: Job Summary paragraph. - Responsibilities: Key Responsibilities (list of bullet points). We'll need to convert each bullet into

. - Requirements: Required Knowledge, Skills, Abilities & Experience (including years of experience, leadership, etc.) plus maybe Education Requirements? Could separate Education as its own section? But we have Education Requirements separate. Could include under Requirements or Qualifications. Since we have separate headings for Qualifications (Preferred Qualifications) and Skills (maybe technical skills). Let's decide: We could have: - About the role - Responsibilities - Requirements (includes required experience, technical skills, leadership skills) - Qualifications (Preferred Qualifications) - Skills (maybe technical skills? but we already put technical skills under Requirements; maybe better to put technical skills under Skills and keep Requirements for experience/leadership. However the posting lumps them together. We need to preserve all info; we can split but must not lose info. Let's create: Requirements: includes the experience bullets (12+ years, 5+ years architecture leadership, etc.) and maybe also "Demonstrated Expertise In ..."? Actually that is under Required Knowledge, Skills, Abilities & Experience after the bullet list? The posting shows: Required Knowledge, Skills, Abilities & Experience The knowledge, skills, abilities and experiences that are required for entry into this job include the following: 12+ years of experience... 5+ years serving in architecture leadership roles. Demonstrated experience designing enterprise-scale data platforms. Proven record leading cross-functional modernization and transformation initiatives. Experience influencing strategic technology decisions without direct authority. Technical Skills Required expertise in the following technologies, or experience with similar tools and platforms: [list] Demonstrated Expertise In Data warehouse architecture... Leadership Skills Strong executive communication skills... Thus we could separate into Requirements (experience and leadership) and Skills (technical skills and demonstrated expertise). But the heading "Skills" is allowed. Let's do: - Requirements: experience and leadership bullets (the first 5 bullet points). - Skills: technical skills list and demonstrated expertise list (maybe also leadership skills? but we already put leadership under Requirements; but we could also include leadership skills under Requirements. We'll keep leadership skills under Requirements as they are part of "Leadership Skills". That seems fine. - Qualifications: Preferred Qualifications bullet list. - Education: Education Requirements. - Benefits: benefits paragraph. - Pay: salary range. - Schedule: hybrid work schedule. We also have Working Conditions etc. Could we include a section "Working Conditions"? Not in the allowed headings list but we could maybe include under About the role? The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It seems they expect those headings; we can include others if needed but better to stick to those. Working Conditions could be omitted? But we must preserve ALL substantive information. Working Conditions includes "Office Work Environment 76 -100% Travel Up to 25% Other Working Conditions". That's substantive. We could incorporate into About the role or maybe a separate section like "Working Conditions" but not in list. However instructions: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we could include a section "Working Conditions" as

as well; it's not prohibited. The important part is not to invent sections with filler. So we can add Working Conditions. Also there is "Licenses, Certifications, or Quals Description". Could be included under Qualifications or Education. Might be minor; we could incorporate into Qualifications. Also "Export Control" etc. That's substantive but maybe legal boilerplate? It's about export controls; could be considered legal/EEO? It's not EEO but it's a legal condition. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Export control is legal; maybe we should remove? It's a legal condition that may affect eligibility. It's substantive but maybe considered legal boilerplate. Safer to remove? The instruction says remove legal boilerplate. So we should remove Export Control section. Also "Test Description No Testing Requirements" - that's minor; could be omitted as filler? It's not really substantive; maybe we can drop. Also "Other Working Conditions" maybe part of Working Conditions. Thus final sections: About the role, Responsibilities, Requirements, Skills, Qualifications, Education, Benefits, Pay, Schedule, Working Conditions. Now we need to format lists. Let's extract content precisely. About the role (Job Summary): "We are seeking a Solution Architect, Data Platforms to lead the architecture, modernization, governance, security, and evolution of our enterprise data platform ecosystem. This role serves as a technical leader who defines strategy, establishes engineering standards, guides delivery teams, and influences technology direction across the organization's data landscape. The successful candidate will partner with enterprise architecture , business leaders, data engineers, platform teams, cybersecurity, and infrastructure teams to deliver scalable, secure, resilient, and governed data capabilities that enable enterprise analytics, data products, AI, and operational decision-making. This is a highly influential individual contributor role with broad architectural accountability. The role requires strong technical leadership, the ability to influence, and a record of driving enterprise-scale transformation." Note there is a space before comma after "enterprise architecture". We'll keep as is. Responsibilities: Key Responsibilities bullet points (each line starts with a bold heading? Actually they are headings like "Data Platform Strategy & Modernization" then sentences. We'll treat each as a list item with the heading bold? But we just need to output

with the text. We'll keep the heading as part of the li text. List: - Define and execute architecture roadmaps for enterprise data platforms by closely partnering with enterprise architecture team. - Lead modernization initiatives that simplify legacy environments and improve platform agility. - Establish future-state architectures for cloud, hybrid, and virtualized data ecosystems. - Evaluate emerging technologies and recommend strategic platform investments. - Drive technical debt reduction initiatives and improve long-term maintainability. - Data Products & Analytics Enablement - Design architecture patterns that accelerate delivery of trusted data products. - Define reusable ingestion, transformation, virtualization, and consumption frameworks. - Partner with data engineering and business teams to reduce time-to-value for analytics initiatives. - Enable scalable self-service analytics and reporting capabilities. - Establish architecture standards that support AI, advanced analytics, and enterprise reporting. - Reliability, Security & Governance - Architect resilient, highly available, and observable data platforms. - Define enterprise standards for RBAC, ABAC, encryption, masking, and data protection. - Establish platform monitoring, observability, operational health, and performance frameworks. - Partner with cybersecurity, compliance, risk, and governance teams to ensure alignment with enterprise requirements. - Design governance controls that improve trust, consistency, and compliance across data assets. - Architecture Governance & Standards - Lead architecture reviews and design assessments. - Create and maintain reference architectures, engineering standards, and reusable patterns. - Influence technology decisions across multiple teams and initiatives. - Provide architectural guidance during major project planning and implementation. - Maintain architecture decision records and technology standards. - Technical Leadership Expectations - Serve as a trusted advisor to senior leadership and delivery teams. - Influence architecture decisions across multiple organizations. - Mentor architects, engineers, and technical leads. - Drive consistency across platforms, delivery teams, and business domains. - Lead complex architecture discussions and technical trade-off analyses. - Build consensus among stakeholders with competing priorities. - Advocate for operational excellence, governance, security, and engineering best practices. We need to preserve all. We'll output each as

. Might be long but okay. Requirements: experience and leadership bullets (first five). Let's list: - 12+ years of experience in data, analytics, data engineering, or platform architecture. - 5+ years serving in architecture leadership roles. - Demonstrated experience designing enterprise-scale data platforms. - Proven record leading cross-functional modernization and transformation initiatives. - Experience influencing strategic technology decisions without direct authority. - Strong executive communication skills. - Ability to influence senior stakeholders. - Exceptional architectural reasoning and decision-making. - Strong facilitation and consensus-building skills. - Ability to translate business objectives into architectural solutions. Wait the leadership skills bullet list appears after "Leadership Skills". Those are also part of Required Knowledge, Skills, Abilities & Experience. So we should include them under Requirements as well. So combine experience and leadership skills. Thus Requirements list includes all those bullet points. Skills: technical skills list and demonstrated expertise list. Technical Skills Required expertise in the following technologies, or experience with similar tools and platforms: Snowflake (Must have) Oracle Exadata Denodo Talend/dbt Microsoft Azure Informatica Data Catalog Data Governance frameworks Data Observability platforms like Monte Carlo and operational monitoring practices Data Security architecture RBAC ABAC Encryption Data masking CI/CD and DevOps practices We need to format as list items maybe each technology? Could be a single paragraph but better to list each. However the instruction: Use

• for any list of duties/requirements/benefits. So we should list each item as
• . We'll split by commas and "and". Let's produce items: - Snowflake (Must have) - Oracle Exadata - Den