DevSecOps / Platform Engineer
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes:
- About Peregrine (company description) - could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Peregrine" describing company. Might map to "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. We have content about the role: "At Peregrine Advisors, you will own the delivery pipelines...". That's role description. Could be "About the role". Also "Your first project" details responsibilities. Could be "Responsibilities". Then "Requirements" heading matches. Then "Who you are" maybe "Qualifications"? Or "Skills"? The "What you bring" could be "Skills". Benefits we have. Pay we have salary range. Schedule we have remote/hybrid with travel. So we can include Pay and Schedule sections.
We must not create sections with filler. So we need to ensure each section has substantive content.
Let's extract content:
Company description: "About PeregrinePeregrine Advisors is a rapidly growing AI and data innovation hub helping government solve hard problems and deliver better outcomes. We work across the full lifecycle—from strategy and governance through architecture, engineering, analytics, AI, visualization, and training—for clients including the SEC, PCAOB, DDOT, and DCAA.Our clients describe our support as “absolutely excellent” and our people as “instrumental to organization’s success.” Winner of the United Nations COP27 Datathon, our work has earned all Exceptional CPARS ratings, SEC Chair’s Awards, the SEC Vision Award, and recognition from FDA leadership.We are also built differently. Peregrine is the first and only social enterprise organized as a Benefit Corporation and SBA 8(a) company focused on AI and data for government. We believe business success should create client value, social value, and opportunity for our people.As we enter our next stage of growth, we need dependable, motivated, and skilled people who have a combination of intellectual curiosity and intellectual courage. With new clients, larger programs, and expanding responsibilities, the people joining Peregrine now will have the opportunity to help shape the company we become.People first. Ownership always.We solve problems through people, process, and technology—in that order. Technology matters, but people make transformation happen. That principle defines our culture. Trust and motivation come before competence. We hire people we can trust, who care deeply about what they do, take ownership, learn quickly, help one another, and refuse to walk past a problem because it belongs to someone else.At Peregrine, you are not joining simply to fill a position. You are joining a team, taking ownership of a mission, and helping build a company. If that excites you, we should talk."
That's a lot of prose. Could be placed under "About the role"? Actually "About the role" is more about the job, but we could treat this as "About the role" describing the company and role. However we also have explicit role description later. Might be better to split: "About the role" could be the description of the role (own delivery pipelines etc). The company description could be omitted? But we must preserve ALL substantive information. So we need to include that somewhere. Perhaps we can include it under "About the role" as a preamble. Or we could create a section "About Peregrine" but the instruction says use headings like About the role, Responsibilities, etc. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It doesn't say we cannot use other headings, but to follow the pattern, we should use those. So we need to map content to those headings.
Thus:
- About the role: could include company description + role overview (own delivery pipelines etc). Might be too long but okay.
- Responsibilities: could be the bullet list under "Your first project" (the list of duties). That's a list.
- Requirements: the bullet list under "Requirements". That's a list.
- Qualifications: maybe the "Preferred" bullet list? Or "Who you are" and "What you bring". Could treat "Qualifications" as the preferred qualifications and personal traits. But we have "Who you are" and "What you bring" describing attributes. Could be "Qualifications". Or we could have "Skills" for technical skills. The instruction includes Skills as a possible heading. We have "What you bring" which is skills. So we could map:
- Qualifications: maybe the "Preferred" list (Federal security experience, RHEL, etc). Or we could combine.
- Skills: the "What you bring" list (hands-on ownership of IaC, scripting, cloud networking, judgment, adapt to AI tools). That's skills.
- Benefits: the bullet list under "Benefits".
- Pay: the salary range statement.
- Schedule: the remote/hybrid description.
We must not create sections with filler. Ensure each has content.
Now we need to format using for each section heading, then content: either
for prose or
- for lists.
We must not include boilerplate like EEO, equal opportunity, application instructions, etc. At the end there is "Peregrine Advisors is an equal opportunity employer." and "Peregrine exclusively works with OPEN Data Jobs to recruit our team. Register with OPEN Data Jobs to be considered for this and future openings." That's application instructions/boilerplate; we should remove.
Also remove duplicated lines.
Now let's extract precise content.
First, company description paragraph(s). We'll combine into a single
maybe multiple paragraphs but we can keep as one
with line breaks? Better to keep as
with the text.
Then role overview: "At Peregrine Advisors, you will own the delivery pipelines, automation, and environments that carry federal systems into production. But we hire people, not seats. As the work evolves, you will learn new systems and tools, take on greater responsibility, and help develop the firm's capabilities, tools, and lines of business. We move our best to where the hardest problems are." That's prose.
Then "This is a full-time W-2 position with a salary of $120,000 to $150,000 per year. It is a remote position, and a hybrid arrangement is preferred: hybrid means traveling to the client site in the Washington, DC metropolitan area, typically one to two days a week. Wherever you work from, occasional travel to DC is part of the role. The initial engagement requires United States citizenship and the ability to obtain a Public Trust determination." This includes Pay and Schedule and also citizenship requirement (maybe part of Requirements?). We'll extract Pay and Schedule later.
Now "Your first project" section: It starts with "Your first projectYour first project will likely have you owning assigned delivery pipelines and the environments beneath them. Depending on the assignment, you may:" then a list of bullet points (each starting with a verb). We need to capture that list.
List items:
- Work on the integration and deployment of enterprise tools and platforms such as SageMaker, Posit Connect, or on-demand, pre-configured EC2-based Linux virtual machines.
- Build and maintain CI/CD pipelines for infrastructure validation, testing, deployment, and release promotion.
- Configure cloud networking, access permissions, storage, and compute resources following established security requirements.
- Build and maintain Linux machine images, including software installation, configuration, patching, and validation.
- Support analytics and development environments, including user onboarding, access configuration, and software dependencies.
- Troubleshoot deployment failures, connectivity problems, permissions, Linux services, and application runtime issues using logs and diagnostic tools.
- Write and maintain scripts that simplify recurring operational tasks and improve consistency.
- Participate in code reviews, test infrastructure changes, and document implementation details, troubleshooting procedures, and operational runbooks.
- Take ownership of assigned changes from implementation through deployment verification, collaborating with senior engineers on architectural decisions and complex incidents.
- You deliver CloudFormation templates, Amazon Machine Images (AMIs), and pipelines that provide the required functionality through the enterprise tools and platforms, enforce the required controls, and produce the evidence a release review needs. You automate the manual steps out of the release path, and you build progressive delivery with automated health checks and rollback so that deploying stops being an event.
Note: The last bullet is a bit long but still a bullet.
We'll put each as
- .
Now Requirements section: bullet list under "Requirements". Items:
- 5+ years of DevSecOps or platform engineering experience
- A bachelor's degree in computer science, information technology, cybersecurity, engineering, or a related technical discipline
- Hands-on experience administering Amazon Web Services (AWS) cloud infrastructure with a working understanding of compute, storage, networking, and identity management
- Practical experience with infrastructure as code (CloudFormation or the AWS Cloud Development Kit), CI/CD pipeline automation with security gates using GitHub Actions or comparable tools, and hands-on Docker image creation and containerization
- Linux administration and troubleshooting skills, including packages, services, permissions, and logs
- Ability to write and troubleshoot scripts in Python and Bash
- Understanding of least-privilege access, zero trust principles, secure configuration, and controlled deployment processes
- Experience with Git-based version control
- Monitoring and logging
- Proficiency in writing, PowerPoint, and Excel
Note: "Proficiency in writing, PowerPoint, and Excel" seems odd but it's there.
Now Preferred (maybe Qualifications): bullet list under "Preferred":
- Federal security experience supporting Federal Information Security Modernization Act (FISMA) compliance, implementing National Institute of Standards and Technology Special Publication 800-53 (NIST SP 800-53) controls, and providing Authority to Operate (ATO) support
- Red Hat Enterprise Linux (RHEL) administration, Ansible, and software packaging experience
- An Amazon Web Services certification
- Nexus, Artifactory, CloudBolt, or comparable artifact management and provisioning platforms
- OpenID Connect (OIDC) authentication, deployment approval controls, and AWS environments spanning multiple accounts
- Federal information technology experience
Now "Who you are
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - About Peregrine (company description) - could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Peregrine" describing company. Might map to "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. We have content about the role: "At Peregrine Advisors, you will own the delivery pipelines...". That's role description. Could be "About the role". Also "Your first project" details responsibilities. Could be "Responsibilities". Then "Requirements" heading matches. Then "Who you are" maybe "Qualifications"? Or "Skills"? The "What you bring" could be "Skills". Benefits we have. Pay we have salary range. Schedule we have remote/hybrid with travel. So we can include Pay and Schedule sections. We must not create sections with filler. So we need to ensure each section has substantive content. Let's extract content: Company description: "About PeregrinePeregrine Advisors is a rapidly growing AI and data innovation hub helping government solve hard problems and deliver better outcomes. We work across the full lifecycle—from strategy and governance through architecture, engineering, analytics, AI, visualization, and training—for clients including the SEC, PCAOB, DDOT, and DCAA.Our clients describe our support as “absolutely excellent” and our people as “instrumental to organization’s success.” Winner of the United Nations COP27 Datathon, our work has earned all Exceptional CPARS ratings, SEC Chair’s Awards, the SEC Vision Award, and recognition from FDA leadership.We are also built differently. Peregrine is the first and only social enterprise organized as a Benefit Corporation and SBA 8(a) company focused on AI and data for government. We believe business success should create client value, social value, and opportunity for our people.As we enter our next stage of growth, we need dependable, motivated, and skilled people who have a combination of intellectual curiosity and intellectual courage. With new clients, larger programs, and expanding responsibilities, the people joining Peregrine now will have the opportunity to help shape the company we become.People first. Ownership always.We solve problems through people, process, and technology—in that order. Technology matters, but people make transformation happen. That principle defines our culture. Trust and motivation come before competence. We hire people we can trust, who care deeply about what they do, take ownership, learn quickly, help one another, and refuse to walk past a problem because it belongs to someone else.At Peregrine, you are not joining simply to fill a position. You are joining a team, taking ownership of a mission, and helping build a company. If that excites you, we should talk." That's a lot of prose. Could be placed under "About the role"? Actually "About the role" is more about the job, but we could treat this as "About the role" describing the company and role. However we also have explicit role description later. Might be better to split: "About the role" could be the description of the role (own delivery pipelines etc). The company description could be omitted? But we must preserve ALL substantive information. So we need to include that somewhere. Perhaps we can include it under "About the role" as a preamble. Or we could create a section "About Peregrine" but the instruction says use headings like About the role, Responsibilities, etc. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It doesn't say we cannot use other headings, but to follow the pattern, we should use those. So we need to map content to those headings. Thus: - About the role: could include company description + role overview (own delivery pipelines etc). Might be too long but okay. - Responsibilities: could be the bullet list under "Your first project" (the list of duties). That's a list. - Requirements: the bullet list under "Requirements". That's a list. - Qualifications: maybe the "Preferred" bullet list? Or "Who you are" and "What you bring". Could treat "Qualifications" as the preferred qualifications and personal traits. But we have "Who you are" and "What you bring" describing attributes. Could be "Qualifications". Or we could have "Skills" for technical skills. The instruction includes Skills as a possible heading. We have "What you bring" which is skills. So we could map: - Qualifications: maybe the "Preferred" list (Federal security experience, RHEL, etc). Or we could combine. - Skills: the "What you bring" list (hands-on ownership of IaC, scripting, cloud networking, judgment, adapt to AI tools). That's skills. - Benefits: the bullet list under "Benefits". - Pay: the salary range statement. - Schedule: the remote/hybrid description. We must not create sections with filler. Ensure each has content. Now we need to format using
for each section heading, then content: either
for prose or
- for lists.
We must not include boilerplate like EEO, equal opportunity, application instructions, etc. At the end there is "Peregrine Advisors is an equal opportunity employer." and "Peregrine exclusively works with OPEN Data Jobs to recruit our team. Register with OPEN Data Jobs to be considered for this and future openings." That's application instructions/boilerplate; we should remove.
Also remove duplicated lines.
Now let's extract precise content.
First, company description paragraph(s). We'll combine into a single
maybe multiple paragraphs but we can keep as one
with line breaks? Better to keep as
with the text. Then role overview: "At Peregrine Advisors, you will own the delivery pipelines, automation, and environments that carry federal systems into production. But we hire people, not seats. As the work evolves, you will learn new systems and tools, take on greater responsibility, and help develop the firm's capabilities, tools, and lines of business. We move our best to where the hardest problems are." That's prose. Then "This is a full-time W-2 position with a salary of $120,000 to $150,000 per year. It is a remote position, and a hybrid arrangement is preferred: hybrid means traveling to the client site in the Washington, DC metropolitan area, typically one to two days a week. Wherever you work from, occasional travel to DC is part of the role. The initial engagement requires United States citizenship and the ability to obtain a Public Trust determination." This includes Pay and Schedule and also citizenship requirement (maybe part of Requirements?). We'll extract Pay and Schedule later. Now "Your first project" section: It starts with "Your first projectYour first project will likely have you owning assigned delivery pipelines and the environments beneath them. Depending on the assignment, you may:" then a list of bullet points (each starting with a verb). We need to capture that list. List items: - Work on the integration and deployment of enterprise tools and platforms such as SageMaker, Posit Connect, or on-demand, pre-configured EC2-based Linux virtual machines. - Build and maintain CI/CD pipelines for infrastructure validation, testing, deployment, and release promotion. - Configure cloud networking, access permissions, storage, and compute resources following established security requirements. - Build and maintain Linux machine images, including software installation, configuration, patching, and validation. - Support analytics and development environments, including user onboarding, access configuration, and software dependencies. - Troubleshoot deployment failures, connectivity problems, permissions, Linux services, and application runtime issues using logs and diagnostic tools. - Write and maintain scripts that simplify recurring operational tasks and improve consistency. - Participate in code reviews, test infrastructure changes, and document implementation details, troubleshooting procedures, and operational runbooks. - Take ownership of assigned changes from implementation through deployment verification, collaborating with senior engineers on architectural decisions and complex incidents. - You deliver CloudFormation templates, Amazon Machine Images (AMIs), and pipelines that provide the required functionality through the enterprise tools and platforms, enforce the required controls, and produce the evidence a release review needs. You automate the manual steps out of the release path, and you build progressive delivery with automated health checks and rollback so that deploying stops being an event. Note: The last bullet is a bit long but still a bullet. We'll put each as
- . Now Requirements section: bullet list under "Requirements". Items: - 5+ years of DevSecOps or platform engineering experience - A bachelor's degree in computer science, information technology, cybersecurity, engineering, or a related technical discipline - Hands-on experience administering Amazon Web Services (AWS) cloud infrastructure with a working understanding of compute, storage, networking, and identity management - Practical experience with infrastructure as code (CloudFormation or the AWS Cloud Development Kit), CI/CD pipeline automation with security gates using GitHub Actions or comparable tools, and hands-on Docker image creation and containerization - Linux administration and troubleshooting skills, including packages, services, permissions, and logs - Ability to write and troubleshoot scripts in Python and Bash - Understanding of least-privilege access, zero trust principles, secure configuration, and controlled deployment processes - Experience with Git-based version control - Monitoring and logging - Proficiency in writing, PowerPoint, and Excel Note: "Proficiency in writing, PowerPoint, and Excel" seems odd but it's there. Now Preferred (maybe Qualifications): bullet list under "Preferred": - Federal security experience supporting Federal Information Security Modernization Act (FISMA) compliance, implementing National Institute of Standards and Technology Special Publication 800-53 (NIST SP 800-53) controls, and providing Authority to Operate (ATO) support - Red Hat Enterprise Linux (RHEL) administration, Ansible, and software packaging experience - An Amazon Web Services certification - Nexus, Artifactory, CloudBolt, or comparable artifact management and provisioning platforms - OpenID Connect (OIDC) authentication, deployment approval controls, and AWS environments spanning multiple accounts - Federal information technology experience Now "Who you are
- for lists.
We must not include boilerplate like EEO, equal opportunity, application instructions, etc. At the end there is "Peregrine Advisors is an equal opportunity employer." and "Peregrine exclusively works with OPEN Data Jobs to recruit our team. Register with OPEN Data Jobs to be considered for this and future openings." That's application instructions/boilerplate; we should remove.
Also remove duplicated lines.
Now let's extract precise content.
First, company description paragraph(s). We'll combine into a single