Senior Engineer
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.
We need to decide which sections to include based on content.
We have:
- About the role: paragraph describing building data platform for DoD, technologies.
- What you will do: list of duties (Build data infrastructure..., Build ETL pipelines..., Leverage software engineering principles...). That's a list.
- What we are looking for: list of requirements (Three plus years..., Experience with large-scale relational..., Experience or knowledge of service mesh..., Experience with supporting enterprise Cloud..., Experience in automation languages..., Experience in data management..., Experience with building and releasing software in cloud-native environments, Experience using a variety of package managers..., Deep knowledge of software design..., Obtain Security+ within first 90 days..., Highly preferred: Experience with Kubernetes..., Experience with building and managing fault-tolerant..., Experience with monitoring and logging..., Solid understanding of Helm Charts). That's a list.
- Clearance Requirements: Ability to obtain and maintain TS/SCI clearance. That's a requirement; could be part of Requirements or separate? Could be a subsection but we can include in Requirements list.
- Work Type: On-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel. That's schedule info.
- Salary Range: $120,000 - $180,000; plus note about determination.
- Benefits: list of offerings: Highly competitive salary (but we already have salary), Fully covered healthcare, dental, and vision coverage, 401(k) and company match, Take as you need PTO + 11 paid holidays, Education & training benefits, Annual budget for your tech/gadgets needs, Monthly box of yummy snacks, Remote, hybrid, and flexible work options, Team off-site in fun places!, Generous Referral Bonuses, And More!
We need to avoid duplication: "Highly competitive salary" duplicates salary info; we can still include but maybe we should not duplicate. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that benefit line as part of benefits, even if repeats salary. But we could combine? Probably keep as is.
We also have Vision Statement etc. That's boilerplate? It's not EEO but it's cultural description; maybe we can keep as prose under a section like "About the company" but we already have "Who we are" at start. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who we are" paragraph at start is substantive about company; we could include as an "About the company" section but not listed as allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? But that's already about role. Maybe we can incorporate into About the role paragraph? The "Who we are" is separate from About the role. Could we treat it as part of About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It says "include a section ONLY when the posting has real, specific content for it". It doesn't say we cannot add other headings, but better to stick to those. We could incorporate the "Who we are" into About the role as a preamble paragraph. That would preserve info.
Similarly, Vision Statement etc could be omitted as boilerplate? It's not EEO but it's cultural vision; maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Vision statement is not explicitly listed, but could be considered fluff. Safer to omit? But we need to preserve ALL substantive information. Is vision statement substantive? It's about company culture; maybe considered substantive but not required for job. However, we could keep it as a paragraph under About the role or as a separate section like "About the company" but not in allowed headings. Might be okay to include as a paragraph under About the role before the role description.
We need to avoid duplication: The "Who we are" and later "Our Vision Statement" etc may duplicate some ideas. We'll keep the first "Who we are" paragraph and maybe skip the later vision statements to avoid duplication.
Now decide sections:
- About the role: combine "Who we are" + "About the role" paragraph.
- Responsibilities: "What you will do" list.
- Requirements: "What we are looking for" list + Clearance Requirements.
- Benefits: "What we will offer you" list.
- Pay: Salary Range.
- Schedule: Work Type (On-site locations, travel).
We should not include Qualifications or Skills unless we have specific content; we could treat Requirements as qualifications. But we already have Requirements section.
We need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
... combined paragraph ...
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
Salary Range: $120,000 - $180,000
Schedule
On-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel.
We need to ensure we preserve all substantive info from the lists.
Let's extract the exact text.
From posting:
About the role paragraph: "Raft is building a data platform for the Department of Defense (DoD), aimed at enhancing operators' awareness of critical data. This data is subsequently enriched, rendered queryable, and ultimately presented as a common operational picture to empower operators in making time critical and pertinent decisions. Key technologies include Kafka, Kafka Streams, Pinot, Java, Scala, and Kubernetes. Your involvement in this role will encompass hands-on collaboration with a team of accomplished individuals, collectively striving towards excellence."
We also have "Who we are:" paragraph: "Raft (https://TeamRaft.com) is a customer-obsessed non-traditional defense tech company dedicated to empowering U.S. military and government agencies with cutting-edge AI/ML and data solutions. We are a leader in autonomous data fusion and Agentic AI, with a purposeful focus on Distributed Data Systems, Platforms at Scale, and Complex Application Development. With headquarters in McLean, VA, our range of clients includes innovative federal and public agencies leveraging design thinking, cutting-edge tech stack, and cloud-native ecosystem. We build digital solutions that impact the lives of millions of Americans."
We can combine: maybe start with Who we are then About the role.
Thus About the role section p: combine both paragraphs.
Now Responsibilities (What you will do):
- Build data infrastructure and platforms using diverse data frameworks such as Apache Kafka, Flink, and Kafka Streams
- Build Extract, Transform, Load (ETL) pipelines to enable comprehensive data operations
- Leverage software engineering principles to architect, develop, and implement large scale data applications
We need to keep exactly as given.
Now Requirements (What we are looking for):
List:
- Three plus years of hands-on relevant industry experience
- Experience with large-scale relational and non-relational databases such as PostgreSQL, MySQL, MongoDB, and Elasticsearch to handle low-latency requirements
- Experience or knowledge of service mesh technologies, such as Istio
- Experience with supporting enterprise Cloud applications or infrastructure
- Experience in automation languages like Python or GoLang
- Experience in data management including ETL processing, data governance, and data storage
- Experience with building and releasing software in cloud-native environments
- Experience using a variety of package managers/dependency managers including Maven, Gradle, and NPM
- Deep knowledge of software design and architecture patterns
- Obtain Security+ within the first 90 days of employment with Raft
- Highly preferred: Experience with Kubernetes
- Highly preferred: Experience with building and managing fault-tolerant, data-intensive platforms using data technologies such as Kafka, Pinot, or Flink
- Highly preferred: Experience with monitoring (i.e. Prometheus, Grafana) and logging (i.e. Fluentbit, Kibana, Loki) solutions in cloud-native environments
- Highly preferred: Solid understanding of Helm Charts
- Clearance Requirements: Ability to obtain and maintain TS/SCI clearance
We need to keep the "Highly preferred:" prefix? It's part of the line. We'll keep as is.
Now Benefits (What we will offer you):
List:
- Highly competitive salary
- Fully covered healthcare, dental, and vision coverage
- 401(k) and company match
- Take as you need PTO + 11 paid holidays
- Education & training benefits
- Annual budget for your tech/gadgets needs
- Monthly box of yummy snacks to eat while doing meaningful work
- Remote, hybrid, and flexible work options
- Team off-site in fun places!
- Generous Referral Bonuses
- And More!
We need to keep exactly.
Now Pay: Salary Range: $120,000 - $180,000 plus note: "The determination of compensation is predicated upon a candidate's comprehensive experience, demonstrated skill, and proven abilities". Should we include that note? It's substantive. We'll include as part of Pay section maybe as a second sentence.
Thus Pay section: Salary Range: $120,000 - $180,000. The determination of compensation is predicated upon a candidate's comprehensive experience, demonstrated skill, and proven abilities.
Schedule: Work Type: On-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel.
We'll output as On-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel.
Now ensure we don't include any boilerplate like EEO etc. We removed.
Now output HTML fragment.
Check for duplicate content: We included "Highly competitive salary" in Benefits and also Salary Range in Pay. That's okay as it's from posting.
Now ensure we didn't miss any substantive info: The "U.S. based position. All of the programs we support require U.S. citizenship to be eligible for employment. All work must be conducted within
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. We need to decide which sections to include based on content. We have: - About the role: paragraph describing building data platform for DoD, technologies. - What you will do: list of duties (Build data infrastructure..., Build ETL pipelines..., Leverage software engineering principles...). That's a list. - What we are looking for: list of requirements (Three plus years..., Experience with large-scale relational..., Experience or knowledge of service mesh..., Experience with supporting enterprise Cloud..., Experience in automation languages..., Experience in data management..., Experience with building and releasing software in cloud-native environments, Experience using a variety of package managers..., Deep knowledge of software design..., Obtain Security+ within first 90 days..., Highly preferred: Experience with Kubernetes..., Experience with building and managing fault-tolerant..., Experience with monitoring and logging..., Solid understanding of Helm Charts). That's a list. - Clearance Requirements: Ability to obtain and maintain TS/SCI clearance. That's a requirement; could be part of Requirements or separate? Could be a subsection but we can include in Requirements list. - Work Type: On-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel. That's schedule info. - Salary Range: $120,000 - $180,000; plus note about determination. - Benefits: list of offerings: Highly competitive salary (but we already have salary), Fully covered healthcare, dental, and vision coverage, 401(k) and company match, Take as you need PTO + 11 paid holidays, Education & training benefits, Annual budget for your tech/gadgets needs, Monthly box of yummy snacks, Remote, hybrid, and flexible work options, Team off-site in fun places!, Generous Referral Bonuses, And More! We need to avoid duplication: "Highly competitive salary" duplicates salary info; we can still include but maybe we should not duplicate. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that benefit line as part of benefits, even if repeats salary. But we could combine? Probably keep as is. We also have Vision Statement etc. That's boilerplate? It's not EEO but it's cultural description; maybe we can keep as prose under a section like "About the company" but we already have "Who we are" at start. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who we are" paragraph at start is substantive about company; we could include as an "About the company" section but not listed as allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? But that's already about role. Maybe we can incorporate into About the role paragraph? The "Who we are" is separate from About the role. Could we treat it as part of About the role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It says "include a section ONLY when the posting has real, specific content for it". It doesn't say we cannot add other headings, but better to stick to those. We could incorporate the "Who we are" into About the role as a preamble paragraph. That would preserve info.
Similarly, Vision Statement etc could be omitted as boilerplate? It's not EEO but it's cultural vision; maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Vision statement is not explicitly listed, but could be considered fluff. Safer to omit? But we need to preserve ALL substantive information. Is vision statement substantive? It's about company culture; maybe considered substantive but not required for job. However, we could keep it as a paragraph under About the role or as a separate section like "About the company" but not in allowed headings. Might be okay to include as a paragraph under About the role before the role description.
We need to avoid duplication: The "Who we are" and later "Our Vision Statement" etc may duplicate some ideas. We'll keep the first "Who we are" paragraph and maybe skip the later vision statements to avoid duplication.
Now decide sections:
- About the role: combine "Who we are" + "About the role" paragraph.
- Responsibilities: "What you will do" list.
- Requirements: "What we are looking for" list + Clearance Requirements.
- Benefits: "What we will offer you" list.
- Pay: Salary Range.
- Schedule: Work Type (On-site locations, travel).
We should not include Qualifications or Skills unless we have specific content; we could treat Requirements as qualifications. But we already have Requirements section.
We need to output only HTML fragment, no /, no markdown.
We'll produce:
About the role
... combined paragraph ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
Salary Range: $120,000 - $180,000
Schedule
On-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel.
We need to ensure we preserve all substantive info from the lists. Let's extract the exact text. From posting: About the role paragraph: "Raft is building a data platform for the Department of Defense (DoD), aimed at enhancing operators' awareness of critical data. This data is subsequently enriched, rendered queryable, and ultimately presented as a common operational picture to empower operators in making time critical and pertinent decisions. Key technologies include Kafka, Kafka Streams, Pinot, Java, Scala, and Kubernetes. Your involvement in this role will encompass hands-on collaboration with a team of accomplished individuals, collectively striving towards excellence." We also have "Who we are:" paragraph: "Raft (https://TeamRaft.com) is a customer-obsessed non-traditional defense tech company dedicated to empowering U.S. military and government agencies with cutting-edge AI/ML and data solutions. We are a leader in autonomous data fusion and Agentic AI, with a purposeful focus on Distributed Data Systems, Platforms at Scale, and Complex Application Development. With headquarters in McLean, VA, our range of clients includes innovative federal and public agencies leveraging design thinking, cutting-edge tech stack, and cloud-native ecosystem. We build digital solutions that impact the lives of millions of Americans." We can combine: maybe start with Who we are then About the role. Thus About the role section p: combine both paragraphs. Now Responsibilities (What you will do): - Build data infrastructure and platforms using diverse data frameworks such as Apache Kafka, Flink, and Kafka Streams - Build Extract, Transform, Load (ETL) pipelines to enable comprehensive data operations - Leverage software engineering principles to architect, develop, and implement large scale data applications We need to keep exactly as given. Now Requirements (What we are looking for): List: - Three plus years of hands-on relevant industry experience - Experience with large-scale relational and non-relational databases such as PostgreSQL, MySQL, MongoDB, and Elasticsearch to handle low-latency requirements - Experience or knowledge of service mesh technologies, such as Istio - Experience with supporting enterprise Cloud applications or infrastructure - Experience in automation languages like Python or GoLang - Experience in data management including ETL processing, data governance, and data storage - Experience with building and releasing software in cloud-native environments - Experience using a variety of package managers/dependency managers including Maven, Gradle, and NPM - Deep knowledge of software design and architecture patterns - Obtain Security+ within the first 90 days of employment with Raft - Highly preferred: Experience with Kubernetes - Highly preferred: Experience with building and managing fault-tolerant, data-intensive platforms using data technologies such as Kafka, Pinot, or Flink - Highly preferred: Experience with monitoring (i.e. Prometheus, Grafana) and logging (i.e. Fluentbit, Kibana, Loki) solutions in cloud-native environments - Highly preferred: Solid understanding of Helm Charts - Clearance Requirements: Ability to obtain and maintain TS/SCI clearance We need to keep the "Highly preferred:" prefix? It's part of the line. We'll keep as is. Now Benefits (What we will offer you): List: - Highly competitive salary - Fully covered healthcare, dental, and vision coverage - 401(k) and company match - Take as you need PTO + 11 paid holidays - Education & training benefits - Annual budget for your tech/gadgets needs - Monthly box of yummy snacks to eat while doing meaningful work - Remote, hybrid, and flexible work options - Team off-site in fun places! - Generous Referral Bonuses - And More! We need to keep exactly. Now Pay: Salary Range: $120,000 - $180,000 plus note: "The determination of compensation is predicated upon a candidate's comprehensive experience, demonstrated skill, and proven abilities". Should we include that note? It's substantive. We'll include as part of Pay section maybe as a second sentence. Thus Pay section:Salary Range: $120,000 - $180,000. The determination of compensation is predicated upon a candidate's comprehensive experience, demonstrated skill, and proven abilities.
Schedule: Work Type: On-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel. We'll output asOn-site in Dayton, OH; On-site in Tampa, FL; May require up to 25% travel.
Now ensure we don't include any boilerplate like EEO etc. We removed. Now output HTML fragment. Check for duplicate content: We included "Highly competitive salary" in Benefits and also Salary Range in Pay. That's okay as it's from posting. Now ensure we didn't miss any substantive info: The "U.S. based position. All of the programs we support require U.S. citizenship to be eligible for employment. All work must be conducted within