Client Technology Manager

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. We need to extract content from posting. Let's parse the posting: - Intro about ECI repeated twice. That's boilerplate? It's about company description. Should we include? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description may be considered boilerplate? It's not navigation/legal/EEO. It's about the company. Might be okay to keep? But we need to preserve all substantive information. The company description is substantive? Possibly yes. However we need to format into sections. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: description of role: "The Client Technology Manager (CTM) is a high impact hands-on leadership role, responsible for delivering our IT managed services to a portfolio of client accounts with the support of a dedicated technical team. The CTM will manage customer relationships and expectations, liaise to internal communities and stakeholders to ensure customer success and spearhead projects to modernize client infrastructure." Also "This role will be hybrid 3 days in office in Dallas, TX." That's schedule? Actually schedule: hybrid 3 days in office. Could be schedule section. - What you will do: list of duties/responsibilities. - Who you are: requirements/qualifications/skills. - Bonus points if you have: additional qualifications/skills. - Benefits: "ECI also offers a competitive compensation package and the range for this role is a maximum of $150,000 annually with flexible PTO, health benefit eligibility the first of the month, life insurance, pet insurance, 401K and so much more!" Also earlier: "ECI’s culture is all about connection..." but that's culture. - Pay: maximum $150,000 annually. - Schedule: hybrid 3 days in office in Dallas, TX. We need to avoid filler like "commensurate with experience". Not present. We must not include duplicated lines. The ECI description appears twice; we should include only once maybe. We must not include application instructions like "If you believe you’d be a great fit and are ready for your best job ever, we’d like to hear from you!!" That's application instruction; remove. Also remove "Love Your Job, Share Your Technology Passion, Create Your Future Here!" etc. Also remove repeated ECI culture paragraph at end. We need to preserve all substantive information: company description, role overview, responsibilities list, qualifications list, bonus points, benefits, pay, schedule. We need to format using

for section headings. Use

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

  for prose. We need to decide which sections to include. Potential sections: - About the role (overview) - Responsibilities (What you will do) - Requirements (Who you are) - Qualifications (maybe same as Requirements? Could combine) - Skills (maybe from bonus points) - Benefits - Pay - Schedule But we should avoid thin sections. Could combine Requirements and Qualifications into one? But instruction says use headings for those specific names if content exists. We can have both if they have distinct content. Let's extract: About the role prose: The Client Technology Manager (CTM) is a high impact hands-on leadership role, responsible for delivering our IT managed services to a portfolio of client accounts with the support of a dedicated technical team. The CTM will manage customer relationships and expectations, liaise to internal communities and stakeholders to ensure customer success and spearhead projects to modernize client infrastructure. Also maybe include hybrid schedule? But schedule separate. Responsibilities list (What you will do): bullet points: - Oversee technology services for a portfolio of ECI clients. - Maintain strong client relationship, serve as trusted strategic advisor leveraging scheduled, ad-hoc, and C-Level strategic meetings. - Develop and maintain a deep functional knowledge of customer’s goals, technical challenges, business objectives, critical infrastructure, and proactively mitigate risk within the environment. - Provide client-based feedback to ECI management on new needs not currently addressed within the ECI Platform with a focus on continuous improvements and enhancements. - Assist with client facing budget forecasting, financial cost analysis reports and documentation. - Engage with client compliance team members to provide security recommendations which cover both business and regulatory needs. - Enable clients using latest technology trends surrounding Information Security and Cloud Services (IaaS/SaaS) - Drive customer satisfaction through support case evaluation, task management and recurring client engagement. - Collaborate cross-functionally to ensure successful delivery of project implementations, migrations, and upgrades, which include mail system migrations, cloud site migrations, new office constructions and new technology deployments. - Hands-on support of client configurations as they pertain to in-house proprietary standards and best practices. - Participate in vendor due-diligence exercises, security reviews, data integrity & availability services. - Manage a team of Field Service Engineers and Senior Systems Engineers in supporting the client portfolios and their distributed workforce. - Be accountable for client technical escalations and subsequent resolutions. Serve as a main point of contact and act as an escalation point to engineers. We need to ensure each bullet is

• . Requirements (Who you are): list: - Recent Advanced knowledge of Microsoft Operating Systems such as Windows Server and Windows 10/11 - Recent Administration experience with Public Cloud platforms with focus in Microsoft 365 and Azure - Recent Experience in technical project management as applied to data/infrastructure migrations, relocations, major system upgrades, and new site deployments. - Extensive experience in administration of e-mail platforms and security integrations such as Exchange Online and Google Workspace - Recent Experience administering VMware vSphere and Hyper-V platforms. - Recent Hands on experience in deployment and management of routing, switching, wireless, and security appliance technologies using vendors such as Cisco, Palo Alto Networks, and Meraki - Proficient in incident response management during security events and high-priority escalations, as well as disaster recovery and business continuity activations Bonus points if you have (could be Skills or Additional Qualifications): - Experience with Managed Service Providers (MSP) - Experience with Microsoft Modern Workplace - Amazon Web Services (AWS) or Google Cloud Platform (GCP) administration experience - Financial Services Industry experience - Certifications in cloud services, network management or cyber-security, such as CCNA, CISSP, Azure Fundamentals and VCP We could treat bonus points as Skills section. Benefits: list: - competitive compensation package - maximum of $150,000 annually (but that's pay) - flexible PTO - health benefit eligibility the first of the month - life insurance - pet insurance - 401K - so much more (maybe vague; but we can include as is) Pay: maximum $150,000 annually. Schedule: hybrid 3 days in office in Dallas, TX. Also maybe include location? Not required heading. We also have company description paragraph about ECI. Could be placed under About the role? Or maybe a separate section "About ECI". But instruction only lists specific headings; we could include About the role as heading and include company description there? The About the role heading expects role overview, not company. But we could include a brief prose about ECI under About the role? Might be okay. Better: we could add a section "About ECI" but not in allowed headings; instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. Safer to stick to those. Thus we can put company description in a

  before any heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray paragraphs before headings. But likely they expect sections with headings. We could include a leading

  for company description, then headings. Let's craft:

  ECI is the leading global provider of managed services, cybersecurity, and business transformation for mid-market financial services organizations across the globe. From its unmatched range of services, ECI provides stability, security and improved business performance, freeing clients from technology concerns and enabling them to focus on running their businesses. More than 1,000 customers worldwide with over $3 trillion of assets under management put their trust in ECI. At ECI, we believe success is driven by passion and purpose. Our passion for technology is only surpassed by our commitment to empowering our employees around the world.

  Then sections. Now ensure we don't repeat duplicated lines. The company description appears twice; we used once. Now check for any other duplicated lines: The Opportunity paragraph repeats earlier; we omitted. Now ensure we don't include boilerplate like "If you believe you’d be a great fit..." etc. We removed. Now produce HTML. We'll need to wrap each section:

  About the role

  ... role overview ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  Maximum of $150,000 annually.

  Schedule

  Hybrid 3 days in office in Dallas, TX.

  Check that we didn't include filler like "and so much more" maybe okay. Now ensure we didn't miss any substantive info: The role overview also includes "Recent Hands-On Technical competencies including Cloud and New Technology experience is required." That's covered in requirements. Also "Please see the 'Who You Are' section below." we omitted. Now check responsibilities list: Did we miss any? Let's re-extract from "What you will do:" paragraph: Oversee technology services for a portfolio of ECI clients. Maintain strong client relationship, serve as trusted strategic advisor leveraging scheduled, ad-hoc, and C-Level strategic meetings. Develop and maintain a deep functional knowledge of customer’s goals, technical challenges, business objectives, critical infrastructure, and proactively mitigate risk within the environment. Provide client-based feedback to ECI management on new needs not currently addressed within the ECI Platform with a focus on continuous improvements and enhancements. Assist with client facing budget forecasting, financial cost analysis reports and documentation. Engage with client compliance team members to provide security recommendations which cover both business and regulatory needs. Enable clients using latest technology trends surrounding Information Security and Cloud Services (IaaS/SaaS) Drive customer satisfaction through support case evaluation, task management and recurring client engagement. Collaborate cross-functionally to ensure successful delivery of project implementations, migrations, and upgrades, which include mail system migrations, cloud site migrations, new office constructions and new technology deployments. Hands-on support of client configurations as they pertain to in-house proprietary standards and best practices. Participate in vendor due-diligence exercises, security reviews, data integrity & availability services. Manage a team of Field Service Engineers and Senior Systems Engineers in supporting the client portfolios and their distributed workforce. Be accountable for client technical escalations and subsequent resolutions. Serve as a main point of contact and act as an escalation point to engineers. All included. Now requirements list: from "Who you are:": Recent Advanced knowledge of Microsoft Operating Systems such