Embedded Software Developer for RDK-B

We need to output HTML fragment with sections: About the role? The posting includes "About The Job You're Considering" and "Your Skills And Experience". Also location line. Also compensation range. Also benefits description. Must not repeat job title. Must not include metadata like Job ID. Must include sections only if real content. We need to parse content: - Location: "This is an onsite role in Santa Clara, CA." Should be maybe a

under a heading? There's no specific heading for location; we could include a

after maybe a heading "Location"? But rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create a heading "Location" if we want, but not in the list? The list includes examples but not exclusive. Probably we can add a heading for Location if we have content. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not limited. Safer to include only those headings if we have content. Location could be placed in a

without heading. - About The Job You're Considering: that's like "About the role". So heading

About the role

then paragraph(s). - Your Skills And Experience: could be "Requirements" or "Skills". We have both skills and experience. Could use

Skills

or

Requirements

. Since they list skills and experience, maybe "Skills". We'll use

Skills

. - Compensation: we have base compensation range. So heading

Pay

with paragraph containing the range and explanation. - Benefits: we have benefits description. So heading

Benefits

with paragraph(s). - Schedule: not mentioned, so omit. - Responsibilities: we have some description of duties in About the job: "design, develop, and integrate advanced networking features...". Could be responsibilities. But we already used About the role for that. Could split: About the role (overview) and Responsibilities (list). But we have limited content; better to keep About the role as overview and maybe include responsibilities within same section. The rule: prefer few substantive sections over many thin ones. So we can combine overview and responsibilities in About the role. Thus sections: About the role, Skills, Pay, Benefits. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, disclaimers, etc. Must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We must exclude the long EEO paragraph, the "Important Notice", "Disclaimers", etc. Also exclude the paragraph about Capgemini being global etc at end (that's boilerplate). Also exclude the "Physical, mental, sensory..." paragraph. Also exclude the "Click the following link..." etc. We need to keep location line, about the job paragraph, skills and experience bullet list (but we need to convert to

• ). Also compensation paragraph, benefits paragraph. Let's extract substantive content: Location: "This is an onsite role in Santa Clara, CA." About The Job You're Considering: "We are looking for an experienced Embedded Software Developer for RDK-B with strong expertise in broadband gateway technologies. In this role, you will design, develop, and integrate advanced networking features for home and business gateway products on RDK-B. You will work closely with chipset vendors, cross-functional teams, and customer support to deliver robust and scalable solutions." Your Skills And Experience: List: - 3+ years of experience in embedded software development using C (C++ is a plus). - Strong knowledge of RDK-B/OpenWRT/prplOS architecture and broadband gateway technologies. - Hands-on experience with embedded Linux, including kernel-level concepts and system debugging. - Solid understanding of TCP/IP stack, networking protocols (DHCP, DNS, HTTP), and packet flow. - Experience with firewall/iptables, and IPv6 transition technologies. - Familiarity with source control tools (Git/Gerrit) and debugging tools (gdb, valgrind, wireshark, tcpdump). - Strong problem-solving and debugging skills in complex embedded environments. Nice to have: - Experience with Wi-Fi technologies and IEEE 802.11 standards (802.11n/ac/ax). - Knowledge of DOCSIS, MoCA, and other broadband technologies. - Familiarity with TR-069/TR-181, SNMP, and remote management protocols. - Exposure to chipset SDKs (Broadcom, Qualcomm, etc.). - Understanding of security protocols (WPA3, RADIUS, SSL/TLS). Compensation: "The base compensation range for this role in the posted location is: $53,580-$122,400. Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws. The base compensation range listed for this position reflects the minimum and maximum target compensation Capgemini, in good faith, believes it may pay for the role at the time of this posting. This range may be subject to change as permitted by law. The actual compensation offered to any candidate may fall outside of the posted range and will be determined based on multiple factors legally permitted in the applicable jurisdiction. These may include, but are not limited to: Geographic location, Education and qualifications, Certifications and licenses, Relevant experience and skills, Seniority and performance, Market and business consideration, Internal pay equity. It is not typical for candidates to be hired at or near the top of the posted compensation range. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws." Benefits: "Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include: Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave Medical, dental, and vision coverage (or provincial healthcare coordination in Canada) Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada) Life and disability insurance Employee assistance programs Other benefits as provided by local policy and eligibility" We should keep that as a paragraph or maybe as a list? The rule: use
  • for any list of duties/requirements/benefits. Benefits is a list; we could convert to
    • . However the benefits description includes sentences with commas; we could split each benefit item. But the instruction: "use
      • for any list of duties/requirements/benefits". So we should make a
        for benefits. However the benefits text includes a lead sentence: "Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include:" then list. We could keep the lead sentence as a

        then

        • for each item. Similarly for skills and experience we should use
          • . The "Nice to have" could be part of same list or separate? Could be separate
            with heading? But we can just include all items in one list, maybe separate nice-to-have as a sublist? Simpler: keep all items in one
            and maybe denote nice-to-have in parentheses? But we must preserve all substantive information; we can keep the nice-to-have as separate items but we could add a note "(Nice to have)" before each. However the original text separates them; we could keep two sections: "Requirements" and "Nice-to-have". But we only have Skills heading; we could split into two subheadings? Not allowed to create extra headings beyond those? We could still use

            for section headings only; we could have

            Skills

            then

            Required:

            ... then

            Nice to have:

            ... That's acceptable as we are not adding new section headings, just paragraphs. Similarly for benefits we can have a

            intro then

            . Now we must not include boilerplate like "Capgemini provides compensation range information..." etc. That is substantive? It's part of compensation description; we should keep it as it's part of the posting. It's not boilerplate; it's explanatory. So keep. Now produce HTML fragment. Structure:

            About the role

            We are looking for an experienced Embedded Software Developer for RDK-B with strong expertise in broadband gateway technologies. In this role, you will design, develop, and integrate advanced networking features for home and business gateway products on RDK-B. You will work closely with chipset vendors, cross-functional teams, and customer support to deliver robust and scalable solutions.

            Skills

            Required:

            • 3+ years of experience in embedded software development using C (C++ is a plus).
            • Strong knowledge of RDK-B/OpenWRT/prplOS architecture and broadband gateway technologies.
            • Hands-on experience with embedded Linux, including kernel-level concepts and system debugging.
            • Solid understanding of TCP/IP stack, networking protocols (DHCP, DNS, HTTP), and packet flow.
            • Experience with firewall/iptables, and IPv6 transition technologies.
            • Familiarity with source control tools (Git/Gerrit) and debugging tools (gdb, valgrind, wireshark, tcpdump).
            • Strong problem-solving and debugging skills in complex embedded environments.

            Nice to have:

            • Experience with Wi-Fi technologies and IEEE 802.11 standards (802.11n/ac/ax).
            • Knowledge of DOCSIS, MoCA, and other broadband technologies.
            • Familiarity with TR-069/TR-181, SNMP, and remote management protocols.
            • Exposure to chipset SDKs (Broadcom, Qualcomm, etc.).
            • Understanding of security protocols (WPA3, RADIUS, SSL/TLS).

            Pay

            The base compensation range for this role in the posted location is: $53,580-$122,400. Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws. The base compensation range listed for this position reflects the minimum and maximum target compensation Capgemini, in good faith, believes it may pay for the role at the time of this posting. This range may be subject to change as permitted by law. The actual compensation offered to any candidate may fall outside of the posted range and will be determined based on multiple factors legally permitted in the applicable jurisdiction. These may include, but are not limited to: Geographic location, Education and qualifications, Certifications and licenses, Relevant experience and skills, Seniority and performance, Market and business consideration, Internal pay equity. It is not typical for candidates to be hired at or near the top of the posted compensation range. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws.

            Benefits

            Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and