Staff DevOps Engineer
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However the instruction says: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should map content to those standard headings where appropriate. But we can also use other headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect we use those headings when applicable. However we must not repeat the job title as a heading. We need to decide which sections map.
We have content: "A Day in the Life" could be considered About the role? Could map to About the role. "Lendistry: Who We Are" maybe About the company, not required. Could be omitted? But we need to preserve ALL substantive information; we cannot drop company description. However we could incorporate it into About the role section? The instruction says we should not invent headings; we should use those standard headings when possible. But we can also include other headings if needed? 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 suggests using those. Probably we should map content to those categories: About the role (intro + company), Responsibilities (What You’ll Be Doing), Requirements/Qualifications (Your Areas of Knowledge and Expertise + Preferred Expertise), Skills (maybe part of requirements), Benefits (Why You'll Love Working Here), Pay (Compensation Range), Schedule (maybe not present; we have Physical Requirements, not schedule). Since schedule not present, we should not create a Schedule section. Physical Requirements could be placed under maybe a separate section? Not in list. Could we omit? We must preserve ALL substantive information; we cannot drop Physical Requirements. But we could incorporate it into About the role or Responsibilities? Probably better to create a section with heading "Physical Requirements" using even though not in the example list; the instruction says use for section headings (e.g. ...). It doesn't say we cannot use other headings; it's just examples. So we can use Physical Requirements as heading.
We must not include boilerplate like EEO statements, etc. We need to remove all that. Also remove duplicated lines, navigation, cookie, legal, EEO, scam-warning, application instructions. So we strip the initial EEO paragraph, the recruiter policy, etc. Also remove the final acknowledgement EEO paragraph.
We need to keep: "A Day in the Life" paragraph, "Lendistry: Who We Are" paragraph, "What You’ll Be Doing" with its subpoints (collaboration & mentorship, cloud architecture..., etc). Then "Your Areas of Knowledge and Expertise" list, "Preferred Expertise" list, "Why You'll Love Working Here" list of benefits, "Compensation Range" paragraph, "Physical Requirements" paragraph.
We need to format lists with - . For prose use
. For subheadings inside What You’ll Be Doing we could treat each bold heading as a subsection? The instruction: Use
for section headings. So each major section gets . Inside we can have
and
. For subheadings like "Collaboration & Mentorship" we could either treat as with bold or maybe as
? But we only allowed for section headings; we could still use or inside . Safer to keep as
with bold text using . But we must not invent headings that are not needed. We'll keep them as ...: then description.
Similarly for Preferred Expertise we could just list items.
We need to preserve all specifics.
Let's extract content.
First, after removing boilerplate, we have:
"A Day in the Life We’re looking for a Staff Engineer DevOps to join our Platform Engineering & Operations team as a hands-on individual-contributor engineer, helping to build and maintain the infrastructure underneath Lendistry’s lending platform. You’ll work on cloud architecture, security posture, and developer experience across a regulated financial services environment — and help support fellow engineers so we can grow without compromising reliability or compliance."
Then "Lendistry: Who We Are We’re proud to be the nation’s largest minority-led, tech-savvy lender for small businesses and commercial real estate. As a certified Community Development Financial Institution (CDFI) and Community Development Entity (CDE), our mission is all about creating economic opportunities and fueling growth for small business owners and their communities. Join us as we pave the way with innovative financing and financial education!"
Then "What You’ll Be Doing Collaboration & Mentorship Work as a hands-on individual contributor engineer on the Platform Engineering & Operations team, without formal people-management responsibilities.Help mentor junior engineers on the team, sharing knowledge as they grow their skills.Provide input and feedback on the technical roadmap for infrastructure and platform engineering. Cloud Architecture & Infrastructure Support cloud architecture and account management across development, staging, and production environments for a regulated lending platform.Help implement and maintain infrastructure-as-code and GitOps practices across infrastructure operations.Support container orchestration across multiple deployable services and cloud accounts. Security, Identity & Compliance Support identity management, account-level security posture, secrets management, and KMS key practices.Assist security and compliance teams with audits and vendor/security assessments for a regulated financial services platform. Developer Experience & CI/CD Maintain and improve CI/CD pipelines across multiple repositories, from build through environment-gated production deployments.Support developer experience and internal tooling improvements for engineering teams. Reliability & Incident Management Participate in on-call and incident-response practices, including postmortems, for a platform where downtime directly impacts loan funding and servicing. AI-Native Platform Engineering Explore and help integrate AI-assisted engineering tools (e.g., Claude Code, GitHub Copilot) into infrastructure workflows, CI/CD pipelines, and internal tooling.Support the adoption of AI-driven observability practices — anomaly detection, predictive alerting, and AI-assisted root-cause analysis — layered on top of existing monitoring stacks.Help support the infrastructure needs of ML/AI-driven product features (e.g., underwriting and fraud models), including model serving, inference monitoring, and compute scaling for AI workloads.Contribute to self-service internal tooling and golden paths that make it easier for engineers to ship safely."
Then "Your Areas of Knowledge and Expertise Bachelor's degree in computer science or a related discipline, or equivalent experience.4+ years of experience engineering highly available, enterprise-grade software and platform applications.2+ years of hands-on experience in platform engineering across various cloud computing models.2+ 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.Working 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.).Experience with continuous integration and continuous delivery (CI/CD) tools and processes (e.g., GitHub Actions, Jenkins, Ansible).Experience with developer tools and open-source technologies.Working familiarity with MLOps/LLMOps concepts and the infrastructure needs of AI/ML workloads (GPU or accelerator provisioning, model serving, inference cost and latency management).Hands-on use of AI coding assistants and developer tools (e.g., Claude Code, GitHub Copilot) in real engineering workflows.Familiarity 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."
Then "Preferred Expertise 2+ years of experience in cloud infrastructure, DevOps, or Site Reliability Engineering (SRE), with hands-on experience in AWS production environments.Experience supporting cloud platforms aligned with the AWS Well-Architected Framework, with an interest in security, reliability, operational excellence, performance efficiency, and cost optimization.Hands-on experience 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 working with infrastructure as code (IaC) using Terraform, AWS CDK, or AWS CloudFormation.Experience supporting CI/CD pipelines using tools such as GitHub Actions or Jenkins.Experience with cloud operations, including platform administration, production support, capacity planning, patching, and maintenance for AWS environments.Experience working with monitoring, logging, alerting, and observability tools such as Amazon CloudWatch, Prometheus, Grafana, and New Relic to support platform health, performance, and availability.Ability to participate as a technical escalation point during production incidents, supporting incident response, root cause analysis (RCA), and post-incident reviews.Familiarity with Site Reliability Engineering (SRE) principles, including service reliability, SLAs/SLOs, incident management, change management, and operational readiness.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.Experience supporting DevSecOps practices, including automated security scanning, policy validation, compliance checks, secrets management, and vulnerability remediation within CI/CD pipelines.Good troubleshooting, problem-solving, and collaboration skills, with the ability to work effectively across engineering, security, operations, and platform teams.Interest in mentoring junior engineers and contributing to cloud engineering best practices is a plus.Interest in 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."
Then "Why You'll Love Working Here Comprehensive Medical, Dental, and Vision InsuranceGenerous Paid Time OffBirthday Day Off12 Paid Company Holidays401(k) MatchFSA and HSAPaid Life Insurance Paid Disability InsurancePet InsuranceEmployee Assistance Program (EAP)Professional Development CoursesIn Office Provided Snacks and DrinksGym Facilities (LA & Tustin/CEC Offices)In Office Engagement Activities"
Then "Compensation Range The US base salary range for this full-time position is $132,300 - $152,300 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 US role postings reflect the base salary only, and do not include any variable compensation elements."
Then "Physical Requirements This is a stationary position that requires frequent sitting (approximately 95%), repetitive wrist motions, grasping, speaking, listening, close vision, and the ability to adjust focus. It also may require occasional standing, lifting, carrying of 20lbs or less, walking, kneeling, bending/stooping, twisting, pulling/pushing,
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect we use those headings when applicable. However we must not repeat the job title as a heading. We need to decide which sections map.
We have content: "A Day in the Life" could be considered About the role? Could map to About the role. "Lendistry: Who We Are" maybe About the company, not required. Could be omitted? But we need to preserve ALL substantive information; we cannot drop company description. However we could incorporate it into About the role section? The instruction says we should not invent headings; we should use those standard headings when possible. But we can also include other headings if needed? 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 suggests using those. Probably we should map content to those categories: About the role (intro + company), Responsibilities (What You’ll Be Doing), Requirements/Qualifications (Your Areas of Knowledge and Expertise + Preferred Expertise), Skills (maybe part of requirements), Benefits (Why You'll Love Working Here), Pay (Compensation Range), Schedule (maybe not present; we have Physical Requirements, not schedule). Since schedule not present, we should not create a Schedule section. Physical Requirements could be placed under maybe a separate section? Not in list. Could we omit? We must preserve ALL substantive information; we cannot drop Physical Requirements. But we could incorporate it into About the role or Responsibilities? Probably better to create a section with heading "Physical Requirements" using even though not in the example list; the instruction says use for section headings (e.g. ...). It doesn't say we cannot use other headings; it's just examples. So we can use Physical Requirements as heading.
We must not include boilerplate like EEO statements, etc. We need to remove all that. Also remove duplicated lines, navigation, cookie, legal, EEO, scam-warning, application instructions. So we strip the initial EEO paragraph, the recruiter policy, etc. Also remove the final acknowledgement EEO paragraph.
We need to keep: "A Day in the Life" paragraph, "Lendistry: Who We Are" paragraph, "What You’ll Be Doing" with its subpoints (collaboration & mentorship, cloud architecture..., etc). Then "Your Areas of Knowledge and Expertise" list, "Preferred Expertise" list, "Why You'll Love Working Here" list of benefits, "Compensation Range" paragraph, "Physical Requirements" paragraph.
We need to format lists with - . For prose use
. For subheadings inside What You’ll Be Doing we could treat each bold heading as a subsection? The instruction: Use
for section headings. So each major section gets . Inside we can have
and
. For subheadings like "Collaboration & Mentorship" we could either treat as with bold or maybe as
? But we only allowed for section headings; we could still use or inside . Safer to keep as
with bold text using . But we must not invent headings that are not needed. We'll keep them as ...: then description.
Similarly for Preferred Expertise we could just list items.
We need to preserve all specifics.
Let's extract content.
First, after removing boilerplate, we have:
"A Day in the Life We’re looking for a Staff Engineer DevOps to join our Platform Engineering & Operations team as a hands-on individual-contributor engineer, helping to build and maintain the infrastructure underneath Lendistry’s lending platform. You’ll work on cloud architecture, security posture, and developer experience across a regulated financial services environment — and help support fellow engineers so we can grow without compromising reliability or compliance."
Then "Lendistry: Who We Are We’re proud to be the nation’s largest minority-led, tech-savvy lender for small businesses and commercial real estate. As a certified Community Development Financial Institution (CDFI) and Community Development Entity (CDE), our mission is all about creating economic opportunities and fueling growth for small business owners and their communities. Join us as we pave the way with innovative financing and financial education!"
Then "What You’ll Be Doing Collaboration & Mentorship Work as a hands-on individual contributor engineer on the Platform Engineering & Operations team, without formal people-management responsibilities.Help mentor junior engineers on the team, sharing knowledge as they grow their skills.Provide input and feedback on the technical roadmap for infrastructure and platform engineering. Cloud Architecture & Infrastructure Support cloud architecture and account management across development, staging, and production environments for a regulated lending platform.Help implement and maintain infrastructure-as-code and GitOps practices across infrastructure operations.Support container orchestration across multiple deployable services and cloud accounts. Security, Identity & Compliance Support identity management, account-level security posture, secrets management, and KMS key practices.Assist security and compliance teams with audits and vendor/security assessments for a regulated financial services platform. Developer Experience & CI/CD Maintain and improve CI/CD pipelines across multiple repositories, from build through environment-gated production deployments.Support developer experience and internal tooling improvements for engineering teams. Reliability & Incident Management Participate in on-call and incident-response practices, including postmortems, for a platform where downtime directly impacts loan funding and servicing. AI-Native Platform Engineering Explore and help integrate AI-assisted engineering tools (e.g., Claude Code, GitHub Copilot) into infrastructure workflows, CI/CD pipelines, and internal tooling.Support the adoption of AI-driven observability practices — anomaly detection, predictive alerting, and AI-assisted root-cause analysis — layered on top of existing monitoring stacks.Help support the infrastructure needs of ML/AI-driven product features (e.g., underwriting and fraud models), including model serving, inference monitoring, and compute scaling for AI workloads.Contribute to self-service internal tooling and golden paths that make it easier for engineers to ship safely."
Then "Your Areas of Knowledge and Expertise Bachelor's degree in computer science or a related discipline, or equivalent experience.4+ years of experience engineering highly available, enterprise-grade software and platform applications.2+ years of hands-on experience in platform engineering across various cloud computing models.2+ 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.Working 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.).Experience with continuous integration and continuous delivery (CI/CD) tools and processes (e.g., GitHub Actions, Jenkins, Ansible).Experience with developer tools and open-source technologies.Working familiarity with MLOps/LLMOps concepts and the infrastructure needs of AI/ML workloads (GPU or accelerator provisioning, model serving, inference cost and latency management).Hands-on use of AI coding assistants and developer tools (e.g., Claude Code, GitHub Copilot) in real engineering workflows.Familiarity 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."
Then "Preferred Expertise 2+ years of experience in cloud infrastructure, DevOps, or Site Reliability Engineering (SRE), with hands-on experience in AWS production environments.Experience supporting cloud platforms aligned with the AWS Well-Architected Framework, with an interest in security, reliability, operational excellence, performance efficiency, and cost optimization.Hands-on experience 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 working with infrastructure as code (IaC) using Terraform, AWS CDK, or AWS CloudFormation.Experience supporting CI/CD pipelines using tools such as GitHub Actions or Jenkins.Experience with cloud operations, including platform administration, production support, capacity planning, patching, and maintenance for AWS environments.Experience working with monitoring, logging, alerting, and observability tools such as Amazon CloudWatch, Prometheus, Grafana, and New Relic to support platform health, performance, and availability.Ability to participate as a technical escalation point during production incidents, supporting incident response, root cause analysis (RCA), and post-incident reviews.Familiarity with Site Reliability Engineering (SRE) principles, including service reliability, SLAs/SLOs, incident management, change management, and operational readiness.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.Experience supporting DevSecOps practices, including automated security scanning, policy validation, compliance checks, secrets management, and vulnerability remediation within CI/CD pipelines.Good troubleshooting, problem-solving, and collaboration skills, with the ability to work effectively across engineering, security, operations, and platform teams.Interest in mentoring junior engineers and contributing to cloud engineering best practices is a plus.Interest in 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."
Then "Why You'll Love Working Here Comprehensive Medical, Dental, and Vision InsuranceGenerous Paid Time OffBirthday Day Off12 Paid Company Holidays401(k) MatchFSA and HSAPaid Life Insurance Paid Disability InsurancePet InsuranceEmployee Assistance Program (EAP)Professional Development CoursesIn Office Provided Snacks and DrinksGym Facilities (LA & Tustin/CEC Offices)In Office Engagement Activities"
Then "Compensation Range The US base salary range for this full-time position is $132,300 - $152,300 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 US role postings reflect the base salary only, and do not include any variable compensation elements."
Then "Physical Requirements This is a stationary position that requires frequent sitting (approximately 95%), repetitive wrist motions, grasping, speaking, listening, close vision, and the ability to adjust focus. It also may require occasional standing, lifting, carrying of 20lbs or less, walking, kneeling, bending/stooping, twisting, pulling/pushing,
even though not in the example list; the instruction says use for section headings (e.g. ...). It doesn't say we cannot use other headings; it's just examples. So we can use Physical Requirements as heading.
We must not include boilerplate like EEO statements, etc. We need to remove all that. Also remove duplicated lines, navigation, cookie, legal, EEO, scam-warning, application instructions. So we strip the initial EEO paragraph, the recruiter policy, etc. Also remove the final acknowledgement EEO paragraph.
We need to keep: "A Day in the Life" paragraph, "Lendistry: Who We Are" paragraph, "What You’ll Be Doing" with its subpoints (collaboration & mentorship, cloud architecture..., etc). Then "Your Areas of Knowledge and Expertise" list, "Preferred Expertise" list, "Why You'll Love Working Here" list of benefits, "Compensation Range" paragraph, "Physical Requirements" paragraph.
We need to format lists with - . For prose use
. For subheadings inside What You’ll Be Doing we could treat each bold heading as a subsection? The instruction: Use
for section headings. So each major section gets . Inside we can have
and
. For subheadings like "Collaboration & Mentorship" we could either treat as with bold or maybe as
? But we only allowed for section headings; we could still use or inside . Safer to keep as
with bold text using . But we must not invent headings that are not needed. We'll keep them as ...: then description.
Similarly for Preferred Expertise we could just list items.
We need to preserve all specifics.
Let's extract content.
First, after removing boilerplate, we have:
"A Day in the Life We’re looking for a Staff Engineer DevOps to join our Platform Engineering & Operations team as a hands-on individual-contributor engineer, helping to build and maintain the infrastructure underneath Lendistry’s lending platform. You’ll work on cloud architecture, security posture, and developer experience across a regulated financial services environment — and help support fellow engineers so we can grow without compromising reliability or compliance."
Then "Lendistry: Who We Are We’re proud to be the nation’s largest minority-led, tech-savvy lender for small businesses and commercial real estate. As a certified Community Development Financial Institution (CDFI) and Community Development Entity (CDE), our mission is all about creating economic opportunities and fueling growth for small business owners and their communities. Join us as we pave the way with innovative financing and financial education!"
Then "What You’ll Be Doing Collaboration & Mentorship Work as a hands-on individual contributor engineer on the Platform Engineering & Operations team, without formal people-management responsibilities.Help mentor junior engineers on the team, sharing knowledge as they grow their skills.Provide input and feedback on the technical roadmap for infrastructure and platform engineering. Cloud Architecture & Infrastructure Support cloud architecture and account management across development, staging, and production environments for a regulated lending platform.Help implement and maintain infrastructure-as-code and GitOps practices across infrastructure operations.Support container orchestration across multiple deployable services and cloud accounts. Security, Identity & Compliance Support identity management, account-level security posture, secrets management, and KMS key practices.Assist security and compliance teams with audits and vendor/security assessments for a regulated financial services platform. Developer Experience & CI/CD Maintain and improve CI/CD pipelines across multiple repositories, from build through environment-gated production deployments.Support developer experience and internal tooling improvements for engineering teams. Reliability & Incident Management Participate in on-call and incident-response practices, including postmortems, for a platform where downtime directly impacts loan funding and servicing. AI-Native Platform Engineering Explore and help integrate AI-assisted engineering tools (e.g., Claude Code, GitHub Copilot) into infrastructure workflows, CI/CD pipelines, and internal tooling.Support the adoption of AI-driven observability practices — anomaly detection, predictive alerting, and AI-assisted root-cause analysis — layered on top of existing monitoring stacks.Help support the infrastructure needs of ML/AI-driven product features (e.g., underwriting and fraud models), including model serving, inference monitoring, and compute scaling for AI workloads.Contribute to self-service internal tooling and golden paths that make it easier for engineers to ship safely."
Then "Your Areas of Knowledge and Expertise Bachelor's degree in computer science or a related discipline, or equivalent experience.4+ years of experience engineering highly available, enterprise-grade software and platform applications.2+ years of hands-on experience in platform engineering across various cloud computing models.2+ 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.Working 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.).Experience with continuous integration and continuous delivery (CI/CD) tools and processes (e.g., GitHub Actions, Jenkins, Ansible).Experience with developer tools and open-source technologies.Working familiarity with MLOps/LLMOps concepts and the infrastructure needs of AI/ML workloads (GPU or accelerator provisioning, model serving, inference cost and latency management).Hands-on use of AI coding assistants and developer tools (e.g., Claude Code, GitHub Copilot) in real engineering workflows.Familiarity 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."
Then "Preferred Expertise 2+ years of experience in cloud infrastructure, DevOps, or Site Reliability Engineering (SRE), with hands-on experience in AWS production environments.Experience supporting cloud platforms aligned with the AWS Well-Architected Framework, with an interest in security, reliability, operational excellence, performance efficiency, and cost optimization.Hands-on experience 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 working with infrastructure as code (IaC) using Terraform, AWS CDK, or AWS CloudFormation.Experience supporting CI/CD pipelines using tools such as GitHub Actions or Jenkins.Experience with cloud operations, including platform administration, production support, capacity planning, patching, and maintenance for AWS environments.Experience working with monitoring, logging, alerting, and observability tools such as Amazon CloudWatch, Prometheus, Grafana, and New Relic to support platform health, performance, and availability.Ability to participate as a technical escalation point during production incidents, supporting incident response, root cause analysis (RCA), and post-incident reviews.Familiarity with Site Reliability Engineering (SRE) principles, including service reliability, SLAs/SLOs, incident management, change management, and operational readiness.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.Experience supporting DevSecOps practices, including automated security scanning, policy validation, compliance checks, secrets management, and vulnerability remediation within CI/CD pipelines.Good troubleshooting, problem-solving, and collaboration skills, with the ability to work effectively across engineering, security, operations, and platform teams.Interest in mentoring junior engineers and contributing to cloud engineering best practices is a plus.Interest in 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."
Then "Why You'll Love Working Here Comprehensive Medical, Dental, and Vision InsuranceGenerous Paid Time OffBirthday Day Off12 Paid Company Holidays401(k) MatchFSA and HSAPaid Life Insurance Paid Disability InsurancePet InsuranceEmployee Assistance Program (EAP)Professional Development CoursesIn Office Provided Snacks and DrinksGym Facilities (LA & Tustin/CEC Offices)In Office Engagement Activities"
Then "Compensation Range The US base salary range for this full-time position is $132,300 - $152,300 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 US role postings reflect the base salary only, and do not include any variable compensation elements."
Then "Physical Requirements This is a stationary position that requires frequent sitting (approximately 95%), repetitive wrist motions, grasping, speaking, listening, close vision, and the ability to adjust focus. It also may require occasional standing, lifting, carrying of 20lbs or less, walking, kneeling, bending/stooping, twisting, pulling/pushing,
- . For prose use
. For subheadings inside What You’ll Be Doing we could treat each bold heading as a subsection? The instruction: Use
for section headings. So each major section gets
. Inside we can have
and
- . For subheadings like "Collaboration & Mentorship" we could either treat as
with bold or maybe as
? But we only allowed
for section headings; we could still use
or inside
. Safer to keep as
with bold text using . But we must not invent headings that are not needed. We'll keep them as
...: then description. Similarly for Preferred Expertise we could just list items. We need to preserve all specifics. Let's extract content. First, after removing boilerplate, we have: "A Day in the Life We’re looking for a Staff Engineer DevOps to join our Platform Engineering & Operations team as a hands-on individual-contributor engineer, helping to build and maintain the infrastructure underneath Lendistry’s lending platform. You’ll work on cloud architecture, security posture, and developer experience across a regulated financial services environment — and help support fellow engineers so we can grow without compromising reliability or compliance." Then "Lendistry: Who We Are We’re proud to be the nation’s largest minority-led, tech-savvy lender for small businesses and commercial real estate. As a certified Community Development Financial Institution (CDFI) and Community Development Entity (CDE), our mission is all about creating economic opportunities and fueling growth for small business owners and their communities. Join us as we pave the way with innovative financing and financial education!" Then "What You’ll Be Doing Collaboration & Mentorship Work as a hands-on individual contributor engineer on the Platform Engineering & Operations team, without formal people-management responsibilities.Help mentor junior engineers on the team, sharing knowledge as they grow their skills.Provide input and feedback on the technical roadmap for infrastructure and platform engineering. Cloud Architecture & Infrastructure Support cloud architecture and account management across development, staging, and production environments for a regulated lending platform.Help implement and maintain infrastructure-as-code and GitOps practices across infrastructure operations.Support container orchestration across multiple deployable services and cloud accounts. Security, Identity & Compliance Support identity management, account-level security posture, secrets management, and KMS key practices.Assist security and compliance teams with audits and vendor/security assessments for a regulated financial services platform. Developer Experience & CI/CD Maintain and improve CI/CD pipelines across multiple repositories, from build through environment-gated production deployments.Support developer experience and internal tooling improvements for engineering teams. Reliability & Incident Management Participate in on-call and incident-response practices, including postmortems, for a platform where downtime directly impacts loan funding and servicing. AI-Native Platform Engineering Explore and help integrate AI-assisted engineering tools (e.g., Claude Code, GitHub Copilot) into infrastructure workflows, CI/CD pipelines, and internal tooling.Support the adoption of AI-driven observability practices — anomaly detection, predictive alerting, and AI-assisted root-cause analysis — layered on top of existing monitoring stacks.Help support the infrastructure needs of ML/AI-driven product features (e.g., underwriting and fraud models), including model serving, inference monitoring, and compute scaling for AI workloads.Contribute to self-service internal tooling and golden paths that make it easier for engineers to ship safely." Then "Your Areas of Knowledge and Expertise Bachelor's degree in computer science or a related discipline, or equivalent experience.4+ years of experience engineering highly available, enterprise-grade software and platform applications.2+ years of hands-on experience in platform engineering across various cloud computing models.2+ 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.Working 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.).Experience with continuous integration and continuous delivery (CI/CD) tools and processes (e.g., GitHub Actions, Jenkins, Ansible).Experience with developer tools and open-source technologies.Working familiarity with MLOps/LLMOps concepts and the infrastructure needs of AI/ML workloads (GPU or accelerator provisioning, model serving, inference cost and latency management).Hands-on use of AI coding assistants and developer tools (e.g., Claude Code, GitHub Copilot) in real engineering workflows.Familiarity 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." Then "Preferred Expertise 2+ years of experience in cloud infrastructure, DevOps, or Site Reliability Engineering (SRE), with hands-on experience in AWS production environments.Experience supporting cloud platforms aligned with the AWS Well-Architected Framework, with an interest in security, reliability, operational excellence, performance efficiency, and cost optimization.Hands-on experience 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 working with infrastructure as code (IaC) using Terraform, AWS CDK, or AWS CloudFormation.Experience supporting CI/CD pipelines using tools such as GitHub Actions or Jenkins.Experience with cloud operations, including platform administration, production support, capacity planning, patching, and maintenance for AWS environments.Experience working with monitoring, logging, alerting, and observability tools such as Amazon CloudWatch, Prometheus, Grafana, and New Relic to support platform health, performance, and availability.Ability to participate as a technical escalation point during production incidents, supporting incident response, root cause analysis (RCA), and post-incident reviews.Familiarity with Site Reliability Engineering (SRE) principles, including service reliability, SLAs/SLOs, incident management, change management, and operational readiness.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.Experience supporting DevSecOps practices, including automated security scanning, policy validation, compliance checks, secrets management, and vulnerability remediation within CI/CD pipelines.Good troubleshooting, problem-solving, and collaboration skills, with the ability to work effectively across engineering, security, operations, and platform teams.Interest in mentoring junior engineers and contributing to cloud engineering best practices is a plus.Interest in 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." Then "Why You'll Love Working Here Comprehensive Medical, Dental, and Vision InsuranceGenerous Paid Time OffBirthday Day Off12 Paid Company Holidays401(k) MatchFSA and HSAPaid Life Insurance Paid Disability InsurancePet InsuranceEmployee Assistance Program (EAP)Professional Development CoursesIn Office Provided Snacks and DrinksGym Facilities (LA & Tustin/CEC Offices)In Office Engagement Activities" Then "Compensation Range The US base salary range for this full-time position is $132,300 - $152,300 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 US role postings reflect the base salary only, and do not include any variable compensation elements." Then "Physical Requirements This is a stationary position that requires frequent sitting (approximately 95%), repetitive wrist motions, grasping, speaking, listening, close vision, and the ability to adjust focus. It also may require occasional standing, lifting, carrying of 20lbs or less, walking, kneeling, bending/stooping, twisting, pulling/pushing,