Senior AI/ML Software Engineer
Peraton · Columbia, MD · 4 wk ago
On-siteEngineering$282k/yrFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Content:
- About Peraton (company description) - maybe not needed? The instruction: "About The Role" is a heading. The "About Peraton" is company overview; maybe we can include under "About the role"? Actually "About The Role" is a heading we should use. The content after "About The Role" includes description of role. So we should put that under
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Content:
- About Peraton (company description) - maybe not needed? The instruction: "About The Role" is a heading. The "About Peraton" is company overview; maybe we can include under "About the role"? Actually "About The Role" is a heading we should use. The content after "About The Role" includes description of role. So we should put that under About the role
with paragraphs.
We also have responsibilities list: bullet points after "Specifically you will:" includes many items. Those are responsibilities. So we can have Responsibilities
with - each.
Qualifications: The section "Qualifications Individual Capabilities/Experience Required:" includes education, experience, clearance, etc. Also there is "Benefits Statement" and "Target Salary Range". Also "Benefits" details. Also "Pay" (salary range). Also "Schedule"? Not mentioned except "full-time position requiring 1880 hours of support per year; and work is performed at a customer location." That's schedule info (hours per year). Could be considered schedule. Also maybe "Pay" section for salary range.
We also have "Benefits" details: "Peraton offers enhanced benefits ... heavily subsidized employee benefits coverage ... 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan." Then later "Benefits Statement: Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays." So we can combine.
We must not include sections like "Skills" unless there is specific content. There's mention of proficiency in LINUX and basic Networking skills, also Gradle Java, Python, etc. Could be under Skills. But we could also put those under Responsibilities or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we might combine skills into Qualifications or Responsibilities. However we have a separate "Qualifications" heading for education/experience/clearance. Skills could be separate but maybe we can include under Qualifications as part of capabilities. But we have to decide.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range, benefits, and hours per year (schedule). So we can include those.
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO, application statements, etc. Also remove "Application Statements", "EEO", etc.
We must preserve all substantive information. So we need to include company description? The instruction: "About Peraton" maybe not needed as it's not about the role. But we could include as a brief intro? The instruction says "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." It doesn't say we must drop company description. However the instruction about sections: Use headings only for those listed. So we could include a
before any headings for general description. That's allowed. The output is just HTML fragment; we can have
containing company overview, then headings.
Thus structure:
Peraton is a next-generation national security company ... (the company description).
Then About the role
with paragraph(s) describing role: "Peraton is hiring a Senior AI/ML Software Engineer to join our Cyber Solutions business unit in Jessup, MD. As a Software Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location. As a Software Engineer on our team, you will work to help design, develop, test, and maintain scalable software solutions and prototypes. You will also work in a Full Stack development environment requiring proficiency in LINUX and basic Networking skills. This will involve customizing access and interfaces with a Large Language Model (LLM) tailored for the customer and related requirement types and users."
Then Responsibilities
with - items from "Specifically you will:" list.
List items:
- Design, develop software applications using Gradle Java, Python;
- Gather and evaluate end-user and customer requirements;
- Write, test, debug and deploy code;
- Perform code reviews to maintain quality;
- Troubleshoot and resolve defects and performance issues;
- Contribute to project planning;
- Collaborate with product managers, developers, SMEs, and leadership contributing to strategic initiatives;
- Design user interface to be widely accessible across the customer community;
- Explore LLM and AI integration opportunities;
- Design interfaces/bridge to external requirements management tools;
- Mentor junior software engineers.
We need to preserve punctuation? Probably fine.
Then
Qualifications
with paragraph(s) covering education/experience, clearance, etc.
Content: "Bachelor's degree in computer science or related discipline from an accredited college or university plus fourteen (14) years of experience as a software engineer in programs and contracts of similar scope, type, complexity is required. Four (4) years of additional SWE experience on projects with similar software processes may be substituted for a bachelor's degree. Must be compliant with DoD8570 IAT2. Position requires an active TS/SCI clearance with polygraph. Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information."
We could also mention "Peraton offers enhanced benefits to employees working on this critical National Security program, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan." That's benefits, but we have separate Benefits section.
Then Benefits
with paragraph(s) combining both benefits statements.
First: "Peraton offers enhanced benefits to employees working on this critical National Security program, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan."
Second: "Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits."
We could combine into one paragraph or two.
Then Pay
with paragraph: "Target Salary Range: $176,000 - $282,000. This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay."
Then Schedule
with paragraph: "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location."
We should ensure we don't repeat info. The schedule mention also appears in About the role; we might not need to duplicate. But we need to preserve all substantive info; we can keep it in About the role and also have Schedule section? That would duplicate. Better to keep schedule info only in Schedule section and not duplicate in About the role. However About the role currently includes that sentence. We could remove it from About the role and put it in Schedule. But we must preserve all substantive info; moving it is fine as long as it's present somewhere. So we can edit About the role paragraph to exclude the schedule sentence, and put schedule in its own section.
Thus About the role paragraph: "Peraton is hiring a Senior AI/ML Software Engineer to join our Cyber Solutions business unit in Jessup, MD. As a Software Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. As a Software Engineer on our team, you will work to help design, develop, test, and maintain scalable software solutions and prototypes. You will also work in a Full Stack development environment requiring proficiency in LINUX and basic Networking skills. This will involve customizing access and interfaces with a Large Language Model (LLM) tailored for the customer and related requirement types and users."
Now schedule section: "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location."
Now ensure we didn't lose any other info: The mention of "Peraton offers enhanced benefits..." we placed in Benefits. Also the "Benefits Statement" we placed.
Check for any other substantive info: The "#MDFSP #AJCM" maybe internal tags; we can drop as minor metadata.
Also "Details" heading before Target Salary Range: we can ignore.
Now ensure we didn't include any boilerplate: Removed Application Statements, EEO, etc.
Now produce HTML fragment:
Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure.
About the role
Peraton is hiring a Senior AI/ML Software Engineer to join our Cyber Solutions business unit in Jessup, MD. As a Software Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. As a Software Engineer on our team, you will work to help design, develop, test, and maintain scalable software solutions and prototypes. You will also work in a Full Stack development environment requiring proficiency in LINUX and basic Networking skills. This will involve customizing access and interfaces with a Large Language Model (LLM) tailored for the customer and related requirement types and users.
Responsibilities
- Design, develop software applications using Gradle Java, Python;
- Gather and evaluate end-user and customer requirements;
- Write, test, debug and deploy code;
- Perform code reviews to maintain quality;
- Troubleshoot and resolve defects and performance issues;
- Contribute to project planning;
- Collaborate with product managers, developers, SMEs, and leadership contributing to strategic initiatives;
- Design user interface to be widely accessible across the customer community;
- Explore LLM and AI integration opportunities;
- Design interfaces/bridge to external requirements management tools;
- Mentor junior software engineers.
Qualifications
B
or drop it." It doesn't say we must drop company description. However the instruction about sections: Use headings only for those listed. So we could include a
before any headings for general description. That's allowed. The output is just HTML fragment; we can have
containing company overview, then headings. Thus structure:
Peraton is a next-generation national security company ... (the company description).
ThenAbout the role
with paragraph(s) describing role: "Peraton is hiring a Senior AI/ML Software Engineer to join our Cyber Solutions business unit in Jessup, MD. As a Software Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location. As a Software Engineer on our team, you will work to help design, develop, test, and maintain scalable software solutions and prototypes. You will also work in a Full Stack development environment requiring proficiency in LINUX and basic Networking skills. This will involve customizing access and interfaces with a Large Language Model (LLM) tailored for the customer and related requirement types and users." ThenResponsibilities
with- items from "Specifically you will:" list.
List items:
- Design, develop software applications using Gradle Java, Python;
- Gather and evaluate end-user and customer requirements;
- Write, test, debug and deploy code;
- Perform code reviews to maintain quality;
- Troubleshoot and resolve defects and performance issues;
- Contribute to project planning;
- Collaborate with product managers, developers, SMEs, and leadership contributing to strategic initiatives;
- Design user interface to be widely accessible across the customer community;
- Explore LLM and AI integration opportunities;
- Design interfaces/bridge to external requirements management tools;
- Mentor junior software engineers.
We need to preserve punctuation? Probably fine.
Then
Qualifications
with paragraph(s) covering education/experience, clearance, etc. Content: "Bachelor's degree in computer science or related discipline from an accredited college or university plus fourteen (14) years of experience as a software engineer in programs and contracts of similar scope, type, complexity is required. Four (4) years of additional SWE experience on projects with similar software processes may be substituted for a bachelor's degree. Must be compliant with DoD8570 IAT2. Position requires an active TS/SCI clearance with polygraph. Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information." We could also mention "Peraton offers enhanced benefits to employees working on this critical National Security program, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan." That's benefits, but we have separate Benefits section. ThenBenefits
with paragraph(s) combining both benefits statements. First: "Peraton offers enhanced benefits to employees working on this critical National Security program, which include heavily subsidized employee benefits coverage for you and your dependents, 25 days of PTO accrued annually up to a generous PTO cap and eligible to participate in an attractive bonus plan." Second: "Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits." We could combine into one paragraph or two. ThenPay
with paragraph: "Target Salary Range: $176,000 - $282,000. This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay." ThenSchedule
with paragraph: "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." We should ensure we don't repeat info. The schedule mention also appears in About the role; we might not need to duplicate. But we need to preserve all substantive info; we can keep it in About the role and also have Schedule section? That would duplicate. Better to keep schedule info only in Schedule section and not duplicate in About the role. However About the role currently includes that sentence. We could remove it from About the role and put it in Schedule. But we must preserve all substantive info; moving it is fine as long as it's present somewhere. So we can edit About the role paragraph to exclude the schedule sentence, and put schedule in its own section. Thus About the role paragraph: "Peraton is hiring a Senior AI/ML Software Engineer to join our Cyber Solutions business unit in Jessup, MD. As a Software Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. As a Software Engineer on our team, you will work to help design, develop, test, and maintain scalable software solutions and prototypes. You will also work in a Full Stack development environment requiring proficiency in LINUX and basic Networking skills. This will involve customizing access and interfaces with a Large Language Model (LLM) tailored for the customer and related requirement types and users." Now schedule section: "This is a full-time position requiring 1880 hours of support per year; and work is performed at a customer location." Now ensure we didn't lose any other info: The mention of "Peraton offers enhanced benefits..." we placed in Benefits. Also the "Benefits Statement" we placed. Check for any other substantive info: The "#MDFSP #AJCM" maybe internal tags; we can drop as minor metadata. Also "Details" heading before Target Salary Range: we can ignore. Now ensure we didn't include any boilerplate: Removed Application Statements, EEO, etc. Now produce HTML fragment:Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure.
About the role
Peraton is hiring a Senior AI/ML Software Engineer to join our Cyber Solutions business unit in Jessup, MD. As a Software Engineer on our team, you will support one of the largest enterprise-wide engineering contracts within the Intelligence Community. As a Software Engineer on our team, you will work to help design, develop, test, and maintain scalable software solutions and prototypes. You will also work in a Full Stack development environment requiring proficiency in LINUX and basic Networking skills. This will involve customizing access and interfaces with a Large Language Model (LLM) tailored for the customer and related requirement types and users.
Responsibilities
- Design, develop software applications using Gradle Java, Python;
- Gather and evaluate end-user and customer requirements;
- Write, test, debug and deploy code;
- Perform code reviews to maintain quality;
- Troubleshoot and resolve defects and performance issues;
- Contribute to project planning;
- Collaborate with product managers, developers, SMEs, and leadership contributing to strategic initiatives;
- Design user interface to be widely accessible across the customer community;
- Explore LLM and AI integration opportunities;
- Design interfaces/bridge to external requirements management tools;
- Mentor junior software engineers.
Qualifications
B