Network Engineer
Cognition · San Francisco, CA · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role (maybe heading "About the role"? The posting says "About The Role". Use for section headings. Also Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We have content: "About The Role" paragraph after that. Then "What you’ll do" which is responsibilities. Then "What we’re looking for" which is requirements/qualifications/skills. There's also "Bonus points" which could be skills or qualifications. There's no explicit Pay, Benefits, Schedule except schedule mentioned: "This role is onsite five days a week. We value teamwork and in-person collaboration." That's schedule info (onsite five days a week). So we can include a Schedule section with that content.
Benefits: none mentioned. Pay: none. So we omit those.
We need to avoid repeating job title as heading. No Job ID.
We need to remove boilerplate: EEO etc. Remove equal opportunity paragraph.
We need to preserve all substantive info.
We need to use
for section headings. Also Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We have content: "About The Role" paragraph after that. Then "What you’ll do" which is responsibilities. Then "What we’re looking for" which is requirements/qualifications/skills. There's also "Bonus points" which could be skills or qualifications. There's no explicit Pay, Benefits, Schedule except schedule mentioned: "This role is onsite five days a week. We value teamwork and in-person collaboration." That's schedule info (onsite five days a week). So we can include a Schedule section with that content.
Benefits: none mentioned. Pay: none. So we omit those.
We need to avoid repeating job title as heading. No Job ID.
We need to remove boilerplate: EEO etc. Remove equal opportunity paragraph.
We need to preserve all substantive info.
We need to use - for any list of duties/requirements/benefits. The responsibilities are a paragraph with multiple sentences; could be turned into list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. The responsibilities section is a list of duties; we could format as
- each duty. But we need to decide if it's a list. The posting has bullet-like sentences separated by periods. Could treat as list items. Safer to make
- for each distinct duty. Similarly for requirements: list items.
We need to preserve all info, not invent.
Let's extract sections:
About the role: paragraph: "We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data. This role is onsite five days a week. We value teamwork and in-person collaboration."
But schedule part we might separate.
Better: About the role: first sentences up to "operational data." Then schedule separate.
Let's parse:
- About the role: "We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data."
- Schedule: "This role is onsite five days a week. We value teamwork and in-person collaboration."
Responsibilities (What you’ll do): multiple bullet-like sentences:
1. Own scalable networks and office delivery
- Design, deploy, and operate high-performance wired and wireless networks across offices, branches, and large campus environments, including RF optimization and resilient architectures using technologies such as VLANs, LACP, OSPF, BGP, VRFs, QoS, and redundant internet and core paths.
- Own network delivery for offices, expansions, and moves—from procurement, circuit turn-up, and vendor coordination through cutover and handoff—and, as Cognition scales, build secure connectivity across offices, cloud infrastructure, and Devin environments using VPC peering, transit networking, IPsec, GRE, or SD-WAN.
- Create repeatable reference architectures, configuration and lifecycle standards, high-availability patterns, capacity models, inventories, diagrams, runbooks, and deployment playbooks for a growing global footprint.
2. Build observable and automated network operations
- Own network monitoring and observability across availability, performance, capacity, and employee experience, using telemetry and analytics to identify degradation before customers report it.
- Develop scripts, reusable tooling, and data pipelines in Python, Go, TypeScript, or another modern language to improve reliability and turn network data into actionable insight.
- Apply infrastructure-as-code, APIs, source control, and CI/CD to automate network configuration and deployment.
- Use Devin and AI to improve network reliability, building the skills, context, and runbooks needed for effective troubleshooting and automation.
3. Secure access and serve our stakeholders
- Implement secure, identity-aware network access, segmentation, certificate-based authentication, and least-privilege infrastructure administration.
- Partner with Security on firewalls, threat detection and prevention, secure remote access, and incident response.
- Troubleshoot systematically across the OSI model, using packet analysis and telemetry to isolate root causes across clients, RF, switching, routing, applications, and external providers.
- Build trusted relationships with stakeholders, listen to their experience, communicate clearly during incidents, and continuously improve rather than accepting that the network is “good enough.”
We could break into
- each top-level bullet? Might be too granular. Simpler: treat each sentence as
- . But we need to preserve all info; we can embed subdetails inside
- as prose.
Let's produce
- for each major duty block.
Similarly Requirements: "What we’re looking for" list:
- 5+ years of hands-on experience designing, deploying, and operating enterprise or campus networks, or equivalent practical experience.
- Experience building and operating networks in a hypergrowth startup, with a track record of thriving amid rapid change, ambiguity, and high ownership.
- A bachelor’s degree in computer science, information technology, network engineering, or a related discipline—or equivalent practical experience.
- Demonstrated depth in wireless RF engineering and enterprise switching and routing, including successful delivery of branch offices or large office environments.
- Strong knowledge of TCP/IP, DNS, DHCP, Ethernet, Wi-Fi, routing protocols, VPN and zero-trust remote access technologies such as Cloudflare WARP, and structured troubleshooting across the OSI model.
- Experience designing for high availability, fault isolation, capacity, and scale across critical network services and connectivity paths.
- Experience with network performance monitoring, telemetry, alerting, and analytics, with a track record of using operational data to improve reliability or customer experience.
- Experience automating network operations with a modern programming or scripting language and applying APIs, infrastructure-as-code, Git, or CI/CD to configuration delivery.
- Working knowledge of network security and identity controls, including IEEE 802.1X, NAC, AAA, RBAC, segmentation, IDS/IPS, or related technologies.
- Experience coordinating carriers, contractors, and vendors while maintaining clear internal ownership of architecture, quality, documentation, and outcomes.
- Strong judgment, communication, and service orientation, with a track record of carrying ambiguous problems through design, implementation, and ongoing operation.
Then "An ideal candidate will bring" list of traits: Ownership, Customer focus, Builder mindset, Curiosity. Could be under Skills or Qualities. We could put under Skills section.
Bonus points list: could be under Skills as well.
We need sections: About the role, Responsibilities, Requirements, Skills, Schedule.
We need to avoid empty sections.
Let's craft HTML:
About the role
We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data.
Responsibilities
- Own scalable networks and office delivery: design, deploy, and operate high-performance wired and wireless networks across offices, branches, and large campus environments, including RF optimization and resilient architectures using technologies such as VLANs, LACP, OSPF, BGP, VRFs, QoS, and redundant internet and core paths.
- Own network delivery for offices, expansions, and moves—from procurement, circuit turn-up, and vendor coordination through cutover and handoff—and, as Cognition scales, build secure connectivity across offices, cloud infrastructure, and Devin environments using VPC peering, transit networking, IPsec, GRE, or SD‑WAN.
- Create repeatable reference architectures, configuration and lifecycle standards, high‑availability patterns, capacity models, inventories, diagrams, runbooks, and deployment playbooks for a growing global footprint.
- Own network monitoring and observability across availability, performance, capacity, and employee experience, using telemetry and analytics to identify degradation before customers report it.
- Develop scripts, reusable tooling, and data pipelines in Python, Go, TypeScript, or another modern language to improve reliability and turn network data into actionable insight.
- Apply infrastructure‑as‑code, APIs, source control, and CI/CD to automate network configuration and deployment.
- Use Devin and AI to improve network reliability, building the skills, context, and runbooks needed for effective troubleshooting and automation.
- Implement secure, identity‑aware network access, segmentation, certificate‑based authentication, and least‑privilege infrastructure administration.
- Partner with Security on firewalls, threat detection and prevention, secure remote access, and incident response.
- Troubleshoot systematically across the OSI model, using packet analysis and telemetry to isolate root causes across clients, RF, switching, routing, applications, and external providers.
- Build trusted relationships with stakeholders, listen to their experience, communicate clearly during incidents, and continuously improve rather than accepting that the network is “good enough.”
Requirements
- 5+ years of hands‑on experience designing, deploying, and operating enterprise or campus networks, or equivalent practical experience.
- Experience building and operating networks in a hypergrowth startup, with a track record of thriving amid rapid change, ambiguity, and high ownership.
- A bachelor’s degree in computer science, information technology, network engineering, or a related discipline—or equivalent practical experience.
- Demonstrated depth in wireless RF engineering and enterprise switching and routing, including successful delivery of branch offices or large office environments.
- Strong knowledge of TCP/IP, DNS, DHCP, Ethernet, Wi‑Fi, routing protocols, VPN and zero‑trust remote access technologies such as Cloudflare WARP, and structured troubleshooting across the OSI model.
- Experience designing for high availability, fault isolation, capacity, and scale across critical network services and connectivity paths.
- Experience with network performance monitoring, telemetry, alerting, and analytics, with a track record of using operational data to improve reliability or customer experience.
- Experience automating network operations with a modern programming or scripting language and applying APIs, infrastructure‑as‑code, Git, or CI/CD to configuration delivery.
- Working knowledge of network security and identity controls, including IEEE 802.1X, NAC, AAA, RBAC, segmentation, IDS/IPS, or related technologies.
- Experience coordinating carriers, contractors, and vendors while maintaining clear internal ownership of architecture, quality, documentation, and outcomes.
- Strong judgment, communication, and service orientation, with a track record of carrying ambiguous problems through design, implementation, and ongoing operation.
Skills
- Ownership: treats reliability and customer experience as personal responsibilities, drives ambiguous work through completion, and remains accountable
- for any list of duties/requirements/benefits, and
for prose. The responsibilities section is a list of duties; we could format as
- each duty. But we need to decide if it's a list. The posting has bullet-like sentences separated by periods. Could treat as list items. Safer to make
- for each distinct duty. Similarly for requirements: list items.
We need to preserve all info, not invent.
Let's extract sections:
About the role: paragraph: "We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data. This role is onsite five days a week. We value teamwork and in-person collaboration."
But schedule part we might separate.
Better: About the role: first sentences up to "operational data." Then schedule separate.
Let's parse:
- About the role: "We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data."
- Schedule: "This role is onsite five days a week. We value teamwork and in-person collaboration."
Responsibilities (What you’ll do): multiple bullet-like sentences:
1. Own scalable networks and office delivery
- Design, deploy, and operate high-performance wired and wireless networks across offices, branches, and large campus environments, including RF optimization and resilient architectures using technologies such as VLANs, LACP, OSPF, BGP, VRFs, QoS, and redundant internet and core paths.
- Own network delivery for offices, expansions, and moves—from procurement, circuit turn-up, and vendor coordination through cutover and handoff—and, as Cognition scales, build secure connectivity across offices, cloud infrastructure, and Devin environments using VPC peering, transit networking, IPsec, GRE, or SD-WAN.
- Create repeatable reference architectures, configuration and lifecycle standards, high-availability patterns, capacity models, inventories, diagrams, runbooks, and deployment playbooks for a growing global footprint.
2. Build observable and automated network operations
- Own network monitoring and observability across availability, performance, capacity, and employee experience, using telemetry and analytics to identify degradation before customers report it.
- Develop scripts, reusable tooling, and data pipelines in Python, Go, TypeScript, or another modern language to improve reliability and turn network data into actionable insight.
- Apply infrastructure-as-code, APIs, source control, and CI/CD to automate network configuration and deployment.
- Use Devin and AI to improve network reliability, building the skills, context, and runbooks needed for effective troubleshooting and automation.
3. Secure access and serve our stakeholders
- Implement secure, identity-aware network access, segmentation, certificate-based authentication, and least-privilege infrastructure administration.
- Partner with Security on firewalls, threat detection and prevention, secure remote access, and incident response.
- Troubleshoot systematically across the OSI model, using packet analysis and telemetry to isolate root causes across clients, RF, switching, routing, applications, and external providers.
- Build trusted relationships with stakeholders, listen to their experience, communicate clearly during incidents, and continuously improve rather than accepting that the network is “good enough.”
We could break into
- each top-level bullet? Might be too granular. Simpler: treat each sentence as
- . But we need to preserve all info; we can embed subdetails inside
- as prose.
Let's produce
- for each major duty block.
Similarly Requirements: "What we’re looking for" list:
- 5+ years of hands-on experience designing, deploying, and operating enterprise or campus networks, or equivalent practical experience.
- Experience building and operating networks in a hypergrowth startup, with a track record of thriving amid rapid change, ambiguity, and high ownership.
- A bachelor’s degree in computer science, information technology, network engineering, or a related discipline—or equivalent practical experience.
- Demonstrated depth in wireless RF engineering and enterprise switching and routing, including successful delivery of branch offices or large office environments.
- Strong knowledge of TCP/IP, DNS, DHCP, Ethernet, Wi-Fi, routing protocols, VPN and zero-trust remote access technologies such as Cloudflare WARP, and structured troubleshooting across the OSI model.
- Experience designing for high availability, fault isolation, capacity, and scale across critical network services and connectivity paths.
- Experience with network performance monitoring, telemetry, alerting, and analytics, with a track record of using operational data to improve reliability or customer experience.
- Experience automating network operations with a modern programming or scripting language and applying APIs, infrastructure-as-code, Git, or CI/CD to configuration delivery.
- Working knowledge of network security and identity controls, including IEEE 802.1X, NAC, AAA, RBAC, segmentation, IDS/IPS, or related technologies.
- Experience coordinating carriers, contractors, and vendors while maintaining clear internal ownership of architecture, quality, documentation, and outcomes.
- Strong judgment, communication, and service orientation, with a track record of carrying ambiguous problems through design, implementation, and ongoing operation.
Then "An ideal candidate will bring" list of traits: Ownership, Customer focus, Builder mindset, Curiosity. Could be under Skills or Qualities. We could put under Skills section.
Bonus points list: could be under Skills as well.
We need sections: About the role, Responsibilities, Requirements, Skills, Schedule.
We need to avoid empty sections.
Let's craft HTML:
About the role
We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data.
Responsibilities
- Own scalable networks and office delivery: design, deploy, and operate high-performance wired and wireless networks across offices, branches, and large campus environments, including RF optimization and resilient architectures using technologies such as VLANs, LACP, OSPF, BGP, VRFs, QoS, and redundant internet and core paths.
- Own network delivery for offices, expansions, and moves—from procurement, circuit turn-up, and vendor coordination through cutover and handoff—and, as Cognition scales, build secure connectivity across offices, cloud infrastructure, and Devin environments using VPC peering, transit networking, IPsec, GRE, or SD‑WAN.
- Create repeatable reference architectures, configuration and lifecycle standards, high‑availability patterns, capacity models, inventories, diagrams, runbooks, and deployment playbooks for a growing global footprint.
- Own network monitoring and observability across availability, performance, capacity, and employee experience, using telemetry and analytics to identify degradation before customers report it.
- Develop scripts, reusable tooling, and data pipelines in Python, Go, TypeScript, or another modern language to improve reliability and turn network data into actionable insight.
- Apply infrastructure‑as‑code, APIs, source control, and CI/CD to automate network configuration and deployment.
- Use Devin and AI to improve network reliability, building the skills, context, and runbooks needed for effective troubleshooting and automation.
- Implement secure, identity‑aware network access, segmentation, certificate‑based authentication, and least‑privilege infrastructure administration.
- Partner with Security on firewalls, threat detection and prevention, secure remote access, and incident response.
- Troubleshoot systematically across the OSI model, using packet analysis and telemetry to isolate root causes across clients, RF, switching, routing, applications, and external providers.
- Build trusted relationships with stakeholders, listen to their experience, communicate clearly during incidents, and continuously improve rather than accepting that the network is “good enough.”
Requirements
- 5+ years of hands‑on experience designing, deploying, and operating enterprise or campus networks, or equivalent practical experience.
- Experience building and operating networks in a hypergrowth startup, with a track record of thriving amid rapid change, ambiguity, and high ownership.
- A bachelor’s degree in computer science, information technology, network engineering, or a related discipline—or equivalent practical experience.
- Demonstrated depth in wireless RF engineering and enterprise switching and routing, including successful delivery of branch offices or large office environments.
- Strong knowledge of TCP/IP, DNS, DHCP, Ethernet, Wi‑Fi, routing protocols, VPN and zero‑trust remote access technologies such as Cloudflare WARP, and structured troubleshooting across the OSI model.
- Experience designing for high availability, fault isolation, capacity, and scale across critical network services and connectivity paths.
- Experience with network performance monitoring, telemetry, alerting, and analytics, with a track record of using operational data to improve reliability or customer experience.
- Experience automating network operations with a modern programming or scripting language and applying APIs, infrastructure‑as‑code, Git, or CI/CD to configuration delivery.
- Working knowledge of network security and identity controls, including IEEE 802.1X, NAC, AAA, RBAC, segmentation, IDS/IPS, or related technologies.
- Experience coordinating carriers, contractors, and vendors while maintaining clear internal ownership of architecture, quality, documentation, and outcomes.
- Strong judgment, communication, and service orientation, with a track record of carrying ambiguous problems through design, implementation, and ongoing operation.
Skills
- Ownership: treats reliability and customer experience as personal responsibilities, drives ambiguous work through completion, and remains accountable
- for each major duty block.
Similarly Requirements: "What we’re looking for" list:
- 5+ years of hands-on experience designing, deploying, and operating enterprise or campus networks, or equivalent practical experience.
- Experience building and operating networks in a hypergrowth startup, with a track record of thriving amid rapid change, ambiguity, and high ownership.
- A bachelor’s degree in computer science, information technology, network engineering, or a related discipline—or equivalent practical experience.
- Demonstrated depth in wireless RF engineering and enterprise switching and routing, including successful delivery of branch offices or large office environments.
- Strong knowledge of TCP/IP, DNS, DHCP, Ethernet, Wi-Fi, routing protocols, VPN and zero-trust remote access technologies such as Cloudflare WARP, and structured troubleshooting across the OSI model.
- Experience designing for high availability, fault isolation, capacity, and scale across critical network services and connectivity paths.
- Experience with network performance monitoring, telemetry, alerting, and analytics, with a track record of using operational data to improve reliability or customer experience.
- Experience automating network operations with a modern programming or scripting language and applying APIs, infrastructure-as-code, Git, or CI/CD to configuration delivery.
- Working knowledge of network security and identity controls, including IEEE 802.1X, NAC, AAA, RBAC, segmentation, IDS/IPS, or related technologies.
- Experience coordinating carriers, contractors, and vendors while maintaining clear internal ownership of architecture, quality, documentation, and outcomes.
- Strong judgment, communication, and service orientation, with a track record of carrying ambiguous problems through design, implementation, and ongoing operation.
Then "An ideal candidate will bring" list of traits: Ownership, Customer focus, Builder mindset, Curiosity. Could be under Skills or Qualities. We could put under Skills section.
Bonus points list: could be under Skills as well.
We need sections: About the role, Responsibilities, Requirements, Skills, Schedule.
We need to avoid empty sections.
Let's craft HTML:
- for each distinct duty. Similarly for requirements: list items.
We need to preserve all info, not invent.
Let's extract sections:
About the role: paragraph: "We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data. This role is onsite five days a week. We value teamwork and in-person collaboration."
But schedule part we might separate.
Better: About the role: first sentences up to "operational data." Then schedule separate.
Let's parse:
- About the role: "We’re looking for a Network Engineer to own the reliability, security, and evolution of Cognition’s global office networks. Strong candidates have operated networks in a hypergrowth startup and thrive amid rapid change, ambiguity, and high ownership. They will apply deep wireless and routing expertise and a builder mindset to deliver scalable wired, wireless, and cloud-connected networks, repeatable office infrastructure, and strong observability and automation. Working across internal teams, carriers, and partners, they will own outcomes end to end and continuously improve the network through stakeholder feedback and operational data."
- Schedule: "This role is onsite five days a week. We value teamwork and in-person collaboration."
Responsibilities (What you’ll do): multiple bullet-like sentences:
1. Own scalable networks and office delivery
- Design, deploy, and operate high-performance wired and wireless networks across offices, branches, and large campus environments, including RF optimization and resilient architectures using technologies such as VLANs, LACP, OSPF, BGP, VRFs, QoS, and redundant internet and core paths.
- Own network delivery for offices, expansions, and moves—from procurement, circuit turn-up, and vendor coordination through cutover and handoff—and, as Cognition scales, build secure connectivity across offices, cloud infrastructure, and Devin environments using VPC peering, transit networking, IPsec, GRE, or SD-WAN.
- Create repeatable reference architectures, configuration and lifecycle standards, high-availability patterns, capacity models, inventories, diagrams, runbooks, and deployment playbooks for a growing global footprint.
2. Build observable and automated network operations
- Own network monitoring and observability across availability, performance, capacity, and employee experience, using telemetry and analytics to identify degradation before customers report it.
- Develop scripts, reusable tooling, and data pipelines in Python, Go, TypeScript, or another modern language to improve reliability and turn network data into actionable insight.
- Apply infrastructure-as-code, APIs, source control, and CI/CD to automate network configuration and deployment.
- Use Devin and AI to improve network reliability, building the skills, context, and runbooks needed for effective troubleshooting and automation.
3. Secure access and serve our stakeholders
- Implement secure, identity-aware network access, segmentation, certificate-based authentication, and least-privilege infrastructure administration.
- Partner with Security on firewalls, threat detection and prevention, secure remote access, and incident response.
- Troubleshoot systematically across the OSI model, using packet analysis and telemetry to isolate root causes across clients, RF, switching, routing, applications, and external providers.
- Build trusted relationships with stakeholders, listen to their experience, communicate clearly during incidents, and continuously improve rather than accepting that the network is “good enough.”
We could break into
- each duty. But we need to decide if it's a list. The posting has bullet-like sentences separated by periods. Could treat as list items. Safer to make