Senior Cloud Engineer

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 if posting has real specific content. We need to extract substantive info: job description, duties, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, etc. We need to preserve all substantive information, not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". So we need to include only actual content. Let's parse the posting. Key sections: - Job Description And Duties: Under general direction ... Senior Cloud Engineer ... duties focused in System Engineering domain; may be assigned other domains. Requires current IT Specialist II exam. Headquartered Sacramento, eligible for hybrid telework schedule. Must report to assigned HQ office. Travel expense to/from HQ employee responsibility. Eligibility for telework requires employee reside in CA per Gov Code. Then "Why choose the California State Lottery?" bullet list of reasons. - Then "May consider a Training & Development assignment." etc. - Then details about application, etc (we remove). - Then "Effective July 1, 2025, specific Bargaining Units..." (salary reduction) - maybe not needed? It's about salary reduction but not actual pay. Might be considered pay info? It's about reduction for personal leave. Probably not needed as pay. - Then "The Lottery is less than 30 minutes from all that Downtown Sacramento has to offer. Amenities include an onsite restaurant, free gym, close to the light rail station, electric car charging stations, and free parking!!" - Then "Apply today..." (application instruction) remove. - Then "You will find additional information about the job in the Duty Statement." - Working Conditions: Senior Cloud Engineer will work in fast-paced environment, competing priorities, critical deliverables. Schedule: normal business hours 8am-5pm unless approved. Weekends, long/irregular hours, after-hours, holiday work may be required. Travel: Statewide overnight travel may be required. Other: required to carry Lottery issued cell phone, reachable outside normal business hours. - Minimum Requirements: refer to Class Specification. Not detailed here. - Additional Documents: Job Application Package Checklist, Duty Statement, Position Details: Job Code #: JC-531940 Position #(s): 358-533-1414-005 Working Title: Senior Cloud Engineer Classification: INFORMATION TECHNOLOGY SPECIALIST II $8,625.00 - $11,557.00 A New to State candidates will be hired into the minimum salary of the classification or minimum of alternate range when applicable. # of Positions: 1 Work Location: Sacramento County Telework: Hybrid Job Type: Permanent, Full Time - Department Information: description of California Lottery. - Special Requirements: felony/gambling offense, background investigation, education transcripts, etc. - Application Instructions etc (remove). - Who May Apply etc (remove). - How To Apply etc (remove). - Desirable Qualifications: list of many items. - Benefits: "Benefit information can be found on the CalHR website and the CalPERS website." - Contact Information: truncated. We need to include sections only if there is real specific content. We have: - About the role? Could be the initial description: "Under general direction ... Senior Cloud Engineer...". That's about role. - Responsibilities: duties listed: system engineering domain, may be assigned other domains, etc. Also working conditions: fast-paced environment, schedule, travel, cell phone, reachable. - Requirements: Minimum Requirements (refer to class spec) plus maybe "requires current Information Technology Specialist II exam". Also "headquartered Sacramento, eligible for hybrid telework schedule". Also "must reside in California for telework". Also "travel expense to/from HQ employee responsibility". Also "must be able to report to assigned HQ office". Also "must carry Lottery issued cell phone". Also "must be reachable outside normal business hours". Also "statewide overnight travel may be required". Also "must be able to work flexible hours". Also "must have current IT Specialist II exam". Also "must be able to take exam if needed". Also "must be able to...". Also "must be able to...". Also "must be able to...". Also "must be able to...". Also "must be able to...". We'll include. - Qualifications: maybe the "Desirable Qualifications" list. - Skills: could be extracted from desirable qualifications (experience architecting Azure, knowledge networking, etc). Could be separate Skills section. - Benefits: we have only generic statement "Benefit information can be found on the CalHR website and the CalPERS website." That's not specific benefit details. According to rule: never create Benefits section unless posting actually states them. It does state that benefit info can be found on websites, but not actual benefits. Is that considered stating them? It's a referral, not actual benefit details. Likely we should not create Benefits section because no specific benefits listed. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states that benefit information can be found on websites, but not the benefits themselves. I'd argue it's not stating benefits, so omit Benefits section. - Pay: we have salary range: $8,625.00 - $11,557.00 (monthly?). Also note about new to state hires. Also mention salary reduction effective July 1, 2025 (but that's a reduction). We have specific pay info, so we can include Pay section. - Schedule: we have schedule details: normal business hours 8am-5pm, weekends/irregular/after-hours/holiday may be required. Also hybrid telework eligibility. So we can include Schedule section. We must not include placeholder text like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown. We'll structure:

About the role

... (description)

Responsibilities

• ... items

Requirements

• ... items

Qualifications

• ... desirable qualifications items

Skills

• ... maybe extract from desirable qualifications? Could be overlapping. But we can still list skills like "Experience architecting and deploying cloud-based data solutions using Microsoft Azure", etc. Might duplicate with qualifications. But we can keep Qualifications as desirable qualifications and Skills as technical skills extracted. However risk of duplication. Perhaps better to combine: Qualifications = Minimum Requirements? Actually Minimum Requirements are not detailed. Could treat Requirements as minimum qualifications (exam, telework eligibility, etc). Qualifications as desirable qualifications. Skills could be specific technical skills from desirable qualifications (like Azure, networking, DevOps, etc). We'll do that. We need to ensure we don't invent content. We'll extract exactly. Let's gather content. About the role paragraph: "Under general direction of the Information Technology Services Division (ITSD) Infrastructure Services Information Technology (IT) Manager I; the Information Technology Specialist II will serve as the Senior Cloud Engineer for the California State Lottery (Lottery). The duties for this position are focused in the System Engineering domain; however, work may be assigned in other domains as needed." We could also include the "Why choose the California State Lottery?" bullet list as part of About the role or maybe as a separate section? Not specified headings. Could include under About the role as a list. But we must not invent headings. We'll keep About the role as paragraph plus maybe a list of reasons. Responsibilities: duties: system engineering domain, may be assigned other domains as needed. Also working conditions: fast-paced environment, competing priorities, critical deliverables. Schedule: normal business hours 8am-5pm unless approved; weekends, long/irregular hours, after-hours, holiday work may be required. Travel: statewide overnight travel may be required. Other: carry Lottery issued cell phone; reachable outside normal business hours. We could also include "May consider a Training & Development assignment." but that's maybe not a responsibility. We'll list responsibilities as bullet points. Requirements: bullet points: - Must have a current Information Technology Specialist II exam (or be eligible to take exam if score expired). - Position is headquartered in Sacramento and eligible for hybrid telework schedule. - Must be able to report to assigned headquarters office as assigned. - Travel expense to and from assigned headquarters is the responsibility of the employee. - Eligibility for telework requires employee to reside in California per California Government Code Section 14200. - Must be able to carry a Lottery issued cell phone. - Must be reachable outside of normal business hours. - Must be willing to work statewide overnight travel as required. - Must be able to work flexible hours including weekends, long/irregular hours, after-hours, holiday work as needed. - Must be able to work in a fast-paced environment with competing priorities and critical deliverables. We need to ensure we don't include placeholder. Qualifications (Desirable Qualifications): list from posting: - Experience architecting and deploying cloud-based data solutions using Microsoft Azure. - Knowledge of networking, capacity planning, elasticity, and cost optimization in hybrid environments. - Enterprise experience with Azure Infrastructure management, cloud application development, associated technologies and tools (e.g., Azure VMWare Services, Azure Data factory, Azure App services, Azure Monitor, Redis, SQL Server, Synapse, PowerShell). - Practical experience with business continuity planning and implementation of cloud-based resources using native tools as well as Enterprise data protection solutions across cloud and on-premises environments. - Working knowledge of Enterprise System Development Architecture and Security. - Experience with DevOps practices and version control using Azure DevOps or Git. - Ability to Research, adapt to new technologies, perform problem solving, and resolve challenging technical issues. - Ability to partner with business, program, and IT teams to translate requirements into technical designs. - Experience in mentoring junior engineers and promoting best practices across cross-functional teams. - Strong analytical, problem-solving, and strategic thinking skills. - Excellent communication, documentation, and stakeholder engagement abilities. - Proven capacity to manage multiple priorities and deliver under tight deadlines. - Knowledge and preferably hands-on experience applying Generative Artificial Intelligence (Gen AI) technologies, Large Language Models (LLMs), and AI-assisted automation approaches to improve data engineering, data management, analytics, and software development processes. - Experience leveraging Gen AI tools to automate repetitive data engineering tasks, enhance data quality, accelerate documentation, improve metadata management, or optimize data pipeline development is highly desirable. We'll put each as
• . Skills: maybe we can extract technical skills: Microsoft Azure, networking, capacity planning, elasticity, cost optimization, Azure Infrastructure management, cloud application development, Azure VMWare Services, Azure Data factory, Azure App services, Azure Monitor, Redis, SQL Server, Synapse, PowerShell, business continuity planning, Enterprise data protection, Enterprise System Development Architecture and Security, DevOps practices, version control (Azure DevOps or Git), problem solving, partnering, mentoring, analytical, communication, documentation, stakeholder engagement, managing priorities, Gen AI, LLMs, AI-assisted automation. But that's essentially same as qualifications. Might be redundant but okay. Alternatively we could skip Skills section if it's too similar. But we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Qualifications and Skills into one section? But headings are prescribed; we can omit Skills if not enough distinct content. However we have distinct technical skills list; but it's largely same as qualifications. Might be considered thin. I'd omit Skills section to avoid thin sections. Pay section: include salary range and note about new to state hires and salary reduction? The reduction is about personal