Site Reliability Engineer - Production Support

We need to output HTML fragment with sections: About the role? Not present. Responsibilities: Duties and Responsibilities. Requirements and Qualifications: Requirements and Qualifications. Preferred Qualifications: Preferred Qualifications. Desired Skills and Experience: maybe combine? The posting includes "Preferred Qualifications" and "Desired Skills and Experience". We need to include sections only if real specific content. We have content for each. We also have Pay Rate: $60 - $70 per hour. So we need a Pay section. Also Location: Cupertino, CA - Remote Role. Could be Schedule? Not given. So we can include Pay and maybe Location as part of a short p? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is not minor? Could be included in a short p under maybe About the role? But we have no About the role. Could create a short p with location and pay? But they said include Pay/Schedule/Benefits sections only if posting actually states them. Pay is stated, so we need a Pay section. Location is not a heading we have defined; we could include it in a short p under maybe About the role? But we don't have About the role. Could we create a section "About the role"? Not required but we could if we have content. The posting includes location and remote role; we could treat that as part of About the role. However instruction: Prefer a few substantive sections over many thin ones. Could combine location and pay into a "Details" section? But headings list only specific ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use About the role for location and remote info. Use Pay section for pay rate. Use Responsibilities for duties. Use Requirements and Qualifications for requirements. Use Preferred Qualifications for preferred. Use Skills maybe for Desired Skills and Experience? Actually Desired Skills and Experience could go under Skills. Or we could treat Desired Skills and Experience as Skills section. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: location and remote. - Responsibilities: Duties and Responsibilities. - Requirements: Requirements and Qualifications. - Qualifications: Preferred Qualifications? Actually they separate Requirements and Qualifications and Preferred Qualifications. Could combine Requirements and Qualifications as Requirements, and Preferred Qualifications as Qualifications? But they have both headings. We could do Requirements (mandatory) and Qualifications (preferred). Or we could do Requirements and Qualifications as separate sections: Requirements (mandatory) and Qualifications (preferred). The list includes both Requirements and Qualifications as possible headings. So we can do:

Requirements

for mandatory.

Qualifications

for preferred. Then Skills: Desired Skills and Experience could go under Skills. Pay: Pay Rate. We should not include Benefits or Schedule as not present. We must preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points etc. Use

• for any list of duties/requirements/benefits. So we need to convert the paragraphs into lists where appropriate. Let's extract content. About the role: Location: Cupertino, CA - Remote Role. Could phrase: "Location: Cupertino, CA (Remote)". We'll put in

  . Responsibilities: The Duties and Responsibilities paragraph: "Production support / application support / NOC / service reliability / incident management. Screen out: security analysts whose Splunk work is log-based threat detection. Watch service health across production; catch, triage, and drive issues to resolution. Run production support against SLAs and work the incident lifecycle directly with the incident management (IM) team. Monitor and investigate using Splunk (and Datadog, where in play). Support the application stack in cloud and datacenter environments. Non-prod and prod deployments using our in-house CD tool; monitor deployments and roll back / debug when they fail. Keep Git repos current; debug deployment scripts." We need to break into list items. Each sentence could be a list item. We'll keep the content. Requirements (mandatory): The block after "Requirements and Qualifications:" up to "Preferred Qualifications". Let's capture: "Hands-on production support/application support in an SLA-bound environment. Must be able to describe what they personally did during a real incident. Incident management experience: triage, severity assessment, escalation, bridge participation, driving to resolution, RCA follow-up. Direct interaction with an IM team. Splunk is required. They will be asked what commands/searches they run. SOC/production monitoring Troubleshooting depth demonstrable at the command line: log tracing, connection failures, latency, service crashes. Conceptual answers fail here. Linux/Unix fluency. Containerized workloads: Docker + Kubernetes (managing, not just using) Cloud: AWS primary; Azure/AKS acceptable and precedented. Datadog - Naveen called it out as a plus point. New to this team's stack vs. prior reqs in Lighthouse is likely a growing surface. Payments/banking production environment (card networks, Visa/Mastercard, wallets, issuer/acquirer processing). Java application troubleshooting." We need to list each as

• . Some are sentences with colon etc. Qualifications (preferred): The block after "Preferred Qualifications": "CI/CD tooling - Jenkins, specifically, can debug the scripts behind a deployment, not just trigger one. Python and/or shell scripting for automation and runbook work. Load balancers, SSL/TLS and certificate management, DNS, and general network troubleshooting. Config management (Ansible/Chef/Puppet), autoscaling design in Kubernetes. Terraform / infrastructure-as-code exposure. ServiceNow / Jira or equivalent ITSM incident tooling; ITIL familiarity." We'll list each. Skills (Desired Skills and Experience): The long list after "Desired Skills and Experience". It's a comma-separated list of many terms. We need to preserve all. Could break into list items each term? The instruction: Use
  • for any list of duties/requirements/benefits. This is a list of skills. So we should make each item a
  • . The list is long; we need to split by commas. Ensure we keep each term exactly as appears. Let's copy the list: "Production Support, Application Support, Site Reliability Engineering, NOC Operations, Service Health Monitoring, SLA Management, Incident Management, Incident Triage, Severity Assessment, Escalation Management, Incident Bridge Participation, Root Cause Analysis, Splunk, Datadog, SOC Monitoring, Production Monitoring, Command-Line Troubleshooting, Log Tracing, Connection Troubleshooting, Latency Troubleshooting, Service Crash Analysis, Linux, Unix, Docker, Kubernetes, AWS, Azure, AKS, Cloud Infrastructure, Datacenter Environments, Production Deployments, Non-Production Deployments, CI/CD, Continuous Delivery, Deployment Monitoring, Rollbacks, Deployment Script Debugging, Git, Java Application Troubleshooting, Payments Processing, Banking Technology, Card Networks, Visa, Mastercard, Digital Wallets, Issuer Processing, Acquirer Processing, Jenkins, Python, Shell Scripting, Automation, Runbooks, Load Balancers, SSL/TLS, Certificate Management, DNS, Network Troubleshooting, Ansible, Chef, Puppet, Kubernetes Autoscaling, Terraform, Infrastructure as Code, ServiceNow, Jira, ITSM, ITIL" We need to split by commas and trim spaces. Some items have spaces like "Kubernetes Autoscaling". We'll keep as is. Pay: Pay Rate: $60 - $70 per hour. We'll put in

    under Pay section. We must not include boilerplate like "Bayside Solutions, Inc. is not able to sponsor any candidates at this time..." etc. Remove that. Now produce HTML fragment:

    About the role

    Location: Cupertino, CA (Remote)

    Responsibilities

    • Production support / application support / NOC / service reliability / incident management.
    • Screen out: security analysts whose Splunk work is log-based threat detection.
    • Watch service health across production; catch, triage, and drive issues to resolution.
    • Run production support against SLAs and work the incident lifecycle directly with the incident management (IM) team.
    • Monitor and investigate using Splunk (and Datadog, where in play).
    • Support the application stack in cloud and datacenter environments.
    • Non-prod and prod deployments using our in-house CD tool; monitor deployments and roll back / debug when they fail.
    • Keep Git repos current; debug deployment scripts.

    Requirements

    • Hands-on production support/application support in an SLA-bound environment.
    • Must be able to describe what they personally did during a real incident.
    • Incident management experience: triage, severity assessment, escalation, bridge participation, driving to resolution, RCA follow-up. Direct interaction with an IM team.
    • Splunk is required. They will be asked what commands/searches they run.
    • SOC/production monitoring
    • Troubleshooting depth demonstrable at the command line: log tracing, connection failures, latency, service crashes. Conceptual answers fail here.
    • Linux/Unix fluency.
    • Containerized workloads: Docker + Kubernetes (managing, not just using)
    • Cloud: AWS primary; Azure/AKS acceptable and precedented. Datadog - Naveen called it out as a plus point. New to this team's stack vs. prior reqs in Lighthouse is likely a growing surface.
    • Payments/banking production environment (card networks, Visa/Mastercard, wallets, issuer/acquirer processing).
    • Java application troubleshooting.

    Qualifications

    • CI/CD tooling - Jenkins, specifically, can debug the scripts behind a deployment, not just trigger one.
    • Python and/or shell scripting for automation and runbook work.
    • Load balancers, SSL/TLS and certificate management, DNS, and general network troubleshooting.
    • Config management (Ansible/Chef/Puppet), autoscaling design in Kubernetes.
    • Terraform / infrastructure-as-code exposure.
    • ServiceNow / Jira or equivalent ITSM incident tooling; ITIL familiarity.

    Skills

    • Production Support
    • Application Support
    • Site Reliability Engineering
    • NOC Operations
    • Service Health Monitoring
    • SLA Management
    • Incident Management
    • Incident Triage
    • Severity Assessment
    • Escalation Management
    • Incident Bridge Participation
    • Root Cause Analysis
    • Splunk
    • Datadog
    • SOC Monitoring
    • Production Monitoring
    • Command-Line Troubleshooting
    • Log Tracing
    • Connection Troubleshooting
    • Latency Troubleshooting
    • Service Crash Analysis
    • Linux
    • Unix
    • Docker
    • Kubernetes
    • AWS
    • Azure
    • AKS
    • Cloud Infrastructure
    • Datacenter Environments
    • Production Deployments