Sr Staff Engineer DevOps

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for lists,

  for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate (EEO, legal, etc). Preserve all substantive info. We need to parse the posting. Key sections: - "A Day in the Life" maybe not needed as heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - About the role: maybe the paragraph after "A Day in the Life" describing the role: "We’re looking for a Senior Staff DevOps Engineer to serve as a senior individual-contributor technical leader on our Platform Engineering & Operations team and scale the infrastructure underneath Lendistry’s lending platform. You’ll drive cloud architecture, security posture, and developer experience across a regulated financial services environment — setting technical direction and mentoring engineers so we can grow without compromising reliability or compliance." - Lendistry: Who We Are: maybe "About the company" but not required heading; could be omitted if not needed. But we could include under "About the role"? Probably not. The instruction says include a section ONLY when posting has real, specific content for it. So we can include "About the role" with that paragraph. - Responsibilities: The "What You’ll Be Doing" section with bullet points (though they are paragraphs). We'll need to extract each bullet as list items. - Requirements / Qualifications: The "Your Areas of Knowledge and Expertise" and "Preferred Expertise". Could combine into Requirements (must-have) and Preferred (nice-to-have). But we have only one Requirements heading allowed? We could have Requirements and Qualifications separate if content exists. The "Your Areas of Knowledge and Expertise" looks like required qualifications. The "Preferred Expertise" is preferred. So we can have Requirements (must) and Qualifications (preferred) or Skills. But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (mandatory) and Qualifications (preferred) maybe. Or Skills separate. We also have Benefits: list under "Why You'll Love Working Here". That's benefits. Pay: "Compensation Range" gives salary range. Schedule: Not mentioned; maybe not include. We must not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to include all details from the posting, except boilerplate. Let's extract content. First, remove boilerplate lines: The initial EEO statement, the lines about unsolicited resumes, MSA, etc. Also the final "ACKNOWLEDGEMENT B.S.D. Capital, Inc. dba Lendistry is an equal employment opportunity employer..." etc. Also the line "Physical Requirements" maybe we should keep? It's substantive about physical requirements; but not under any heading. Could be included under maybe "Requirements"? But it's not a skill. Could be its own section? Not in allowed headings. Could we include under "Requirements"? Probably not appropriate. But we must preserve ALL substantive information. If we cannot create a heading for it, we could embed it as a paragraph under maybe "Requirements" or "Qualifications"? But that might misrepresent. However instruction: "Prefer a few substantive sections over many thin ones." It didn't forbid adding other headings not listed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, but we could use other headings if needed? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we need to preserve all substantive info; physical requirements is substantive. Could we include it under "Requirements" as a bullet? It's not a requirement but a physical demand. Could be placed under "Requirements" as a note. Might be okay. Alternatively, we could create a section "Physical Requirements" as

  but not in the list; risk of being considered not following instruction. Safer to embed under "Requirements" as a paragraph. Now, let's extract each piece. **About the role** paragraph: "We’re looking for a Senior Staff DevOps Engineer to serve as a senior individual-contributor technical leader on our Platform Engineering & Operations team and scale the infrastructure underneath Lendistry’s lending platform. You’ll drive cloud architecture, security posture, and developer experience across a regulated financial services environment — setting technical direction and mentoring engineers so we can grow without compromising reliability or compliance." **Responsibilities** (What You’ll Be Doing): bullet points: - Serve as a senior technical leader and hands-on individual contributor for the Platform Engineering & Operations team, without formal people-management responsibilities. - Mentor cloud and platform engineers, sharing expertise and raising the technical bar across the team. - Contribute to and help shape the technical strategy and roadmap for infrastructure and platform engineering. - Drive cloud architecture and account strategy across development, staging, and production environments for a regulated lending platform. - Drive adoption of infrastructure-as-code and GitOps practices across infrastructure operations. - Own container orchestration across multiple deployable services and cloud accounts. - Experience with CDN/edge/WAF platforms (e.g., Cloudflare, Akamai) for content delivery, DDoS protection, edge security, and traffic/performance optimization. - Own identity management, account-level security posture, secrets management, and KMS key strategy. - Partner with security and compliance teams on audits and vendor/security assessments for a regulated financial services platform. - Own and evolve CI/CD pipelines across multiple repositories, from build through environment-gated production deployments. - Drive best-in-class developer experience and internal tooling for engineering teams. - Contribute to on-call and incident-response practices, including postmortems, for a platform where downtime directly impacts loan funding and servicing. - Evaluate and drive adoption of AI-assisted engineering tools (e.g., Claude Code, GitHub Copilot) across infrastructure workflows, CI/CD pipelines, and internal tooling to accelerate delivery. - Lead the integration of AI-driven observability and operations practices — anomaly detection, predictive alerting, and AI-assisted root-cause analysis — layered on top of existing monitoring stacks. - Own the infrastructure strategy for ML/AI-driven product features (e.g., underwriting and fraud models), including model serving, inference monitoring, and compute scaling for AI workloads. - Champion a builder's mindset toward internal developer platforms — self-service tooling and golden paths that let engineers ship safely without waiting on the platform team. **Requirements** (Your Areas of Knowledge and Expertise): - Bachelor's degree in computer science or a related discipline, or equivalent experience. - 8+ years of experience engineering highly available, enterprise-grade software and platform applications. - 5+ years of hands-on experience in platform engineering across various cloud computing models. - 5+ years of hands-on experience with Kubernetes, container orchestration, Docker, and cloud-native applications. - Substantial hands-on experience with public cloud platform services such as AWS, Azure, and GCP. - Hands-on coding experience in at least two programming languages (Java, JavaScript, Python, Go, or .NET/C#). - Experience with cloud-native application patterns and tools, microservices architectures, and application migrations to any cloud platform. - Strong understanding of infrastructure, virtualization, containers, networking, storage, and monitoring and logging/analytics tools (e.g., Splunk). - Experience with application performance management tools (Splunk, AppDynamics, New Relic, Dynatrace, etc.). - Deep expertise in continuous integration and continuous delivery (CI/CD) tools and processes (e.g., GitHub Actions, Jenkins, Ansible). - Extensive experience with developer tools and open-source technologies. - Deep familiarity with MLOps/LLMOps concepts and the infrastructure needs of AI/ML workloads (GPU or accelerator provisioning, model serving, inference cost and latency management). - Extensive hands-on use of AI coding assistants and agentic developer tools in real engineering workflows, with the judgment to evaluate where they create leverage vs. risk. - Experience with policy-as-code (e.g., OPA, Kyverno) and software supply chain security practices (SBOM generation, artifact signing/provenance) as applied to CI/CD pipelines. **Preferred Expertise** (Qualifications maybe): - 5+ years of experience in cloud infrastructure, DevOps, or Site Reliability Engineering (SRE), with extensive hands-on experience managing AWS production environments at scale. - Proven experience designing, implementing, and operating cloud platforms aligned with the AWS Well-Architected Framework, with a focus on security, reliability, operational excellence, performance efficiency, and cost optimization. - Strong hands-on expertise with AWS core services, including VPC, EC2, IAM, Route 53, CloudFront, S3, networking, security services, and container orchestration platforms such as Amazon EKS or ECS. - Experience implementing and managing infrastructure as code (IaC) using Terraform, AWS CDK, or AWS CloudFormation. - Experience designing and maintaining CI/CD pipelines using tools such as GitHub Actions or Jenkins. - Strong experience in cloud operations, including platform administration, production support, capacity planning, patching, maintenance, and operational excellence for mission-critical AWS environments. - Experience implementing comprehensive monitoring, logging, alerting, and observability solutions using tools such as Amazon CloudWatch, Prometheus, Grafana, and New Relic to ensure platform health, performance, and availability. - Ability to serve as a key technical escalation point during production incidents, leading incident response, root cause analysis (RCA), post-incident reviews, and continuous operational improvements to minimize recurring issues. - Strong understanding of Site Reliability Engineering (SRE) principles, including service reliability, SLAs/SLOs, incident management, change management, and operational readiness. - Strong understanding of cloud cost optimization strategies, including resource right-sizing, Reserved Instances, Savings Plans, storage lifecycle policies, and automation to improve operational efficiency and reduce cloud spend. - Hands-on experience implementing DevSecOps best practices, including automated security scanning, policy validation, compliance checks, secrets management, and vulnerability remediation within CI/CD pipelines. - Strong troubleshooting, problem-solving, and collaboration skills, with the ability to work effectively across engineering, security, operations, and platform teams. - Experience mentoring engineers and driving cloud engineering best practices across cross-functional teams is highly desirable. - Strong awareness of AI model governance and model-risk considerations (explainability, monitoring for drift/bias) in the context of AI-assisted decisioning within a regulated financial services environment. **Benefits** (Why You'll Love Working Here): - Comprehensive Medical, Dental, and Vision Insurance - Generous Paid Time Off - Birthday Day Off - 12 Paid Company Holidays - 401(k) Match - FSA and HSA - Paid Life Insurance - Paid Disability Insurance - Pet Insurance - Employee Assistance Program (EAP) - Professional Development Courses - In Office Provided Snacks and Drinks - Gym Facilities (LA & Tustin/CEC Offices) - In Office Engagement Activities **Pay** (Compensation Range): - The US base salary range for this full-time position is $179,300 - $209,100 annually. - Our salary ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum base salary for new hires for the position across all US locations. - Within the range, individual pay is determined by multiple factors like job-related skills, experience, and state of residence. - Your recruiter can share more about the specific salary range during the interview process. - Please note that the compensation details listed in