Senior Software Engineer II, Network Datapath

We need to output HTML fragment with sections: About the role (maybe "About The Role" heading), Responsibilities (What You'll Be Doing), Requirements/Qualifications (What We're Looking For, Experience With Hardware-accelerated Networking Is Highly Valuable, At the Senior Engineer level..., Nice to Have). Also Benefits, Pay, Schedule sections if present. The posting includes Compensation Range $167,200 - $209,000 and mentions hybrid role. Also benefits described: reimbursement for conferences, training, education, LinkedIn Learning, Employee Assistance Program, Local Employee Meetups, flexible time off policy, equity compensation, bonus, etc. So we can include Benefits section summarizing those. Pay section: compensation range. Schedule: hybrid role (maybe mention hybrid). Should we include Schedule? The posting says "This is a hybrid role". So schedule: hybrid (maybe remote/onsite). We'll include a Schedule section with that. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, equal-opportunity, scam-warning, application instructions, etc. Also remove duplicated lines. We need to preserve all substantive information. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which sections to include: About the role, Responsibilities, Requirements (maybe combine Qualifications and Skills), Benefits, Pay, Schedule. Possibly also "Nice to Have" could be part of Requirements or separate? Could be under Requirements as a sublist? But we need to follow rule: use heading only when posting has real specific content. Nice to Have is specific content, so we could include a section "Nice to Have" or incorporate into Requirements. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Nice to Have into one "Requirements" section with sublists? But we need to use

  • for any list. Could have separate headings for "Required Qualifications" and "Preferred Qualifications". That's two sections but still substantive. However they said prefer a few substantive sections over many thin ones. Might be okay to have Required and Preferred as separate sections. But we could also have one "Requirements" section with two sublists: Required and Preferred. However we need headings for sublists? Not required; we can just have paragraphs indicating required vs preferred. But better to follow typical format: "Requirements" and "Preferred Qualifications". That's two sections. Also "Experience With Hardware-accelerated Networking Is Highly Valuable." could be part of Requirements. Also "At the Senior Engineer level, you will be expected to:" could be part of Responsibilities or Expectations. Could be a separate section "Expectations". But we can incorporate into Responsibilities. We need to avoid filler like "commensurate with experience". Not present. Let's extract content. About The Role: paragraph after "About The Role". We'll copy that paragraph. Responsibilities: "What You'll Be Doing" bullet list (actually each line starts with a verb). We'll make
    • each line. Requirements: "What We're Looking For" bullet list (each line). Also "Experience With Hardware-accelerated Networking Is Highly Valuable." bullet list (each line). Also "At the Senior Engineer level, you will be expected to:" bullet list. Also "Nice to Have" bullet list. We could combine all into one Requirements section with subheadings? But we need to use headings only for sections. Could have subheadings inside? Not allowed? Only headings are

      . Could we use

      ? Not allowed per instruction: use

      for section headings. It doesn't forbid other headings but says use

      for section headings. Safer to only use

      . So we cannot add other heading levels. So we need to decide: either make multiple sections each with its own

      , or combine into one section with paragraphs and lists. Given "Prefer a few substantive sections over many thin ones", we should combine into fewer sections. Let's make sections: About the role, Responsibilities, Requirements (including required, preferred, senior expectations), Benefits, Pay, Schedule. Within Requirements section, we can have multiple paragraphs and lists. We can separate required vs preferred via paragraphs like "Required:" then list, "Preferred:" then list. That's okay. Now Benefits: we need to capture all benefits described: reimbursement for relevant conferences, training, and education; LinkedIn Learning's 10,000+ courses; Employee Assistance Program; Local Employee Meetups; flexible time off policy; equity compensation (equity grants upon hire, option to participate in Employee Stock Purchase Program); bonus (based on company and individual performance). Also maybe "competitive array of benefits". We'll list those. Pay: compensation range $167,200 - $209,000. Schedule: hybrid role. Now ensure we don't include boilerplate like "DigitalOcean is an equal-opportunity employer..." etc. Remove that. Also remove "Application Limit: You may apply to a maximum of 3 positions within any 180-day period." etc. Also remove "JR: 2026-8151" (Job ID). Also remove "Why DigitalOcean" section? That contains substantive info about why you'd like working there, but that is similar to Benefits? It includes "We innovate with purpose...", "We prioritize career development...", "We care about your well-being...", "We reward our employees." This is essentially benefits and culture. Could be part of Benefits or a separate "Why DigitalOcean" section. But we already have Benefits section covering many of those points. The "Why DigitalOcean" includes career development, well-being, rewards. We can incorporate those into Benefits. However we must not invent or summarize away detail. We need to preserve all substantive information. So we need to include the points from "Why DigitalOcean": innovate with purpose, cutting-edge technology company, upward trajectory, proud to simplify cloud and AI, builders can spend more time creating software that changes the world. As a member of the team, you will be a Shark who thinks big, bold, and scrappy, like an owner with a bias for action and a powerful sense of responsibility for customers, products, employees, and decisions. We prioritize career development. At DO, you’ll do the best work of your career. You will work with some of the smartest and most interesting people in the industry. We are a high-performance organization that will always challenge you to think big. Our organizational development team will provide you with resources to ensure you keep growing. We provide employees with reimbursement for relevant conferences, training, and education. All employees have access to LinkedIn Learning's 10,000+ courses to support their continued growth and development. We care about your well-being. Regardless of your location, we will provide you with a competitive array of benefits to support you from our Employee Assistance Program to Local Employee Meetups to flexible time off policy, to name a few. While the philosophy around our benefits is the same worldwide, specific benefits may vary based on local regulations and preferences. We reward our employees. The salary range for this position is based on market data, relevant years of experience, and skills. You may qualify for a bonus in addition to base salary; bonus amounts are determined based on company and individual performance. We also provide equity compensation to eligible employees, including equity grants upon hire and the option to participate in our Employee Stock Purchase Program. Thus many of these are already captured in Benefits section (conferences, training, education, LinkedIn Learning, EAP, Local Employee Meetups, flexible time off, equity, bonus). Also career development, high-performance organization, resources to keep growing, working with smart people, etc. Those are also benefits/culture. We could include them in Benefits section as bullet points. Thus we can have Benefits section covering: career development resources, reimbursement for conferences/training/education, LinkedIn Learning access, Employee Assistance Program, Local Employee Meetups, flexible time off policy, equity compensation (grants upon hire, ESPP), performance-based bonus, innovative purpose-driven work, high-performance culture, working with smart people, etc. Now ensure we don't repeat same info. Now produce HTML. Structure:

      About the role

      ...

      Responsibilities

      • Design, develop, and optimize high-performance network datapath software for DigitalOcean's cloud infrastructure.
      ...

      Requirements

      Required:

      • Strong experience designing and developing production software in C, C++, or Go.
      ...

      Preferred:

      • Experience working on cloud networking or hyperscale infrastructure.
      ...

      Senior Engineer expectations:

      • Own significant technical components and deliver them from design through production.
      ...

      Benefits

      • Career development: reimbursement for relevant conferences, training, and education; access to LinkedIn Learning's 10,000+ courses; organizational development resources to keep growing.
      • Work with some of the smartest and most interesting people in the industry; high‑performance organization that challenges you to think big.
      • Employee Assistance Program, Local Employee Meetups, flexible time off policy.
      • Equity compensation: equity grants upon hire and option to participate in the Employee Stock Purchase Program.
      • Performance‑based bonus in addition to base salary.
      • Innovative, purpose‑driven mission to simplify cloud and AI so builders can focus on creating world‑changing software.

      Pay

      $167,200 - $209,000 base salary range.

      Schedule

      Hybrid role.

      Check we didn't miss any substantive info: The "About The Role" paragraph: "DigitalOcean is looking for a Senior Software Engineer, Network Datapath to help build and evolve the software that powers high-performance networking across our cloud infrastructure. You will work at the intersection of networking, operating systems, distributed systems, and high-performance software, developing datapath technologies that enable DigitalOcean to deliver high throughput, low latency, and predictable network performance at scale. This role will focus on the software running in and around the network datapath, including packet processing, forwarding, routing, acceleration, observability, and integration with host and hardware-based networking components. You will work closely with Network Infrastructure, Compute, Availability, and hardware teams to design, implement, optimize, and operate production networking systems. The ideal candidate is a strong software engineer with deep networking knowledge who enjoys working close to the system and is excited about optimizing the path that packets take through cloud infrastructure." We need to include that as paragraph. Now responsibilities list: need to capture each bullet from "What You'll Be Doing". Let's list them: - Design, develop, and optimize high-performance network datapath software for DigitalOcean's cloud infrastructure. - Build and improve packet-processing and forwarding systems with a focus on throughput, latency, CPU efficiency, scalability, and reliability. - Develop networking functionality across the host, kernel, user space, and hardware-accelerated datapath. - Work with technologies such as Linux networking, eBPF, XDP, DPDK, AF_XDP, SR-IOV, and programmable datapaths. - Analyze packet-processing paths and identify opportunities to eliminate bottlenecks and improve performance. - Develop software for routing, packet filtering, encapsulation, tunneling, load balancing, traffic steering, and network virtualization. - Build and improve datapath observability, telemetry, debugging, and performance monitoring. - Design software that integrates with DPUs, SmartNICs, programmable NICs, and other hardware acceleration technologies. - Develop automated testing