#689 - Engagement Manager

We need to output HTML fragment with sections: About the role? The posting includes description of company and role. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. Let's parse posting: Company description: BlueCloud is a Snowflake Elite Partner... etc. That's about the company, not necessarily "About the role". Could be "About the role" maybe includes description of role. The posting includes "As an Engagement Manager, you will own the delivery..." That's responsibilities. We need sections: About the role (maybe a brief summary), Responsibilities (list), Requirements (maybe experience), Qualifications (maybe similar), Skills (maybe technical fluency), Benefits (maybe "WHY JOIN BLUECLOUD" includes benefits), Pay (none), Schedule (none). We should not create Pay or Schedule if not present. We must preserve all substantive information, not invent. Remove boilerplate: cookie/navigation/legal/EEO etc. There's a paragraph about AI tools in hiring - that's boilerplate? It's about hiring process, maybe we should remove as it's not substantive about role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI tools paragraph is about hiring process, maybe considered boilerplate? It's not EEO but it's about process. Might be considered application instructions? It says "We may use artificial intelligence (AI) tools to support parts of the hiring process...". That's about hiring process, could be considered application instructions. Safer to remove it. Also "Don't be mistaken, this is a challenging career path but also highly rewarding. Are you up for the challenge? If so, stop reading and start applying." That's application encouragement, maybe remove as application instruction. We need to keep substantive content: company description, role description, responsibilities list, ideal candidate requirements, why join. Let's structure:

About the role

As an Engagement Manager at BlueCloud, you will own the delivery of data and AI engagements end-to‑hand, acting as the client’s day‑to‑day point of contact, running status meetings and steering committees, managing risk and scope, and translating technical delivery into business outcomes.

But we need to preserve all substantive information; we can't summarize away detail. Must keep details: "Own full delivery accountability for assigned engagements, from kickoff through close, with no gaps or unaccountable hand-offs", etc. So better to put responsibilities as list under Responsibilities. About the role could be a short paragraph summarizing role: maybe from first paragraph: "As an Engagement Manager, you will own the delivery of BlueCloud’s data and AI engagements end-to-end, working hand-in-hand with client sponsors, architects, and BlueCloud’s delivery teams. You’ll be the client’s day-to-day point of contact—running status meetings and steering committees independently, managing risk and scope, and translating technical delivery into business outcomes the client can act on." That's substantive. Responsibilities: list each bullet from "AS AN ENGAGEMENT MANAGER, YOU WILL:" block. Requirements: maybe from "OUR IDEAL ENGAGEMENT MANAGER WILL HAVE:" block. Qualifications: maybe same as requirements? Could combine but we need separate sections only if content. Could put Requirements as experience, Qualifications as education? Not present. Could skip Qualifications if no distinct content. But we need to avoid empty sections. Skills: maybe technical fluency, presentation, communication skills. Could extract from responsibilities and ideal candidate. Benefits: from "WHY JOIN BLUECLOUD:" block. Pay: none -> omit. Schedule: none -> omit. We must not repeat job title as heading. Now produce HTML fragment. Let's extract responsibilities list exactly: - Own full delivery accountability for assigned engagements, from kickoff through close, with no gaps or unaccountable hand-offs - Run client status meetings, steering committees, and stakeholder check-ins independently, without needing escalation to an architect or sponsor - Bring real technical fluency to each engagement—understanding delivery components well enough to speak credibly with clients and architects - Communicate proactively and clearly with internal teams and client stakeholders on status, issues, and blockers - Document risks, issues, dependencies, and action items continuously, and drive them to resolution - Maintain a change log covering scope, timeline, resource, and budget changes, and drive stakeholder sign-off - Partner with client sponsors and IT stakeholders to position BlueCloud as a trusted partner—not just a vendor - Take on complex, large-scale engagements, including programs spanning multiple concurrent project teams - Act as Product Owner when needed—leading business requirements capture and partnering with architects to shape user stories - Mentor and guide other Engagement Managers, contributing to the evolution of BlueCloud’s Engagement Management practice - Lead project QA across engagements, ensuring delivery standards are upheld - Proactively surface risks and red flags before escalation, while building strong rapport across BlueCloud and client teams Now requirements list from "OUR IDEAL ENGAGEMENT MANAGER WILL HAVE:": - 7+ years of experience owning delivery for complex, technical, client-facing engagements (or similar roles) - Direct experience in data engineering, cloud data platforms, Snowflake, or comparable enterprise data/BI/cloud technology stacks - Proven ability to independently run client-facing meetings and steering committees without executive or sponsor support - Demonstrated success managing multiple complex projects simultaneously, including ownership of risk logs, change logs, and documentation - Strong presentation and communication skills, with the ability to translate technical delivery into insights for both technical and executive audiences - Bonus: experience acting as a Product Owner, leading business requirements, or mentoring delivery professionals Now benefits from "WHY JOIN BLUECLOUD:": - Work on high-impact data and AI engagements as part of a Snowflake Elite Partner - Own real client relationships and engagements from day one—not just tickets - Join a delivery team built on ownership, technical credibility, and trusted-advisor relationships - Learn from an experienced, high-performing team of delivery professionals - We are looking for someone who is experienced in building lasting relationships and is passionate about making meaningful contributions to our team. - Don't be mistaken, this is a challenging career path but also highly rewarding. (maybe remove as application encouragement) Might be considered boilerplate? It's more motivational. Could keep as part of benefits? It's not a benefit per se. Might be considered fluff. Safer to keep only substantive benefits: first four bullets. The last two are more motivational; could be considered filler. I'd keep them as they are part of why join? Might be okay. But instruction: never emit a heading followed by filler/placeholder text. These are not filler but motivational. Might be okay. However they are somewhat generic. I'd include them as part of benefits list. Now About the role paragraph: we can use the first two sentences: "As an Engagement Manager, you will own the delivery of BlueCloud’s data and AI engagements end-to-end, working hand-in-hand with client sponsors, architects, and BlueCloud’s delivery teams. You’ll be the client’s day-to-day point of contact—running status meetings and steering committees independently, managing risk and scope, and translating technical delivery into business outcomes the client can act on." That's substantive. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We'll have sections: About the role, Responsibilities, Requirements, Benefits. Possibly Skills? Could extract skills from responsibilities and requirements: technical fluency, presentation/communication, ability to translate technical delivery, etc. But we already have those in responsibilities/requirements. Could create Skills section summarizing: technical fluency, presentation and communication skills, ability to translate technical delivery, risk management, change management, stakeholder management, product ownership, mentoring, QA. But that might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if its content is covered elsewhere. However we need to include a section only when posting has real specific content for it. The posting does mention skills implicitly but not a dedicated "Skills" heading. So we should not create a Skills section. Qualifications: similar to Requirements; we could treat Requirements as qualifications. But we have both headings; we could put Requirements as experience, Qualifications as education/certifications (none). So better to omit Qualifications. Thus sections: About the role, Responsibilities, Requirements, Benefits. Now produce HTML. Ensure no extra whitespace? Just output. Let's craft:

  About the role

  As an Engagement Manager, you will own the delivery of BlueCloud’s data and AI engagements end-to-end, working hand-in-hand with client sponsors, architects, and BlueCloud’s delivery teams. You’ll be the client’s day-to-day point of contact—running status meetings and steering committees independently, managing risk and scope, and translating technical delivery into business outcomes the client can act on.

  Responsibilities

  • Own full delivery accountability for assigned engagements, from kickoff through close, with no gaps or unaccountable hand-offs
  • Run client status meetings, steering committees, and stakeholder check-ins independently, without needing escalation to an architect or sponsor
  • Bring real technical fluency to each engagement—understanding delivery components well enough to speak credibly with clients and architects
  • Communicate proactively and clearly with internal teams and client stakeholders on status, issues, and blockers
  • Document risks, issues, dependencies, and action items continuously, and drive them to resolution
  • Maintain a change log covering scope, timeline, resource, and budget changes, and drive stakeholder sign-off
  • Partner with client sponsors and IT stakeholders to position BlueCloud as a trusted partner—not just a vendor
  • Take on complex, large-scale engagements, including programs spanning multiple concurrent project teams
  • Act as Product Owner when needed—leading business requirements capture and partnering with architects to shape user stories
  • Mentor and guide other Engagement Managers, contributing to the evolution of BlueCloud’s Engagement Management practice
  • Lead project QA across engagements, ensuring delivery standards are upheld
  • Proactively surface risks and red flags before escalation, while building strong rapport across BlueCloud and client teams

  Requirements

  • 7+ years of experience owning delivery for complex, technical, client-facing engagements (or similar roles)
  • Direct experience in data engineering, cloud data platforms, Snowflake, or comparable enterprise data/BI/cloud technology stacks
  • Proven ability to independently run client-facing meetings and steering committees without executive or sponsor support
  • Demonstrated success managing multiple complex projects simultaneously, including ownership of risk logs, change logs, and documentation
  • Strong presentation and communication skills, with the ability to translate technical delivery into insights for both technical and executive audiences
  • Bonus: experience acting as a Product Owner, leading business requirements, or mentoring delivery professionals

  Benefits

  • Work on high-impact data and AI engagements as part of a Snowflake Elite Partner
  • Own real client relationships and engagements from day one—not just tickets
  • Join a delivery team built on ownership, technical credibility, and trusted-advisor relationships
  • Learn from an experienced, high-performing team of delivery professionals
  • We are looking for someone who is experienced in building lasting relationships and is passionate about making meaningful contributions to our team.
  • Don't be mistaken, this is a challenging career path but also highly rewarding.
  Check for any duplicated lines: none. Check for boilerplate removed: we removed AI tools paragraph and "stop reading and start applying". Good. Now output only HTML fragment.