Mid/Senior Site Reliability Engineer (US Federal)

for section headings. Use

• for lists. Use

  for prose. We must not repeat job title as heading. Not needed. We must not put Job ID/requisition numbers as headings. We need to decide which sections to include. Potential sections: - About The Team (maybe as a section heading "About the Team") - we have content. - About The Role (maybe as "About the Role") - we have responsibilities list. But the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect those specific headings. However they also say "include a section ONLY when the posting has real, specific content for it". So we can choose which of those headings to use. We could map: - About the role: we have a paragraph describing role (maybe the intro before responsibilities). Could combine with responsibilities. - Responsibilities: the bullet list. - Requirements: citizenship, security clearance, location, maybe basic qualifications. - Qualifications: other qualifications (degree, etc.) - Skills: technical skills list. - Benefits: bonus plan, stock grants, flexible work? Actually flexible work is schedule. - Pay: base pay range. - Schedule: flexible work approach. We need to avoid duplication. Let's extract content. First, About The Team paragraph: "Do what you love. Love what you do. At Workday, we help the world’s largest organizations adapt to what’s next by bringing finance, HR, and planning into a single enterprise cloud. We work hard, and we’re serious about what we do. But we like to have fun, too. We put people first, celebrate diversity, drive innovation, and do good in the communities where we live and work. The SAMBT (Source, Artifact Management & Build Tools) team at Workday relentlessly pursues reliability and availability of build, development and deployment tools by employing a culture of learning, continuous improvement and an engineering focus. The team builds and crafts innovative solutions to support all Workday development teams in their SDLC which includes binary artifact management, software distribution, source control systems and build tools. We support our users with high energy, attention to detail and strong collaboration." We can keep that as prose under About the Team heading? But heading list didn't include About the Team. However we could treat it as "About the role" maybe? But we have separate About The Team and About The Role. The instruction's example headings didn't include About the Team, but we can still use it if we have content. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. But better to stick to those examples to be safe. However we have a lot of team info that could be placed under "About the role" maybe? But that would mix team description with role description. Might be okay. Alternatively we could create a section "About the Team" as heading, it's not prohibited. The instruction didn't forbid other headings, just gave examples. So we can include. But to be safe, we could incorporate team description into "About the role" section as prose. Let's decide: We'll create sections: - About the role (h3) containing the team description and role overview paragraph. - Responsibilities (h3) with ul list. - Requirements (h3) with ul list: citizenship, security clearance, location (DMV), maybe basic qualifications? But basic qualifications are more like requirements. - Qualifications (h3) with ul list: degree, other qualifications (design systems, SCM, Agile, Linux, scripting, reliability engineering, public cloud networking, JFrog Artifactory, DoD 8570 certification). - Skills (h3) with ul list: specific technical skills: configuration management frameworks (Chef, Ansible, Terraform, Docker, Kubernetes), public/cloud (AWS, GCP, Azure), scripting languages (Python, Ruby, Golang), source code management tools, CI/CD, etc. - Benefits (h3) with ul list: Workday Bonus Plan, role-specific commission/bonus, annual refresh stock grants, comprehensive benefits (maybe mention but not detail). Could also include flexible work? But that's schedule. - Pay (h3) with p: base pay range $111,500 - $199,800 USD, note varies by location, bonus, stock. - Schedule (h3) with p: flexible work approach: at least 50% time each quarter in office/field with customers/prospects/partners; remote home office roles can come together for important moments. We must avoid duplication: The basic qualifications appear twice for two levels (Site Reliability Engineer and Senior Site Reliability Engineer). They are similar except years of experience (3+ vs 5+). We could combine them as requirements: "3+ years of experience as a software developer supporting Production Engineering, DevOps or equivalent roles (or 5+ years for senior level)". But we need to preserve all substantive info; we can note both levels. We could list under Requirements: "Site Reliability Engineer: 3+ years experience... Senior Site Reliability Engineer: 5+ years experience..." etc. But we also have Other Qualifications same for both. We could treat Requirements as the mandatory items: citizenship, security clearance, location, basic qualifications (years experience). Qualifications as other qualifications (degree, etc). Skills as technical skills. Let's extract exact phrasing. From About You: "This role will support one or more direct or indirect contracts with the U.S. Federal Government which, due to federal government security requirements, mandates that all Workday personnel working on the contracts be United States citizens (naturalized or native)." "This role may require a security clearance at the TS/SCI w/CI Poly level. Applicants must have the ability to obtain and maintain a U.S. government issued security clearance. An active TS/SCI w/CI Poly is preferred." "May be required to be on site at client locations in the DC, MD, and VA (DMV) area." Then we have "Site Reliability Engineer Basic Qualifications:" list. Then "Other Qualifications:" list. Then "Senior Site Reliability Engineer Basic Qualifications:" list. Then "Other Qualifications:" same list again (duplicate). We'll need to avoid duplication. We need to preserve all substantive info, but we can combine duplicates. Let's capture the bullet points under Basic Qualifications for Site Reliability Engineer: - 3+ years of experience as a software developer supporting Production Engineering, DevOps or equivalent roles - 3+ years of experience in using configuration management frameworks like Chef, Ansible, Terraform, Docker, Kubernetes in Public/Private Cloud (AWS, GCP, Azure, etc.) Other Qualifications (same for both): - Bachelor's or master's degree in computer science, software engineering, or a related field - Experience in designing systems for ease of maintenance, repair, and upgrades, contributing to reduced downtime and increased system longevity. - Proficiency in maintaining and administering source code management (SCM) tools - Proficient with Agile methodologies, SDLC, and CI/CD. - Experience in Linux operating systems and various scripting languages such as - Python, Ruby, Golang - Expertise in applying Reliability Engineering principles to forecast product lifespans, analyze potential failures, and develop maintenance plans for optimal system reliability. - Deep understanding of Public Cloud Networking - JFrog Artifactory administration experience an advantage - Preferred DoD 8570/8140 compliant with at least IAT Level II certification, including a current Computing Environment (CE) credential and one approved specialty certification (e.g., CompTIA CySA+, GICSP, CASP+) Senior Site Reliability Engineer Basic Qualifications: - 5+ years of experience as a software developer supporting Production Engineering, DevOps or equivalent roles - 5+ years of experience in using