Software Engineer (Staff Level)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove EEO etc. Also remove contact info for disabilities? That's maybe application instruction; we should remove application instructions. Also remove "Individuals with disabilities who need assistance..." etc. Also remove "For more information, please visit us at https://oceus.io" maybe not needed but it's not boilerplate? It's a link; could keep? It's not a section; but we can keep as prose maybe. However we need to preserve all substantive information; that link is not essential but it's info about company; we could keep in About Us paragraph. We need to parse the posting. Let's extract sections: - About Us: "Oceus Networks’ mission is to enable our customers to securely communicate anywhere at any time. Our team of telecommunications experts works to solve the unique communications and data challenges in a wide range of commercial private networks, combat tactical, austere, and emergency response situations. We develop, integrate, and customize technology for delivering access to fast, reliable broadband connectivity in mission-critical operations." - Security Clearance Requirement: "Current clearance or ability obtain a secret clearance" - Location: "Local to The Colony, TX to support on-site work" - Travel: "Expected 5-10%" - Job Type: "Full Time offering competitive salary and eligibility for company benefits" - Then description: "Oceus is hiring a Software Engineer to join our team at the Staff Level. Our Software Engineers operate and maintain end-to-end solutions, systems, and products for our customers. The team investigates and resolves product and solution problems in conjunction with other engineering and technical personnel. Candidates load software, configure, integrate, verify, and troubleshoot solutions in a lab environment or customer site using Oceus' products, 3rd party products, and/or customized packages." - Responsibilities include (but are not limited to): list bullet points. - Position Requirements: list bullet points. - Preferred Qualifications: "Current U.S. Government Security Clearance is preferred" - Techno-Functional Competency Requirements: list bullet points. - Preferred Technical Skills: "Working knowledge of wireless technologies such as LTE and GSM is a plus." - Then later: "This position offers a full-time salary and eligibility to participate in the company’s benefits program. Oceus offers competitive compensation and benefits to all employees. Salary ranges are advertised based on good faith estimates at the time of posting and indicating pay that Oceus anticipates for successful applicants. The estimated salary range displayed in this posting is dependent upon position requirements, individual qualifications, education, experience, location, and other job-related factors. Our recruiting team will review candidates’ related experience and desired salary targets during the evaluation process. All qualified candidates will be considered." - Then EEO etc which we must remove. We need to decide which sections to include. We have content for: - About the role: Could be the description of role (the paragraph after "Oceus is hiring..."). - Responsibilities: the bullet list. - Requirements: the Position Requirements bullet list (U.S. Citizenship, secret clearance, BS degree, driver's license, passport). Also maybe Security Clearance Requirement could be part of Requirements. - Qualifications: Preferred Qualifications (Current US Gov Security Clearance preferred) maybe also Preferred Technical Skills. - Skills: Techno-Functional Competency Requirements (list). Could be considered Skills. - Benefits: mention of full-time salary and eligibility to participate in company's benefits program, competitive compensation and benefits. That's substantive. - Pay: The posting mentions salary ranges are advertised based on good faith estimates, but does not give actual numbers. It says "estimated salary range displayed in this posting is dependent upon..." but no actual range given. Since we should not include Pay section unless posting actually states them (specific numbers or range). It does not give numbers, just says they are advertised based on estimates. That's not a specific figure. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay section. - Schedule: Not mentioned besides full-time. Could infer schedule but not given. So no Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. So headings are just the section names. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given (maybe minor wording changes? Should preserve). We must not drop any bullet. Let's extract bullet points precisely. Responsibilities include (but are not limited to): - Work as part of a collaborative team designing and developing complex software components and systems - Work closely with product management, QA, security, and infrastructure teams to ensure work product meets business goals and customer needs - Support challenging software and integration issues and work with cross-functional teams to drive efficient resolution - Ensure established best practices are met to meet scalability, performance, and security requirements - Participate in team solution planning activities such as design discussions, requirements refinement, technical scoping, prototype development, risk identification, and collaborative problem solving - Maintain a commitment to continuous learning to stay abreast of emerging tools, technologies, frameworks and methodologies - Other duties, as assigned Position Requirements: - U.S. Citizenship - Current secret security clearance (or ability to obtain a clearance) - Bachelor of Science degree in Computer Science/Telecommunications or related field - Current state-issued driver's license - Current U.S. passport Preferred Qualifications: - Current U.S. Government Security Clearance is preferred Techno-Functional Competency Requirements: - 2-4 years of related software engineering experience with telecommunications and systems integration including: - Experience developing and optimizing production grade applications using modern programming languages such as Go, Rust, Java, C++, or Python - Understanding of software architecture and distributed systems design to support implementation of complex subsystems - Understanding of cloud native concepts, microservices, container orchestration, messaging systems, and CI/CD pipelines - Demonstrated problem-solving capability, including diagnosing multi layered issues across code, infrastructure, networking, and security boundaries - Knowledge of secure system design principles, threat modeling, and compliance-oriented engineering approaches - Ability to work independently, demonstrating initiative and problem-solving skills. - Excellent written and verbal English communication skills, with the ability to convey complex technical information clearly - Ability to work under pressure, meet deadlines, and deliver with high quality - Ability to solve problems and work with minimum supervision - Ability to learn quickly and work in a team environment Preferred Technical Skills: - Working knowledge of wireless technologies such as LTE and GSM is a plus. Benefits: The posting says: "This position offers a full-time salary and eligibility to participate in the company’s benefits program. Oceus offers competitive compensation and benefits to all employees." Also earlier: "Job Type: Full Time offering competitive salary and eligibility for company benefits". So we can combine. We need to put Benefits as a

  • list? It's prose; could be

    . The rule: Use

    • for any list of duties/requirements/benefits, and

      for prose. Benefits is not a list but we could make a

      . However if we want to list benefits items, we don't have specific items. So use

      . Now About the role: we need prose describing role. Could combine the initial About Us paragraph and the description of Software Engineer role. Let's craft a paragraph that includes all substantive info from those parts without omitting. About Us paragraph: "Oceus Networks’ mission is to enable our customers to securely communicate anywhere at any time. Our team of telecommunications experts works to solve the unique communications and data challenges in a wide range of commercial private networks, combat tactical, austere, and emergency response situations. We develop, integrate, and customize technology for delivering access to fast, reliable broadband connectivity in mission-critical operations." Then the role description: "Oceus is hiring a Software Engineer to join our team at the Staff Level. Our Software Engineers operate and maintain end-to-end solutions, systems, and products for our customers. The team investigates and resolves product and solution problems in conjunction with other engineering and technical personnel. Candidates load software, configure, integrate, verify, and troubleshoot solutions in a lab environment or customer site using Oceus' products, 3rd party products, and/or customized packages." We could combine into one

      or two

      . Probably one

      is fine. We also have location, travel, job type info. Should we include those somewhere? They are substantive. Where to put? Could be part of About the role or maybe a separate section like "Job Details". But we only have allowed headings list; we could add a section like "Job Details" but not in allowed list. The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings when appropriate. It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings; we can embed location/travel/job type into About the role paragraph or maybe into Benefits? Better to include in About the role as prose. Thus About the role paragraph will include mission, role description, location, travel, job type. Let's craft: "Oceus Networks’ mission is to enable our customers to securely communicate anywhere at any time. Our team of telecommunications experts works to solve the unique communications and data challenges in a wide range of commercial private networks, combat tactical, austere, and emergency response situations. We develop, integrate, and customize technology for delivering access to fast, reliable broadband connectivity in mission-critical operations. Oceus is hiring a Software Engineer to join our team at the Staff Level. Our Software Engineers operate and maintain end-to-end solutions, systems, and products for our customers. The team investigates and resolves product and solution problems in conjunction with other engineering and technical personnel. Candidates load software, configure, integrate, verify, and troubleshoot solutions in a lab environment or customer site using Oceus' products, 3rd party products, and/or customized packages. The position is local to The Colony, TX to support on-site work, with expected travel of 5-10%, and is a full-time role offering competitive salary and eligibility for company benefits." That preserves all. Now Responsibilities: list as

      • . Requirements: list as
        • . Should we include security clearance requirement here? Yes. Qualifications: list as
          • . Include Preferred Qualifications (Current US Gov Security Clearance is preferred). Possibly also include Preferred Technical Skills? But that is more skills. We'll put Preferred Technical Skills under Skills. Skills: list as
            • . Include Techno-Functional Competency Requirements (the sub-bullets). Also Preferred Technical Skills. We need to decide how to format nested lists. The Techno-Functional Competency Requirements includes a main bullet "2-4 years of related software engineering experience with telecommunications and systems integration including:" then sub-bullets. We could represent as a
            • containing a
              . That's acceptable. Similarly, Preferred Technical Skills is a simple bullet. Thus Skills section will have a
              with li items: one for the 2-4 years experience with sublist, then each of the other bullet points (ability to work independently, etc.), then a li for Preferred Technical Skills. We must preserve all bullet points exactly. Let's extract each bullet from Tech