IT Design Architect II

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 that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO, legal, navigation, application instructions, duplicate lines. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: maybe "The Impact You Will Have" and description. Could be "About the role". The posting includes "The Impact You Will Have" paragraph. Also "What You Will Be Doing" is responsibilities. Also "Additional Responsibilities". Also "What You Bring" is qualifications/requirements/skills. Also "What's In It For You" is benefits. Also there is "Department Professional Services Employment Type Full Time Location USA - Remote Workplace type Fully remote Reporting To Ali Abed". This is metadata; we can fold into a short

maybe under a heading? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

with that metadata. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include those with content. We have content for About the role (impact). Responsibilities (What You Will Be Doing + Additional Responsibilities). Requirements/Qualifications/Skills (What You Bring). Benefits (What's In It For You). Pay and Schedule not mentioned, so omit. We must not create sections with placeholder like "commensurate with experience". Not present. We need to use

for each section heading. Use

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

  for prose. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep bullet points as they appear? The posting has paragraphs, not explicit bullet lists. We can convert sentences into

• items if they are list-like. But we need to decide: Use
  • for any list of duties/requirements/benefits. The posting has many sentences separated by line breaks; we can treat each as a list item. However we must not lose info. Could wrap each sentence in
  • . But that may be too granular. Perhaps we can keep paragraphs as

    and only use lists where there are explicit bullet-like items. The instruction: "Use

    • for any list of duties/requirements/benefits". If we don't have explicit list markup, we could still treat each duty as list item. Safer to convert each duty sentence into
    • . But we need to ensure we don't miss any nuance. Let's extract duties: Under "What You Will Be Doing": - Understand and follow “The VC3 Way”. This is our set of standards and processes that produce a predictable result for the client. You must be aware of and maintain our standards - Work with Client Strategic Advisors & Clients to understand client I.T. approach and direction, provide consultation and in-depth expertise to drive VC3 & Industry standards - Develop and maintain a catalog of technical capabilities and the technologies and platforms providing them within VC3; Assist in identifying overlaps and gaps as needed - Understand client business & technical requirements and use them to create value-based proposals, addressing business drivers & pain points – guiding the technical sales cycle towards a technical close & a business win - Manage a response to ‘Proposal Requests’ initiated internally and ensure that the solution proposed is complete and appropriate and results in the best proposal possible - Oversee implementation of technical architecture by producing blueprints (high level review and scope) that guides the implementation of business solutions for client projects - Prepare situation analysis assessments in relation to architecture standards (system reliability, capacity growth, backups, etc.) - Consider impact of solution to VC3 departments operations - Analyze technical requirements to determine platform infrastructure designs, potential issues, and related costs - Participate in Project Implementation Reviews to ensure project scopes are constantly being evaluated for accuracy and current known best practices - Keep abreast of industry standards, software and data innovation, architectural trends, and major technology vendors and leaders - Keep on top of product line changes & update standard labour & product templates - Update standard templates for high level review documents Under "Additional Responsibilities": - Maintain accurate and real time timesheets, record complete and accurate notes of troubleshooting and communication with clients - Receive mentoring and feedback from peers and others - Where appropriate, escalate complicated issues to a more senior resource or other appropriate teams - Actively Participate in Team Huddles, L10 Meetings, One on One Meetings, and any other Team Meetings - Attend monthly training & team meetings as required - Maintain constant and clear communication with clients and colleagues - Collaborate with all VC3 departments to maximize client satisfaction Now "What You Bring" includes qualifications/skills: - Good problem solving and decision-making skills; ability to understand and analyze complex issues - A Bachelor’s degree in Information Technology, Computer Science OR Diploma OR Equivalent experience - At least 5+ years’ direct experience in supporting and maintaining Server, Storage, Network & Backups in SMB environments - Self-motivated, detail orientated, highly organized and able to handle a variety of tasks and responsibilities in an efficient manner with a high level of quality - Very strong interpersonal skills, able to build effective working relationships, solicit co-operation and resolve conflicts with a variety of stakeholders both internally and externally - Team player who can collaborate across disciplines in IT - Excellent communication skills including documenting, visualizing, presenting to a mixed audience, and balancing talking and listening - Skills including collaboration, accountability, results driven, big-picture thinking, building strong relations, and negotiating - Advanced knowledge of Identity, directory, authentication/authorization, single-sign-on, access management, encryption, data privacy, backup, and disaster recovery - Expert knowledge of compute, storage, network, load-balancing, scalability, and availability - Intermediate practical knowledge of cloud platform strategy and implementation including PaaS, SaaS, HaaS and IaaS in Microsoft Azure Cloud Environment - Strong experience determining and addressing non-functional requirements: response times, availability, disaster recovery, scalability, data retention, etc. - Intermediate knowledge of Microsoft Licensing Models for Azure & On-Premises infrastructure - Proven record of architecting and building solutions used in business-critical operations, high availability, proper backup, restore, and disaster recovery implementation Now Benefits "What's In It For You": - Well-being & Support - Caring for our team goes beyond the workday. We offer a range of benefits to support your overall well-being, from mental health and leave support through our Employee and Family Assistance Program, to financial wellness through company-matched 401(k)/RRSP plans. Whether it’s today’s needs or tomorrow’s goals, we’ve got you covered. - Grow with Us – Whether you’re just getting started or ready to take the next step, we are committed to investing in your growth. We offer structured development through our Leadership Academy, monthly learning sessions, mentorship programs, learning reimbursements, internal career fairs, job shadowing, and personalized career-pathing to support internal mobility. - People-First Culture – We live our values, support each other, and create a space where everyone belongs. We have a common goal of doing work that matters, with autonomy, recognition, and a mission to serve those who serve. - Transparent Leadership – From open communication to clear company goals, our leaders are involved, and our managers are here to support your growth every step of the way. - Applicant selected will be subject to a criminal and department of motor vehicles background checks and must meet Criminal Justice Information Systems (CJIS) requirements post-employment Also there is a paragraph about "About VC3, Inc." but that's boilerplate? It's description of company; maybe we can include as "About the role"? Actually "About the role" could be the impact paragraph. The "About VC3, Inc." is more company overview; could be considered boilerplate but it's substantive about company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About VC3, Inc." is not explicitly listed as boilerplate; it's company description. Might be okay to keep as part of "About the role" or separate section like "About the company". But we only have allowed headings list; we could put it under "About the role". However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview into About the role. Thus About the role section could include: "The Impact You Will Have" paragraph plus maybe company overview? But we need to preserve all substantive info; we can include company overview as a paragraph under About the role. Now we need to output HTML fragment only. Structure:

      About the role

      ... impact paragraph ...

      ... company overview ...

      Responsibilities

      • ... each duty ...
      ...

      Requirements

      • ... each requirement/qualification/skill ...
      ...
      Maybe we separate Requirements and Skills? But we have both qualifications and skills mixed. Could split into Requirements (education, experience) and Skills (technical/soft). But we need to avoid thin sections. Could combine into one "Requirements & Skills". But allowed headings include Requirements, Qualifications, Skills. We could use Requirements for education/experience, Skills for technical/soft skills. That seems reasonable. Let's parse: Requirements (education/experience): - A Bachelor’s degree in Information Technology, Computer Science OR Diploma OR Equivalent experience - At least 5+ years’ direct experience in supporting and maintaining Server, Storage, Network & Backups in SMB environments Qualifications (maybe soft skills? but we have many). Could treat Qualifications as the list of soft skills and competencies: problem solving, interpersonal, team player, communication, collaboration, accountability, etc. Skills as technical knowledge: advanced knowledge of identity, etc.; expert knowledge of compute, storage, network; intermediate practical knowledge of cloud platform; strong experience determining non-functional requirements; intermediate knowledge of Microsoft Licensing; proven record of architecting solutions. But we need to ensure we don't create sections with placeholder. All have content. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Now we need to ensure we don't repeat job title heading. Not include. Now we need to strip duplicate lines: there were duplicate "Department Professional Services Employment Type Full Time Location USA - Remote Workplace type Fully remote Reporting To Ali Abed" appears twice; we will include once as a short

      maybe under About the role or separate metadata. Let's include as a

      after About the role maybe. But we should not create a heading for metadata; just a

      . Now we need to ensure we don't include application instructions like "Apply Now", "Register Your Interest", "Learn more about VC3 by visiting our website", etc. Those are boilerplate/application instructions; remove them. Also remove "Thank you for your interest in VC3..." etc. Now we need to preserve all substantive info: the impact paragraph, responsibilities list, requirements/qualifications/skills list, benefits list, metadata paragraph. Now let's craft the HTML. We'll need to escape any HTML special characters like &, but we can keep as is; it's fine. Let's write. First, About the role: Impact paragraph: "The IT Design Architect II ensures infrastructure work is in alignment with the overall Business Architecture framework, IT strategy, strategic drivers, and standards. They work with Client Strategy, PMO, Implementation & Onboarding teams to onboard new client technologies and define the infrastructure of the future, including network, compute, and storage, to deliver highly available, resilient, and responsive infrastructure and optimize business capabilities. Assesses systems requirements and designs against best practices, technology advances, industry standards