IT Architecture Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role: The initial paragraph(s) describing the role: "An exciting career awaits you At MPC, we’re committed to being a great place to work – one that welcomes new ideas, encourages diverse perspectives, develops our people, and fosters a collaborative team environment. Position Summary MPC is seeking a hands-on and collaborative Manager of IT Architecture to lead the delivery of architectural strategies across corporate functions and enterprise business systems. This key role will facilitate the design and implementation of scalable, secure, and innovative technology solutions that align with business objectives and support enterprise-wide operational excellence. The successful candidate will drive cross-functional collaboration, promote architectural best practices, and personally review and shape solution designs and make the architectural calls the team escalates. By mentoring a talented architecture team and contributing to the technology roadmap, the Manager of IT Architecture will play a vital role in advancing our organization’s success. The role carries responsibility for the quality and consistency of architecture across finance, HR, supply chain, Enterprise business services, legal, communications, strategy & business development and the platforms that support them. Equally important is developing the people. The successful candidate will coach architects on integration approaches, data authority and non-functional requirements, establish peer review as normal practice so design quality does not depend on who was assigned, and build the practice’s capacity to work independently through patterns, guardrails and reusable decisions. We are looking for someone who can raise the technical standard of a team by working alongside them. Accountable for business results primarily achieved through the work of others. Manages staff, sets direction, and deploys resources. Has responsibility for employee development, performance reviews, pay reviews, and staffing decisions. Accountable for business, functional or operational areas, processes, or programs."
That's a lot of prose. We'll put under About the role
with
containing that. - Responsibilities: The "Key Responsibilities" list. Many bullet points. We'll extract each bullet as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't require all; we include only when posting has real content. We have content for Requirements (education/experience) and Qualifications (maybe same). Could treat them as one section called Requirements (or Qualifications). But we need to decide.
Better: Use Requirements for education/experience, and Qualifications for the "MINIMUM QUALIFICATIONS" (though similar). But that would be duplicate content; we risk repeating same info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we would duplicate the same bullets, which is okay as it's preserving detail but might be considered redundant. However they said do not repeat job title as a heading, but didn't forbid repeating content. But better to avoid duplication; we can combine into one section called Requirements (or Qualifications). Which heading is more appropriate? The posting has "Education and Experience" and "MINIMUM QUALIFICATIONS". Both are qualifications. I'd choose "Qualifications" as heading and include both sets (maybe combine). But we need to avoid filler like "commensurate with experience". Not present.
Thus we can have Qualifications
with - ...
containing:
- Bachelor's degree in Computer Science, Information Technology, Management Information Systems, Engineering, Business, or other computer-related degree required.
- 10+ years of diversified IT experience required.
- 3+ years of experience leading professional staff required.
- (or direct/indirect leadership experience) 3+ years of direct or indirect leadership experience.
We could combine: "3+ years of experience leading professional staff (direct or indirect leadership) required."
But we must not invent or summarize away detail. If we combine, we might lose nuance of "direct or indirect". Safer to list both as separate bullets: one for "3+ years of experience leading professional staff required." and another for "3+ years of direct or indirect leadership experience". However they are essentially same; but we can keep both to preserve detail.
- Skills: The posting lists a set of skills under "Skills". Each bullet preceded by skill name and description. We'll extract each as
Benefits
with- ...
referencing link. However instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So benefits list should be
- . The link can be in a
- Full-time
- Regular . But it's not a list of duties; it's prose. Use
- ... ...
- Bachelor's degree in Computer Science, Information Technology
after list. - Pay: The posting does not mention specific pay/salary. No pay info. So we should NOT create Pay section. - Schedule: No schedule info (full-time mentioned but not schedule details). There's "Employee Group: Full time Employee Subgroup: Regular". That's schedule info? It indicates full-time regular. Could be considered schedule. The instruction: include Schedule section only if posting actually states them. It states "Employee Group: Full time Employee Subgroup: Regular". That's schedule info (full-time). So we could include Schedule section with that detail. However we need to avoid filler like "not specified". This is specified: Full time. So we can include Schedule section with
Full-time regular position.
Or maybe. We must not include Job ID etc. Also remove boilerplate like EEO, legal, etc. We'll strip those. Now construct HTML fragment. We'll have:
About the role
... (the long paragraph)
Responsibilities
Qualifications