Senior Platform Engineer

We need to output HTML fragment with sections: About the role? The posting includes description about Accenture Federal Services, mission, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "As required by local law..."? That's about compensation ranges; we need to keep compensation info (Pay). The posting includes base pay range for certain states: $124,000—$246,400 USD. Also mentions "Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here." That's vague; we cannot create Benefits section unless posting actually states them. It just says offers a wide variety of benefits, but no specifics. According to rule: never create Benefits section unless posting actually states them. Since it only says offers a wide variety of benefits with link, but no detail, we should not create Benefits section. Similarly, Schedule: not mentioned. So we may have sections: About the role (maybe we can combine intro), Responsibilities (What You Will Do), Requirements/Qualifications (What you’ll need, Bonus Points if you have, Clearance), maybe Skills (but we can incorporate into Requirements). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We need to avoid filler headings. So we need to decide which sections have real specific content. We have: - About the role: The intro paragraph about Accenture Federal Services mission, description of role: "Accenture Federal Services is seeking a Data Platform Architect to set technical vision for a common data platform and broader mission cloud ecosystem in a secure, regulated environment. This is a hands-on technical leadership role, influencing the delivery team as the platform expands. Architecture governance is collective, with this role as a key voice on data architecture." That's substantive. So we can have About the role section. - Responsibilities: "What You Will Do:" list bullet points. So we can have Responsibilities section with

• . - Requirements/Qualifications: "What you’ll need:" list bullet points. Also "Bonus Points if you have:" list. Also "Clearance: Must have an active Top Secret level clearance". So we can have Requirements section (maybe combine required and bonus). Could also have Qualifications separate but we can just have Requirements. - Skills: Could be derived from requirements but we might not need separate Skills if we already have Requirements. The instruction says prefer a few substantive sections over many thin ones. So we can combine Requirements and Qualifications into one section maybe called Requirements. Or we could have Requirements and Qualifications separate if there is distinct content. The "What you’ll need:" includes hands-on development/engineering experience, Python development skills, experience working with senior stakeholders, experience setting technical direction. Bonus points list includes many specific experiences. Could treat those as Qualifications. But to keep few sections, we can have Requirements (including required and preferred). That's fine. - Pay: The posting includes base pay range for certain states: $124,000—$246,400 USD. Also mentions compensation varies depending on factors. So we have Pay section. - Benefits: Not specific, so omit. - Schedule: Not mentioned, omit. Thus output HTML with sections: About the role, Responsibilities, Requirements, Pay. We need to use

  for each section heading. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. The job title is Data Platform Architect; we should not put that as heading. We must not put Job ID/requisition numbers as headings; none present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from What You Will Do, What you’ll need, Bonus Points if you have, Clearance, Pay range, etc. Also include the introductory paragraphs about Accenture Federal Services mission and role description. We need to remove boilerplate: EEO statements, accommodation, other employment statements, etc. Also remove lines like "As required by local law, Accenture Federal Services provides reasonable ranges of compensation for hired roles based on labor costs in the states of California, Colorado, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Virginia, Washington, and the District of Columbia, and the city of Cleveland." That's part of Pay info but we need to keep the pay range. The sentence about compensation varying depending on factors is also part of Pay. We can keep that as prose. We need to remove duplicated lines: The pay range appears twice? It appears: "The base pay range for this position in these locations is shown below. Compensation for roles at Accenture Federal Services varies depending on a wide array of factors, including but not limited to office location, role, skill set, and level of experience. Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here. We accept applications on an on-going basis and there is no fixed deadline to apply. The pay range for the states of California, Colorado, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Virginia, Washington, and the District of Columbia, and the city of Cleveland is: $124,000—$246,400 USD". We'll keep the pay range and maybe the sentence about compensation varying. The benefits line we omit because no specifics. The "We accept applications..." is application instruction, remove. We also need to remove lines like "As a company wholly dedicated to serving the US federal government..." that's part of "What We Believe" etc. That's boilerplate? It's about company values; might be considered boilerplate but it's substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What We Believe" section is more about company culture; could be considered boilerplate but not explicitly listed. However it's likely part of generic fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "What We Believe" is not directly about the job; it's generic company statement. Might be considered boilerplate but not EEO. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not EEO. It's a values statement. Could be considered boilerplate but not explicitly prohibited. However we prefer few substantive sections; we could include it in About the role section as part of description. But it's not directly about the role. Might be okay to keep as part of About the role. But we need to be careful not to include too much fluff. The instruction: "Prefer a few substantive sections over many thin ones." So we can include a brief About the role paragraph that captures the role description and maybe the mission statement. We'll include the first paragraph: "At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. Join us to drive positive, lasting change that moves missions and the government forward!" That's generic but maybe okay. Then the role-specific description: "Accenture Federal Services is seeking a Data Platform Architect to set technical vision for a common data platform and broader mission cloud ecosystem in a secure, regulated environment. This is a hands-on technical leadership role, influencing the delivery team as the platform expands. Architecture governance is collective, with this role as a key voice on data architecture." We'll include that. Now Responsibilities: list bullet points from "What You Will Do:" (the bullet points). We need to preserve each bullet. Let's extract them: - Own technical vision and roadmap for the data platform (data lake/lakehouse, ingestion, modeling, governance, analytics) - Translate vision into design decisions, standards, and reference patterns for engineering - Present and defend architecture positions to the Architecture Review Board; communicate approved decisions to the team - Influence architectural direction beyond the data platform as the program matures - Identify and retire technical debt with clear rationale - Remain hands-on: prototype, review code, build reference implementations, set engineering quality standards - Design/build data pipelines and platform services in Python and related tools, focusing on performance, reliability, maintainability - Establish data quality, lineage, and observability practices - Ensure security and compliance requirements are met from the start - Stakeholder Engagement - Engage government customers and mission stakeholders to clarify direction and requirements - Communicate technical vision, tradeoffs, and risks to senior stakeholders in actionable language - Ensure technical team understands both what to build and why - Represent the data platform in customer and partner discussions - Documentation and Standards - Document decisions, standards, patterns, and rationale for transparency and onboarding - Contribute to and uphold engineering and architecture standards We need to format as

    • . For sub-bullets, we could either nest
      inside
      • or just keep as separate lines with dash. The instruction: Use
        • for any list of duties/requirements/benefits. It doesn't forbid nesting. We'll do top-level
          with
          • items; for sub-bullets we can include another
            inside. Now Requirements: "What you’ll need:" bullet points: - Hands-on development/engineering experience (data architecture/platforms) - Python development skills and familiarity with data processing, orchestration, and/or analysis tools - Experience working with senior stakeholders and/or leading engineering teams, adjusting depth/language as needed - Experience setting technical direction through influence, standards, and design leadership Then "Bonus Points if you have:" list: - Ability to turn unclear stakeholder direction into defensible technical requirements/designs - Experience designing/delivering data lake, lakehouse, or large-scale data platform solutions (e.g.: ingestion, storage, transformation, governance, consumption) - Experience with distributed data processing frameworks and/or modern open data formats - Experience with architecture governance (e.g.: review boards, design reviews, consensus building) - Experience supporting test, evaluation, or operational data workflows with large data collection/analysis - Experience with data tagging, classification, and segregation in strict access control environments - Experience delivering in DevSecOps pipelines with automated security/compliance controls - Familiarity with MBSE and model-driven approaches to systems/data design - Experience in SAFe or similar scaled agile environments - Experience mentoring engineers and raising technical capability without formal management Then "Clearance: Must have an active Top Secret level clearance" We'll include all these as
            • items under Requirements section. Could separate required vs bonus but we can just list all. Now Pay: We need to include the pay range and maybe the sentence about compensation varying. We'll put:

              The base pay range for this position in the listed locations is $124,000—$246,400 USD. Compensation varies depending on factors such as office location, role, skill set, and level of experience.

              We should not include the benefits line. Now we need to output only HTML fragment, no /, no markdown fences. Thus final output:

              About the role