Senior Engineer - Cloud & Infra Management

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content. We have role description (role description). We need to parse content: The posting includes role description paragraphs, then "Qualifications Required Qualifications ..." then "Preferred Qualifications ..." then "Other Details" includes compensation and benefits. We need to extract sections: maybe: About the role (role description), Responsibilities (maybe from role description?), Requirements (maybe required qualifications), Qualifications (maybe both required and preferred?), Skills (maybe from qualifications?), Benefits (benefits listed), Pay (compensation range?), Schedule (maybe weekend/holiday requirement). Let's see. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO etc. Remove that. We need to preserve all substantive info. Let's extract: Role Description paragraph(s): "As a CritSit Manager CSM during your shift youll be proactively monitoring all CritSits to determine which CritSits require immediate engagement and to ensure that the CritSit process is being followed and any need of escalation is addressed When engaged the CritSit Manager collaborates with various supportengineering teams following up on case assignment escalates as needed and drives continuous traction towards resolution CritSit Managers effectively engage with customers providing strong collaboration and communication for increased trust and customer satisfaction When managing a CritSit the CritSit Manager will need to be able to share concise status updates to our customers demonstrating progress and any potential blockers To be successful in their role CritSit Managers must be able to demonstrate empathy and deescalate our customers during their most critical support concerns instilling confidence in them and have them realize that the CritSit Manager is an extension of them advocating attention on their concerns from the broader Support organization The CritSit Manager will need to facilitate and broker discussions between the customer members of the Support team and members of the Account team The CritSit Manager will collaborate leverage relationships and influence Engineering teams andor Support teams to identify the right technical resource and ensure the right groups are engaged to resolve highly complex customer issues Identifying systemic issues and flagging process breakdown during the execution of the CritSit Process the CritSit System Effective endtoend technical escalation management driving fast and accurate resolutions for our customers Proactive initiatives to help mitigate and minimize repeating incident themes Demonstrate a strong sense of urgency focus and going above and beyond for our customers Meet or exceed customer expectations on response quality timeliness of responses and overall customer experience Push creative thinking beyond closed boundaries to come up with process improvements and new ways to delight customers" That's a long paragraph. We can split into responsibilities maybe. Qualifications Required Qualifications list: bullet points (but they are sentences). Let's list them: - 3 years of customer service technology industry or related experience - Passion for solving customer issues and advocating for their success in a fast paced highly technical environment - Excellent relationship management customer service and communication skills in variety of forms written live chat conference calls inperson - Strong English written and verbal communication skills (Other languages may be required depending on location and area to be supported) - Excellent judgment decision making skills and the ability to work under continual deadline pressure - Strong sense of empathy and compassion during tense customer interactions - Ability to remain calm composed and articulate when dealing with tough customer situations - Ability to deescalate a customer quickly instill confidence and advocate for them - Ability to influence and build relationships within our broader Support organization - Collaborative team player with strong stakeholder management skills - Ability to manage and work within ambiguity to reach a successful outcome - Strong prioritization and time management - Excellent at multitasking task prioritization - Certifications relevant to the Microsoft products are helpful - Ability to work weekend and public holidays is required Preferred Qualifications: - Inquisitive and proactive actively identifying new problems to resolve - Escalation management - Critical situation handling - Influencing impact experience in working with various groups for common goals Other Details: - Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity. - Benefits/perks listed below may vary depending on the nature of your employment with LTIMindtree (“LTIM”): Benefits And Perks list: - Comprehensive Medical Plan Covering Medical, Dental, Vision - Short Term and Long-Term Disability Coverage - 401(k) Plan with Company match - Life Insurance - Vacation Time, Sick Leave, Paid Holidays - Paid Paternity and Maternity Leave - The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations. Within the range, individual pay is determined by work location and job level and additional factors including job-related skills, experience, and relevant education or training. - Depending on the position offered, other forms of compensation may be provided as part of overall compensation like an annual performance-based bonus, sales incentive pay and other forms of bonus or variable compensation. - Disclaimer: The compensation and benefits information provided herein is accurate as of the date of this posting. - LTIMindtree is an equal opportunity employer ... (boilerplate to remove) We need to remove EEO boilerplate etc. So we drop the equal opportunity paragraph. We need to include sections only if real specific content. Potential sections: - About the role (role description) - Responsibilities (maybe we can extract from role description but we could also just put role description under About the role and not have separate Responsibilities). But we need to follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which sections to include. We have content for About the role (role description). We have Responsibilities (maybe we can extract responsibilities from role description). Could also treat role description as About the role and then Responsibilities as a list of duties. We have Requirements (maybe required qualifications). We have Qualifications (maybe both required and preferred? But we already have Requirements). Could have Skills (maybe communication skills etc). But we can combine. We have Benefits (list). We have Pay (compensation range description). We have Schedule (ability to work weekend and public holidays is required). That's schedule info. Thus we can include sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't create sections with placeholder text. Let's craft content. About the role: a paragraph summarizing role description. Could be the original paragraph but maybe we can keep as is. Responsibilities: list of duties extracted from role description. Let's extract bullet points: - Proactively monitor all CritSits to determine which require immediate engagement and ensure the CritSit process is followed; address escalation needs. - Collaborate with support engineering teams, follow up on case assignments, escalate as needed, drive continuous traction toward resolution. - Engage with customers, providing strong collaboration and communication to increase trust and satisfaction. - Share concise status updates with customers, demonstrating progress and any potential blockers. - Demonstrate empathy and de-escalate customers during critical support concerns, instilling confidence and advocating for them. - Facilitate and broker discussions between customer, support team members, and account team. - Collaborate, leverage relationships, and influence engineering and/or support teams to identify the right technical resource and ensure appropriate groups are engaged to resolve highly complex customer issues. - Identify systemic issues and flag process breakdowns during execution of the CritSit process. - Drive effective end-to-end technical escalation management for fast and accurate resolutions. - Initiate proactive initiatives to mitigate and minimize repeating incident themes. - Demonstrate a strong sense of urgency, focus, and going above and beyond for customers. - Meet or exceed customer expectations on response quality, timeliness, and overall experience. - Push creative thinking beyond closed boundaries to develop process improvements and new ways to delight customers. That seems good. Requirements: list of required qualifications. - 3 years of customer service technology industry or related experience. - Passion for solving customer issues and advocating for their success in a fast-paced, highly technical environment. - Excellent relationship management, customer service, and communication skills in various forms (written, live chat, conference calls, in-person). - Strong English written and verbal communication skills (other languages may be required depending on location). - Excellent judgment and decision-making skills; ability to work under continual deadline pressure. - Strong sense of empathy and compassion during tense customer interactions. - Ability to remain calm, composed, and articulate when dealing with tough customer situations. - Ability to de-escalate a customer quickly, instill confidence, and advocate for them. - Ability to influence and build relationships within the broader Support organization. - Collaborative team player with strong stakeholder management skills. - Ability to manage and work within ambiguity to reach a successful outcome. - Strong prioritization and time management. - Excellent at multitasking and task prioritization. - Certifications relevant to Microsoft products are helpful. - Ability to work weekends and public holidays is required. We could also include "Ability to work weekend and public holidays is required" maybe under Schedule instead. Preferred Qualifications: maybe we can include under Skills or Qualifications? But we have no separate Skills section. Could add a Skills section for preferred qualifications? But we already have Requirements. Could add a "Preferred Qualifications" section but not in the list of allowed headings? The allowed headings list includes Qualifications, Skills, etc. We could put preferred qualifications under Qualifications or Skills. But we already used Requirements for required qualifications. We could have Qualifications section for both required and preferred? But we already used Requirements. Perhaps better to have Requirements (required) and Skills (preferred). Or we could have Qualifications (required) and Skills (preferred). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications if we want, but we need to avoid duplication. Let's assign: - Requirements: required qualifications. - Qualifications: maybe we can include both required and preferred? But we already used Requirements. Could use Qualifications for preferred qualifications. Or we could combine required and preferred under Qualifications and not have Requirements. But we have both sets; better to split. Thus: Requirements: required qualifications list. Qualifications: preferred qualifications list. Skills: maybe we can list specific skills like communication, empathy, de-escalation, stakeholder management, prioritization, multitasking, etc. But that overlaps. Could skip Skills section if we feel it's redundant. However we need to ensure we include all substantive info. If we put preferred qualifications under Qualifications, we still have all info. Skills section could be omitted. But we might want to include Skills for things like "Excellent relationship management customer service and communication skills", "Strong English written and verbal communication", "Ability to influence and build relationships", "Strong prioritization and time management", "Excellent at multitasking task prioritization". Those are already in required qualifications. So we can keep them there. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule. Now Benefits: list as above. Pay: we have compensation description: "Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity." plus "The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations. Within the range, individual pay is determined by work location and job level and additional factors including job-related skills, experience, and relevant education or training." plus "Depending on the position offered, other forms of compensation may be provided as part of overall compensation like an annual performance-based bonus, sales incentive pay and other forms of bonus or variable compensation." plus disclaimer about accuracy (we can keep but not boilerplate). We'll include that as Pay section. Schedule: "Ability to work weekend and public holidays is required." Also maybe shift work? Not mentioned. So we can put that. Now we need to output HTML fragment only, no /. Use

for headings,