Datacenter Architect

We need to output HTML fragment only, with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Need to preserve substantive info. We need to parse the posting: It starts with "Who is Trace3?" then description of company. Then some culture bullet points (Street-Smart, Juice, Teamwork). Then "*This position can be either W2 Contract or FTE". Then JOB SUMMARY, SUMMARY OF ESSENTIAL JOB FUNCTIONS, REQUIRED SKILLS AND EXPERIENCE, LOCATION, CLEARANCE REQUIRMENT, SALARY RANGE, PHYSICAL DEMANDS, WORK ENVIRONMENT, The Perks, Our Commitment, etc. We need to decide which sections to include: About the role (maybe company overview?), Responsibilities (essential job functions), Requirements (maybe required skills/experience), Qualifications (maybe clearance?), Skills (maybe required skills?), Benefits (The Perks), Pay (salary range), Schedule (maybe location? but schedule not given). We should only include sections with real specific content. We have location: Full Time/ On-Site in Linthicum Heights, MD or Annapolis Junction, MD. That's location, not schedule. No schedule info. So we should not create Schedule section unless posting actually states schedule (like full-time, part-time, shift). It says Full Time/ On-Site. That indicates full-time schedule. Could we consider that as schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Full Time, which is schedule info. So we could include Schedule section with "Full-time, on-site". However they also have location separate. Might be okay to put schedule info under Schedule. Pay: Salary range given: $185,001 to $198,458.50. Also "Estimated Pay Range: $185,001 USD - $198,458.50 USD". So we can include Pay section. Benefits: The Perks list: comprehensive medical, dental and vision plans, 401(k) with employer match, 529 College Savings Plan, HSA, Life Insurance, Long-Term Disability, Competitive Compensation, Training and development programs, Major offices stocked with snacks and beverages, Collaborative and cool culture, Work-life balance and generous paid time off. So Benefits section. About the role: Could be the company description at start: "Who is Trace3? Trace3 is a leading Transformative IT Authority..." plus culture bullet points. That seems like About the role/company. We'll put that in About the role. Responsibilities: SUMMARY OF ESSENTIAL JOB FUNCTIONS (list of duties). We'll put that. Requirements: Could be CLEARANCE REQUIRMENT? Or maybe "Required Skills and Experience" is more like Requirements. Qualifications maybe education? Not given. We could treat REQUIRED SKILLS AND EXPERIENCE as Requirements. Qualifications maybe not present; we could skip Qualifications if no specific content. Skills: maybe we could separate out skills from requirements? But we have limited sections. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one? But we need to use headings only when posting has real specific content for it. We could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. Qualifications and Skills maybe omitted if not distinct. But we have "Required Skills and Experience" which is definitely skills. Could treat as Skills section. Requirements could be clearance and location? Actually clearance is a requirement. Location is also a requirement. So we could have Requirements section containing clearance and location. Skills section containing the long list of required skills/experience. Thus we have: About the role, Responsibilities, Requirements (clearance, location, contract type), Skills (required skills/experience), Benefits, Pay, Schedule (full-time on-site). That seems reasonable. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections. We need to format lists with

• . For prose, use

  . We need to include the company description and culture bullet points. Those are currently in paragraphs with bullet-like lines but not actual list markup. We should convert them to

  • if they are list items. The text: "Street-Smart - Thriving in Dynamic Times We are flexible and resilient..." etc. It's like a heading then description. Could treat as list items? Might be better to keep as

    for each bullet? The instruction: Use

    • for any list of duties/requirements/benefits. For culture bullet points, they are not duties/requirements/benefits but could be considered list. Safer to treat as
      • for any list. We'll convert each bullet to
      • . Similarly, the "The Perks" list: we need to convert to
        • . Essential job functions: list of duties, each sentence starting with a verb. We'll convert to
          • . Required skills/experience: many items, each sentence. Convert to
            • . Requirements: clearance requirement, location, contract type (W2 Contract or FTE). We'll make list. Schedule: Full-time/On-site. Could be a

              or list. Pay: salary range. Now we need to ensure we don't include boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At the end there is EEO statement, commitment, etc. That's boilerplate; we should remove. Also "Our Commitment" and equal opportunity statement is boilerplate; remove. Also "If you require a reasonable accommodation..." is application instruction? Might be considered boilerplate; remove. Also "***To all recruitment agencies..." is boilerplate; remove. Also "Physical Demands" and "Work Environment" sections: Are they substantive? They are not in our selected headings but could be considered part of Requirements? However they are not explicitly requested headings. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We could decide to include them under Requirements or maybe as separate sections like "Physical Demands" and "Work Environment" but those are not in the allowed headings list (only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we must not create other headings. So we need to fold that content into existing allowed sections if appropriate. Physical demands and work environment could be considered part of Requirements (maybe as "Working Conditions") but not explicitly listed. However we could include them under Requirements as additional details. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must not drop that info. We need to incorporate it somewhere. Since we cannot create new headings, we can put them under Requirements as a list, or maybe under Skills? Probably Requirements is appropriate: includes clearance, location, contract type, physical demands, work environment. We'll add those as list items under Requirements. Similarly, "The Perks" we put under Benefits. Now we need to ensure we don't include duplicated lines. There's duplicate salary range lines: "SALARY RANGE: $185,001 to $198,458.50" and later "Estimated Pay Range: $185,001 USD - $198,458.50 USD". We'll include only once. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

              About the role

              Trace3 is a leading Transformative IT Authority, providing unique technology solutions and consulting services to our clients. Equipped with elite engineering and dynamic innovation, we empower IT executives and their organizations to achieve competitive advantage through a process of Integrate, Automate, Innovate.

              • Street-Smart - Thriving in Dynamic Times: We are flexible and resilient in a fast-changing environment. We continuously innovate and drive constructive change while keeping a focus on the “big picture.” We exercise sound business judgment in making high-quality decisions in a timely and cost-effective manner. We are highly creative and can dig deep within ourselves to find positive solutions to different problems.
              • Juice - The “Stuff” it takes to be a Needle Mover: We get things done and drive results. We lead without a title, empowering others through a can-do attitude. We look forward to the goal, mentally mapping out every checkpoint on the pathway to success, and visualizing what the final destination looks and feels like.
              • Teamwork - Humble, Hungry and Smart: We are humble individuals who understand how our job impacts the company's mission. We treat others with respect, admit mistakes, give credit where it’s due and demonstrate transparency. We “bring the weather” by exhibiting positive leadership and solution-focused thinking. We hug people in their trials, struggles, and failures – not just their success. We appreciate the individuality of the people around us.
              Note: The bullet text originally had dash after heading; we combined. Now Responsibilities:

              Responsibilities

              • Serve as the senior, customer-facing technical lead for datacenter discovery, architecture, design, modernization, and solution shaping engagements.
              • Lead structured workshops with executive sponsors, engineering, infrastructure, platform, cybersecurity, compliance, program-management, and application stakeholders.
              • Translate mission objectives, user and workload requirements, performance targets, availability goals, growth expectations, recovery objectives, and regulatory constraints into actionable architectures.
              • Develop and communicate end-to-end modern datacenter architectures spanning compute, accelerated/GPU compute, network, storage, backup and disaster recovery, virtualization, containers, shared services, observability, and operational management.
              • Design hybrid-cloud solutions integrating on-premises environments with Microsoft Azure Government and Microsoft GCC-High while addressing identity, secure connectivity, data protection, workload placement, governance, compliance, and operational boundaries.
              • Apply Zero Trust Architecture and defense-in-depth principles across identity, access, segmentation, endpoint and workload protection, encryption, key and certificate management, logging, observability, vulnerability management, and security operations.
              • Perform capacity planning, workload placement, performance analysis, resiliency planning, technology evaluation, lifecycle planning, and migration or modernization planning for current and target environments.
              • Produce reference architectures, high-level and detailed designs, diagrams, sizing inputs, bills of materials, implementation roadmaps, controls mappings, assumptions, risks, and decision records.
              • Present complex technical concepts to technical and non-technical audiences; lead architecture reviews, whiteboarding sessions, demonstrations, proposal responses, statements of work, and executive briefings.
              Now Requirements:

              Requirements

              • Top Secret clearance required; TS/SCI preferred.
              • Location: Full Time/ On-Site in Linthicum Heights, MD or Annapolis Junction, MD.
              • This position can be either W2 Contract or FTE.
              • Physical demands: Remain in a stationary position for extended periods; operate a computer, keyboard, and other office equipment using hands and fingers; communicate effectively in person, over the phone, and through electronic means; occasionally move about the office to access files, office equipment, and meeting spaces; lift and/or move up to 15 pounds as needed; maintain specific vision abilities, including close vision and the ability to adjust focus.
              • Work environment: Performed within a secure, classified workspace; must comply with all applicable