Support Specialist - Platform

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule if present. We must not repeat job title. Must not include Job ID etc. Must include only sections with real content. We need to parse the description. First paragraph: "Description As a Level 3 Support Specialist in our Platform team, you will be responsible for providing pro-active technical support and incident management services for Vista’s Cloud, SaaS, and managed service clients globally. As the Platform Support team delivers round the clock service, 365 days a year, from around the globe, there may be a requirement to work outside of normal business hours, or on weekend days. This may on an occasional or ad-hoc basis or scheduled on an on-call or rotating-day basis. Any such after-hours work will be well coordinated and compensated for. At the tier 1 role level we'd expect to see that you are starting to practice some basic leadership capabilities and that you will often need to seek guidance or instruction. Please Note - you will be required to work weekends in this role." That's generic description; we can put as prose under maybe "About the role"? Actually there is a later "About The Role" heading with bullet points. We need to create sections: About the role (the heading after description). Under that we have bullet points: "Proactive Services: Work with proactive platform monitoring technology to identify and address incidents Lead by example and assist with mentoring/training new staff Responding to and resolving Incidents logged for Cloud/VMS/SaaS Working collaboratively with Vista teams globally to resolve incidents Reading and understanding program code to assist with problem solving Using SQL Server and SQL statements to assist with problem solving Using Azure and monitoring tools to assist with problem solving Reading and interpreting error logs Recording all details of support calls into Vista’s issues system Be available on rotation with a cell phone for urgent after-hours support issues Travel domestically or internationally" Then "Platform: Continuously building expertise in the platform and product and acting as a subject matter expert for those product areas within Services Escalated access/support/modifications/config for the platform that aren’t in the user interface or in tooling Becoming proficient in the use of tools for platform monitoring; Work on platform monitoring technology and alerting to grow the maturity of the system Performing technical configuration to support client requests or project work Contributes to support documentation, articles, playbooks, etc..." Thus we can treat these as responsibilities. Then "About Vista" paragraph: description of company. Could be separate section maybe "About Vista" but not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Vista" not in list; we could incorporate into About the role? Probably better to put as a separate paragraph under maybe "About the role" or just as prose before responsibilities. The instruction: use headings for those specific section names; we can also have other prose not under headings? 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 we should follow. Probably we should include About the role heading then responsibilities under it? Actually they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have those headings when content exists. So we need sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule if present. We have Pay: "SALARY - $80,000-$85,000". So we need Pay section. Schedule: Not explicitly given; they mention may need to work outside normal business hours, weekends, on-call rotation. That's schedule info. Could be considered Schedule section. The posting states requirement to work weekends, after-hours, on-call rotation. So we can include Schedule section with that info. Benefits: There's a Benefits paragraph: "Benefits SALARY - $80,000-$85,000 You will be supported to continually learn and improve your tech skills, share knowledge and ideas in the team, and be part of a dynamic and open culture. We have a range of benefits, a strong mentoring & career development focus and fun team events including the Vista Innovation Cup." Actually they included salary in benefits line. But we already have Pay section for salary. Benefits section should contain other benefits: learning, mentoring, career development, fun team events, Vista Innovation Cup, inclusive culture, etc. Requirements: bullet list: "You'll need: 3 years or more experience working in IT support or services type role Experience working with Azure, SaaS, VMS, Cloud (preferred) Microsoft AZ900, AZ104 (preferred) Strong knowledge of SQL Server and networking Undergraduate degree in IT (preferred)". Also maybe "Skills, Knowledge, Abilities and Personal Attributes:" is separate but could go under Skills section. Skills: The paragraph after Requirements: "Skills, Knowledge, Abilities and Personal Attributes: You are a strong team player who create value and builds trust through your contribution and your genuine care in doing your best for your team. You are an effective communicator who builds trust through your open, honest and constructive communication style. You constantly improve the way we work and create value by challenging the status quo. You take action and create value though intelligent risks and prioritising what’s most important for Vista Group You create value by believing in the magic of cinema and seeking to understand the bigger picture of the wider business and industry, to better contribute towards the success of Vista Group". That's skills/attributes. Thus we have sections: About the role (maybe short intro), Responsibilities (the bullet points), Requirements, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include boilerplate like EEO etc. Remove that. We need to preserve all substantive information. Ensure we don't invent. Let's extract content precisely. About the role: The heading "About The Role" then bullet list. We'll put that as

About the role

then maybe a

with items. But the bullet list includes two main categories: Proactive Services and Platform. Could split into two
or just one list with items. We'll keep as list items. Responsibilities: Might be same as About the role? Actually the "About The Role" already describes responsibilities. Could treat that as Responsibilities section. But we already have About the role heading; maybe we should not duplicate. The instruction: use headings for those section names; we can have About the role and Responsibilities both if content distinct. However the posting has "About The Role" with details; there is no separate "Responsibilities" heading. But we could still create Responsibilities section using the same content? Might be duplication. Better to follow the posting: we have About the role content; we can treat that as About the role section. Then we could have Responsibilities section maybe empty? Not allowed. So we should not create Responsibilities if no distinct content. However we have details about proactive services and platform; those are responsibilities. So we could put them under Responsibilities heading and omit About the role? But the posting explicitly has "About The Role" heading. The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid using both if content exists. But we need to avoid filler. If we put same content under both headings, that's duplication. Better to follow the posting: Use About the role heading for the introductory paragraph maybe? Actually after "About The Role" there is a list of duties. So we can treat that as About the role content. Then we could have Responsibilities section maybe summarizing? But we don't have separate responsibilities beyond that. So maybe we just have About the role and skip Responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine About the role and Responsibilities into one section? But we need to follow heading usage. Could we use About the role heading and put the responsibilities list under it? That seems fine: About the role section includes the duties. Then we don't need a separate Responsibilities heading. Thus sections: About the role, Requirements, Skills, Benefits, Pay, Schedule. Now extract content for each. About the role: The paragraph after "About The Role" includes: "Proactive Services: Work with proactive platform monitoring technology to identify and address incidents Lead by example and assist with mentoring/training new staff Responding to and resolving Incidents logged for Cloud/VMS/SaaS Working collaboratively with Vista teams globally to resolve incidents Reading and understanding program code to assist with problem solving Using SQL Server and SQL statements to assist with problem solving Using Azure and monitoring tools to assist with problem solving Reading and interpreting error logs Recording all details of support calls into Vista’s issues system Be available on rotation with a cell phone for urgent after-hours support issues Travel domestically or internationally Platform: Continuously building expertise in the platform and product and acting as a subject matter expert for those product areas within Services Escalated access/support/modifications/config for the platform that aren’t in the user interface or in tooling Becoming proficient in the use of tools for platform monitoring; Work on platform monitoring technology and alerting to grow the maturity of the system Performing technical configuration to support client requests or project work Contributes to support documentation, articles, playbooks, etc..." We need to preserve all details; we can split into list items. Let's list each item: - Work with proactive platform monitoring technology to identify and address incidents - Lead by example and assist with mentoring/training new staff - Responding to and resolving Incidents logged for Cloud/VMS/SaaS - Working collaboratively with Vista teams globally to resolve incidents - Reading and understanding program code to assist with problem solving - Using SQL Server and SQL statements to assist with problem solving - Using Azure and monitoring tools to assist with problem solving - Reading and interpreting error logs - Recording all details of support calls into Vista’s issues system - Be available on rotation with a cell phone for urgent after-hours support issues - Travel domestically or internationally - Continuously building expertise in the platform and product and acting as a subject matter expert for those product areas within Services - Escalated access/support/modifications/config for the platform that aren’t in the user interface or in tooling - Becoming proficient in the use of tools for platform monitoring; Work on platform monitoring technology and alerting to grow the maturity of the system - Performing technical configuration to support client requests or project work - Contributes to support documentation, articles, playbooks, etc... We should keep punctuation as in original but can adjust for list. Now Requirements: list: - 3 years or more experience working in IT support or services type role - Experience working with Azure, SaaS, VMS, Cloud (preferred) - Microsoft AZ900, AZ104 (preferred) - Strong knowledge of SQL Server and networking - Undergraduate degree in IT (preferred) Now Skills: paragraph: "You are a strong team player who create value and builds trust through your contribution and your genuine care in doing your best for your team. You are an effective communicator who builds trust through your open, honest and constructive communication style. You constantly improve the way we work and create value by challenging the status quo. You take action and create value though intelligent risks and prioritising what’s most important for Vista Group You create value by believing in the magic of cinema and seeking to understand the bigger picture of the wider business and industry, to better contribute towards the success of Vista Group" Note there are some minor grammar issues but we keep as is. Now Benefits: The benefits paragraph after "Benefits SALARY - $80,000-$85,000". We'll separate salary into Pay section. Benefits: "You will be supported to continually learn and improve your tech skills, share knowledge and ideas in the team, and be part of a dynamic and open culture. We have a range of benefits, a strong mentoring & career development focus and fun team events including the Vista Innovation Cup. We value inclusivity celebrate diversity