Senior Cloud Network Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include only sections with real specific content. We need to extract content from posting.
We have sections: About Simplesense (company description) maybe not needed? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly.
We have "About the Role" section: description of role responsibilities. Could be placed under About the role
with paragraphs.
Responsibilities: bullet list of duties under "What You’ll Do". So we can put Responsibilities
with - items.
Requirements: maybe "What You Bring Required Qualifications". That's required qualifications. Could be
Requirements
with list.
Qualifications: maybe "Preferred Qualifications". Could be Qualifications
(or Preferred Qualifications). But we have both Required and Preferred. Could combine? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate. Use Requirements for required qualifications, Qualifications for preferred qualifications.
Skills: maybe we can extract from required qualifications: expertise list. Could be a Skills section. But we might not need separate if covered. However we can include Skills if we have specific skill list. The posting includes: Deep understanding of VPC design, subnetting, Route53, transit gateways, PrivateLink and related AWS technologies; experience troubleshooting complex connectivity issues across multi-account or hybrid on-prem/cloud environments. IaC and Automated Deployment: Experience deploying network infrastructure with CloudFormation or Terraform, and CI/CD tools such as GitHub Actions. Ownership, Observability, Travel, Compliance, Privileged Access Requirements, Security Clearance. Those are more qualifications than skills. But we could still make a Skills section for technical skills: VPC design, subnetting, Route53, transit gateways, PrivateLink, AWS, troubleshooting, IaC (CloudFormation/Terraform), CI/CD (GitHub Actions), observability, etc. Might be okay.
Benefits: The posting lists Competitive Benefits: Equity, Medical, Life, Short-Term Disability, and AD&D insurance, Medical travel coverage, Dental coverage, Vision coverage, 401k matching. So we can have Benefits section.
Pay: Pay Range: $155k-195k per year. So Pay section.
Schedule: Not explicitly mentioned. There's work model: hybrid, quarterly travel. Could be considered Schedule? Not exactly schedule like full-time/part-time. The instruction: only include Pay/Schedule/Benefits if posting actually states them. Schedule not stated explicitly; we have work model but not schedule. Might skip Schedule.
We also need to include maybe a short paragraph for metadata like location etc. Could be placed in a under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location info in a paragraph.
We must remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, navigation, cookie, legal. Also remove duplicated lines.
We need to preserve all substantive information.
Let's extract content:
Company description: "Simplesense builds, deploys, and sustains the Installation Resilience Platform that enables mission operators to rapidly adapt and respond. The Platform protects critical infrastructure from cyber attack while unlocking previously siloed information to monitor, diagnose, and improve response times to incidents. Our adversaries rapidly adopt the latest technology: we help defense users respond in kind. Simplesense is a non-traditional defense contractor and prime on the Air Force's Installation Resilience Operations Command and Control (IROC) program, which is now expanding to five additional Air Force, Space Force, and Army installations from the one prototype installation, Tyndall Air Force Base. Our team combines over 100 years of direct mission experience solving hard problems with 50 years technical expertise deploying DevSecOps, cybersecurity, and cloud infrastructure, giving us a deep appreciation for our customers’ mission and end users’ priorities. We build for scale, architecting and prioritizing technical work for long term sustainability."
Then "About Simplesense" repeats similar content. We'll keep one concise paragraph maybe.
But we need to include substantive info; we can include a brief "About Simplesense" paragraph maybe not under a heading (since headings limited). Could be placed as a
before sections.
Now role specifics:
About the Role: "As a Senior Cloud Network Engineer, you are responsible for leading the deployment and operation of a distributed cloud network infrastructure and interface to on-premise connectivity. You will act as the technical owner for cloud network components and drive improvements to ensure reliability, scalability and security. This role is a critical member of the team helping to ensure that our hybrid platform meets the demanding expectations of our customers."
Work Model: "We prioritize candidates who reside in the Denver, CO area, (hybrid as needed) but we are open to exceptional remote talent. Locals: Onsite as needed for collaborative workspace time. Remote: Quarterly travel to hub locations for team syncs and alignment."
Our Performance Culture: core values etc. Might be considered part of About the role or separate? Could be included under About the role as prose.
What You’ll Do: list of responsibilities.
What You Bring Required Qualifications: list.
Preferred Qualifications: list.
What Success Looks Like: 30/60/90 days.
Compensation and Benefits: Pay Range and Benefits.
We need to map to headings.
Let's create sections:
About the role
- include paragraphs: role description, work model, performance culture (maybe as prose).
Responsibilities
- ul list from "What You’ll Do".
Requirements
- ul list from Required Qualifications.
Qualifications
- ul list from Preferred Qualifications.
Skills
- maybe we can extract technical skills from Required Qualifications: VPC design, subnetting, Route53, transit gateways, PrivateLink, AWS technologies, troubleshooting complex connectivity, IaC (CloudFormation/Terraform), CI/CD (GitHub Actions), ownership, observability, travel ability, US citizenship, DoD NIPR account, CAC, privileged access, DoD Secret Clearance. But many are qualifications not skills. Might be okay to skip Skills section if not needed. The instruction: prefer a few substantive sections over many thin ones. So we could omit Skills if not needed.
Benefits
- ul list.
Pay
- p with pay range.
We might also include a short paragraph for location etc. Could be placed under About the role.
We must not include sections with filler like "commensurate with experience". Not present.
Now we need to ensure we don't repeat job title as heading. We'll not.
Now produce HTML fragment.
Let's craft content.
About the role paragraph:
Simplesense builds, deploys, and sustains the Installation Resilience Platform that enables mission operators to rapidly adapt and respond. The Platform protects critical infrastructure from cyber attack while unlocking previously siloed information to monitor, diagnose, and improve response times to incidents. As a Senior Cloud Network Engineer, you will lead the deployment and operation of a distributed cloud network infrastructure and interface to on‑premise connectivity, acting as the technical owner for cloud network components and driving improvements for reliability, scalability, and security. The role is hybrid‑friendly with priority given to candidates in the Denver, CO area (onsite as needed); remote workers are expected to travel quarterly to hub locations for team syncs. Simplesense values high‑trust autonomy, psychological safety, customer obsession, ruthless prioritization, and a bias for action.
That seems good.
Now Responsibilities list:
- Collaborate across engineering and user success teams to understand desired system level outcomes and operational requirements.
- Investigate, design, test, deploy and support cloud network infrastructure to ensure a resilient and secure platform.
- Manage scalable cloud network topologies, including transit gateways, VPCs, subnets, security groups, and route tables, ensuring low‑latency and secure communication between distributed services.
- Design and maintain infrastructure‑as‑code, CI/CD pipelines and configuration automation for repeatable and scalable deployments.
- Provide technical input and guidance during planning and design sessions with Principal and Staff Engineers to ensure success of the larger integrated system (e.g., service and resource deployment patterns, security controls, cost optimization).
- Deliver hands‑on technical contributions to cloud network infrastructure deployment and operation (~80% time on coding IaC, system design, reviews, troubleshooting) and mentor/coordinate with senior engineers (~20% time).
- Act as the second escalation point for complex incidents, leading thorough root cause analysis (RCA) and implementing systemic, long‑term fixes.
Now Requirements list (Required Qualifications):
- 5+ years of cloud network engineering experience.
- Deep understanding of VPC design, subnetting, Route53, transit gateways, PrivateLink and related AWS technologies.
- Experience troubleshooting complex connectivity issues across multi‑account or hybrid on‑prem/cloud environments.
- Experience deploying network infrastructure with CloudFormation or Terraform, and CI/CD tools such as GitHub Actions.
- Demonstrated ability to take ownership of a problem and deliver a production‑ready solution.
- Strong experience with observability as applied to cloud network environments.
- Ability to travel quarterly for Product Increment planning and team syncs.
- Must be a U.S. Citizen and capable of obtaining a DoD NIPR network account and Common Access Card (CAC).
- Ability to meet privileged access requirements through degree or approved technical certifications within 90 days.
- Must have, or be able to obtain, a DoD Secret Clearance.
Now Qualifications list (Preferred Qualifications):
- Strong preference for candidates residing in the Denver, CO metro area.
- Prior experience working within DoD, Air Force, Space Force, or fast‑paced Federal contractor/dual‑use startup environments.
- Relevant technical certifications: AWS Solutions Architect, AWS Advanced Networking, CloudOps, DevOps or similar AWS certification, or an advanced degree in a related field.
Now Benefits list:
- Equity
- Medical, Life, Short‑Term Disability, and AD&D insurance
- Medical travel coverage
- Dental coverage
- Vision coverage
- 401k matching
Now Pay paragraph:
- Pay range: $155,000 – $195,000 per year, based on experience, skill level, and location; ranges reviewed regularly for market competitiveness.
We could also include a short paragraph about location maybe already in About the role.
Now ensure no boilerplate: removed EEO, application process, etc.
Now output HTML fragment.
We need to use for each section heading. Use - for lists. Use
for prose.
Let's construct:
About Simplesense paragraph? Actually we included company description in About the role. Might be okay.
But we might want a separate
for company overview before sections. Not required but could be included as a
without heading. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other
outside headings. So we can have a leading
with company overview.
Let's add:
Simplesense builds, deploys, and sustains the Installation Resilience Platform that enables mission operators to rapidly adapt and respond. The Platform protects critical infrastructure from cyber attack while unlocking previously siloed
Requirements
with list. Qualifications: maybe "Preferred Qualifications". Could beQualifications
(or Preferred Qualifications). But we have both Required and Preferred. Could combine? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and Qualifications separate. Use Requirements for required qualifications, Qualifications for preferred qualifications. Skills: maybe we can extract from required qualifications: expertise list. Could be a Skills section. But we might not need separate if covered. However we can include Skills if we have specific skill list. The posting includes: Deep understanding of VPC design, subnetting, Route53, transit gateways, PrivateLink and related AWS technologies; experience troubleshooting complex connectivity issues across multi-account or hybrid on-prem/cloud environments. IaC and Automated Deployment: Experience deploying network infrastructure with CloudFormation or Terraform, and CI/CD tools such as GitHub Actions. Ownership, Observability, Travel, Compliance, Privileged Access Requirements, Security Clearance. Those are more qualifications than skills. But we could still make a Skills section for technical skills: VPC design, subnetting, Route53, transit gateways, PrivateLink, AWS, troubleshooting, IaC (CloudFormation/Terraform), CI/CD (GitHub Actions), observability, etc. Might be okay. Benefits: The posting lists Competitive Benefits: Equity, Medical, Life, Short-Term Disability, and AD&D insurance, Medical travel coverage, Dental coverage, Vision coverage, 401k matching. So we can have Benefits section. Pay: Pay Range: $155k-195k per year. So Pay section. Schedule: Not explicitly mentioned. There's work model: hybrid, quarterly travel. Could be considered Schedule? Not exactly schedule like full-time/part-time. The instruction: only include Pay/Schedule/Benefits if posting actually states them. Schedule not stated explicitly; we have work model but not schedule. Might skip Schedule. We also need to include maybe a short paragraph for metadata like location etc. Could be placed in aunder About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include location info in a paragraph. We must remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, navigation, cookie, legal. Also remove duplicated lines. We need to preserve all substantive information. Let's extract content: Company description: "Simplesense builds, deploys, and sustains the Installation Resilience Platform that enables mission operators to rapidly adapt and respond. The Platform protects critical infrastructure from cyber attack while unlocking previously siloed information to monitor, diagnose, and improve response times to incidents. Our adversaries rapidly adopt the latest technology: we help defense users respond in kind. Simplesense is a non-traditional defense contractor and prime on the Air Force's Installation Resilience Operations Command and Control (IROC) program, which is now expanding to five additional Air Force, Space Force, and Army installations from the one prototype installation, Tyndall Air Force Base. Our team combines over 100 years of direct mission experience solving hard problems with 50 years technical expertise deploying DevSecOps, cybersecurity, and cloud infrastructure, giving us a deep appreciation for our customers’ mission and end users’ priorities. We build for scale, architecting and prioritizing technical work for long term sustainability." Then "About Simplesense" repeats similar content. We'll keep one concise paragraph maybe. But we need to include substantive info; we can include a brief "About Simplesense" paragraph maybe not under a heading (since headings limited). Could be placed as a
before sections. Now role specifics: About the Role: "As a Senior Cloud Network Engineer, you are responsible for leading the deployment and operation of a distributed cloud network infrastructure and interface to on-premise connectivity. You will act as the technical owner for cloud network components and drive improvements to ensure reliability, scalability and security. This role is a critical member of the team helping to ensure that our hybrid platform meets the demanding expectations of our customers." Work Model: "We prioritize candidates who reside in the Denver, CO area, (hybrid as needed) but we are open to exceptional remote talent. Locals: Onsite as needed for collaborative workspace time. Remote: Quarterly travel to hub locations for team syncs and alignment." Our Performance Culture: core values etc. Might be considered part of About the role or separate? Could be included under About the role as prose. What You’ll Do: list of responsibilities. What You Bring Required Qualifications: list. Preferred Qualifications: list. What Success Looks Like: 30/60/90 days. Compensation and Benefits: Pay Range and Benefits. We need to map to headings. Let's create sections:
About the role
- include paragraphs: role description, work model, performance culture (maybe as prose).Responsibilities
- ul list from "What You’ll Do".Requirements
- ul list from Required Qualifications.Qualifications
- ul list from Preferred Qualifications.Skills
- maybe we can extract technical skills from Required Qualifications: VPC design, subnetting, Route53, transit gateways, PrivateLink, AWS technologies, troubleshooting complex connectivity, IaC (CloudFormation/Terraform), CI/CD (GitHub Actions), ownership, observability, travel ability, US citizenship, DoD NIPR account, CAC, privileged access, DoD Secret Clearance. But many are qualifications not skills. Might be okay to skip Skills section if not needed. The instruction: prefer a few substantive sections over many thin ones. So we could omit Skills if not needed.Benefits
- ul list.Pay
- p with pay range. We might also include a short paragraph for location etc. Could be placed under About the role. We must not include sections with filler like "commensurate with experience". Not present. Now we need to ensure we don't repeat job title as heading. We'll not. Now produce HTML fragment. Let's craft content. About the role paragraph: Simplesense builds, deploys, and sustains the Installation Resilience Platform that enables mission operators to rapidly adapt and respond. The Platform protects critical infrastructure from cyber attack while unlocking previously siloed information to monitor, diagnose, and improve response times to incidents. As a Senior Cloud Network Engineer, you will lead the deployment and operation of a distributed cloud network infrastructure and interface to on‑premise connectivity, acting as the technical owner for cloud network components and driving improvements for reliability, scalability, and security. The role is hybrid‑friendly with priority given to candidates in the Denver, CO area (onsite as needed); remote workers are expected to travel quarterly to hub locations for team syncs. Simplesense values high‑trust autonomy, psychological safety, customer obsession, ruthless prioritization, and a bias for action. That seems good. Now Responsibilities list: - Collaborate across engineering and user success teams to understand desired system level outcomes and operational requirements. - Investigate, design, test, deploy and support cloud network infrastructure to ensure a resilient and secure platform. - Manage scalable cloud network topologies, including transit gateways, VPCs, subnets, security groups, and route tables, ensuring low‑latency and secure communication between distributed services. - Design and maintain infrastructure‑as‑code, CI/CD pipelines and configuration automation for repeatable and scalable deployments. - Provide technical input and guidance during planning and design sessions with Principal and Staff Engineers to ensure success of the larger integrated system (e.g., service and resource deployment patterns, security controls, cost optimization). - Deliver hands‑on technical contributions to cloud network infrastructure deployment and operation (~80% time on coding IaC, system design, reviews, troubleshooting) and mentor/coordinate with senior engineers (~20% time). - Act as the second escalation point for complex incidents, leading thorough root cause analysis (RCA) and implementing systemic, long‑term fixes. Now Requirements list (Required Qualifications): - 5+ years of cloud network engineering experience. - Deep understanding of VPC design, subnetting, Route53, transit gateways, PrivateLink and related AWS technologies. - Experience troubleshooting complex connectivity issues across multi‑account or hybrid on‑prem/cloud environments. - Experience deploying network infrastructure with CloudFormation or Terraform, and CI/CD tools such as GitHub Actions. - Demonstrated ability to take ownership of a problem and deliver a production‑ready solution. - Strong experience with observability as applied to cloud network environments. - Ability to travel quarterly for Product Increment planning and team syncs. - Must be a U.S. Citizen and capable of obtaining a DoD NIPR network account and Common Access Card (CAC). - Ability to meet privileged access requirements through degree or approved technical certifications within 90 days. - Must have, or be able to obtain, a DoD Secret Clearance. Now Qualifications list (Preferred Qualifications): - Strong preference for candidates residing in the Denver, CO metro area. - Prior experience working within DoD, Air Force, Space Force, or fast‑paced Federal contractor/dual‑use startup environments. - Relevant technical certifications: AWS Solutions Architect, AWS Advanced Networking, CloudOps, DevOps or similar AWS certification, or an advanced degree in a related field. Now Benefits list: - Equity - Medical, Life, Short‑Term Disability, and AD&D insurance - Medical travel coverage - Dental coverage - Vision coverage - 401k matching Now Pay paragraph: - Pay range: $155,000 – $195,000 per year, based on experience, skill level, and location; ranges reviewed regularly for market competitiveness. We could also include a short paragraph about location maybe already in About the role. Now ensure no boilerplate: removed EEO, application process, etc. Now output HTML fragment. We need to use for each section heading. Use - for lists. Use
for prose.
Let's construct:
About Simplesense paragraph? Actually we included company description in About the role. Might be okay.
But we might want a separate
for company overview before sections. Not required but could be included as a
without heading. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other
outside headings. So we can have a leading
with company overview.
Let's add:
Simplesense builds, deploys, and sustains the Installation Resilience Platform that enables mission operators to rapidly adapt and respond. The Platform protects critical infrastructure from cyber attack while unlocking previously siloed
for prose. Let's construct:
About Simplesense paragraph? Actually we included company description in About the role. Might be okay. But we might want a separate
for company overview before sections. Not required but could be included as a
without heading. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other
outside headings. So we can have a leading
with company overview. Let's add:
Simplesense builds, deploys, and sustains the Installation Resilience Platform that enables mission operators to rapidly adapt and respond. The Platform protects critical infrastructure from cyber attack while unlocking previously siloed