Sr. Manager - IT Architecture
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. The posting includes: About Us (company description). Job Summary (role description). Role Description (with subheadings: Leadership & Talent Development, Architecture Strategy & Governance, Business & Technology Alignment, Delivery Enablement, Continuous Improvement). Behaviors and Competencies (list). Skill Level Requirements (list). Other Requirements (list). Pay: "The estimated annual pay range for this position is $165,000 - $205,000 which includes a base salary. The compensation for this position is dependent on job-related knowledge, skills, experience, and market location and, therefore, will vary from individual to individual." That's pay info, but includes "will vary". The instruction says never create Pay section unless posting actually states them, and never emit heading followed by filler/placeholder text like "varies". However they do state a range, but also note it varies. Is that considered filler? The phrase "will vary from individual to individual" is somewhat generic but they gave a range. I think we can include Pay section with the range. The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "varies" is considered filler. But they gave a range plus statement that it varies. Might be considered filler? Safer to omit Pay section? However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." They did state a pay range. So we should include Pay. But we must avoid filler text like "varies". We could include just the range and maybe note that compensation depends on factors, but that is somewhat generic. Might be okay. The instruction says never emit heading followed by filler/placeholder text. If we include the range and also the sentence about varying, that sentence is filler. We could omit that sentence and just keep the range. But we must preserve ALL substantive information; do NOT invent or summarize away detail. The sentence about varying is substantive? It's basically saying compensation depends on factors, which is generic but still part of posting. However it's somewhat boilerplate. Might be considered filler. The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That sentence about compensation varying might be considered boilerplate but it's specific to pay. I'd lean to include Pay section with the range only, and maybe note that it's based on factors? But that might be considered filler. Let's see typical examples: they said never emit heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include the phrase "will vary from individual to individual", that's "varies". So we should not include that sentence. We can keep the range. That is substantive. So Pay section:
Pay
The estimated annual pay range for this position is $165,000 - $205,000 which includes a base salary.
Benefits: They say "Benefits may include, but are not limited to, medical, vision, dental, 401K, and flexible spending." That's specific enough. So we can include Benefits section with a- list.
Schedule: They mention "This position is required to report to the Austin, TX or Somerset, NJ office location on a hybrid basis." That's schedule/location/hybrid. Not exactly schedule but indicates hybrid work. Could be considered Schedule? The instruction says use
- for any list of duties/requirements/benefits. So we can treat each of these as a list under a heading maybe "Responsibilities". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Responsibilities section containing the bullet points from Role Description. Thus we need to extract each duty: Leadership & Talent Development: - Lead, coach, and develop Enterprise Architects and Solution Architects. - Establish team goals, performance expectations, and career development plans. - Manage architecture team capacity, resource planning, and prioritization. - Foster a culture of collaboration, accountability, and continuous improvement. Architecture Strategy & Governance: - Partner with IT leadership to define and evolve architecture standards, principles, and governance practices. - Ensure solutions align with enterprise architecture standards, technology standards, security requirements, and business strategy. - Lead architecture review processes and facilitate architectural decision-making. - Drive consistency in architecture methodologies, deliverables, and practices. Business & Technology Alignment: - Collaborate with business and technology leaders to translate strategic objectives into technology roadmaps and solution approaches. - Guide and participate in technology evaluation, modernization, and transformation initiatives. - Serve as a trusted advisor for architecture-related decisions and technology investments. Delivery Enablement: - Provide oversight and guidance for complex initiatives and major technology investments. - Partner with Product Management, PMO, Engineering, Infrastructure, Security, Quality Assurance, and DevOps teams to support successful solution delivery. - Act as an escalation point for significant architectural challenges and risks. Continuous Improvement: - Advance architecture maturity, governance processes, and organizational effectiveness. - Establish and monitor architecture performance metrics and outcomes. - Champion reusable patterns, standards, and best practices across the enterprise. We can combine these into a single
- list under Responsibilities, or we could have subheadings but instruction only mentions using
- each competency (maybe just the name). But we need to preserve the description? The description after colon explains each. Could be considered substantive. We could keep each as
- with the full sentence. Eg: "Strategic Thinking: Can analyze complex situations, drive organizational transformation, and adapt strategies to changing market conditions." That is a competency description. So we can list them.
- Skill Level Requirements: list of bullet points. Could be under Requirements or Qualifications. The instruction includes Requirements and Qualifications. We could put them under Requirements. Or Qualifications. Since they are requirements, we can use Requirements.
- Other Requirements: list of bullet points (education, experience, certifications, etc.). Could be under Qualifications. We'll decide.
We need to avoid duplication. The Skill Level Requirements and Other Requirements overlap somewhat. We'll keep both as separate sections maybe Requirements and Qualifications.
Let's map:
- About Us:
About Us
...
- About the role (Job Summary):About the role
...
- Responsibilities:Responsibilities
- ... ...
Skills
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- medical
- vision
- dental
- 401K
- flexible spending
Pay
The estimated annual
for section headings, not subheadings. Could still use
for each subheading but that would be many thin sections. Prefer few substantive sections. So we can put all duties under one Responsibilities heading. - Behaviors and Competencies: list of competencies each with description. Could be under Skills or Qualifications? The instruction includes Skills as a possible heading. We could put them under Skills. Each competency is a skill. So we can make a Skills section with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could create a Schedule section for hybrid basis. However they said never create Schedule section unless posting actually states them. It does state hybrid basis. So we can include Schedule.
But we also have About Us section. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About Us is not in the list but could be considered similar to About the role? They gave examples but not exhaustive. We could use About Us as a heading. However they said do NOT repeat the job title as a heading. About Us is fine.
We need to preserve all substantive information. Let's extract:
- About Us: Since 1989, SHI International Corp. has helped organizations change the world through technology. We’ve grown every year since, and today we’re proud to be a $16 billion global provider of IT solutions and services. Over 17,000 Organizations Worldwide Rely On SHI’s Concierge Approach To Help Them Solve What’s Next. But The Heartbeat Of SHI Is Our Employees – All 7,000 Of Them. If You Join Our Team, You’ll Enjoy Our commitment to diversity, as the largest minority- and woman-owned enterprise in the U.S. Continuous professional growth and leadership opportunities. Health, wellness, and financial benefits to offer peace of mind to you and your family. World-class facilities and the technology you need to thrive – in our offices or yours.
We need to keep that as prose (
). Might be long but okay. - Job Summary: The Senior Manager - IT Architecture is responsible for leading SHI's Enterprise Architecture and Solution Architecture functions. This role provides leadership, architectural governance, strategic technology direction, and organizational oversight to ensure technology investments and solutions align with business objectives, enterprise standards, and long-term technology strategy. The Senior Manager partners closely with IT and business leaders to advance architecture maturity, support strategic initiatives, and develop a high-performing team of architects who balance business outcomes with technical excellence. This position combines people leadership, technology strategy, governance, and delivery enablement. This position is required to report to the Austin, TX or Somerset, NJ office location on a hybrid basis. We could treat Job Summary as a section maybe "About the role" or "Job Summary". The instruction says use