Software Engineer (Mid Level)

We need to output HTML fragment with sections: About the role? Actually we have "About Us" but we need to use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. Let's parse. Content: - About Us: mission statement, description. Could map to "About the role"? Actually "About Us" is about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for description of role? But we have "Position Description". That could be under "About the role". We'll include that. - Duties and Responsibilities: list bullet points. - Qualifications and Requirements: includes many bullet points (citizenship, clearance, degree, experience, etc). Also "Preferred Qualifications": bullet points. - Skills: maybe we can extract from qualifications: knowledge of languages etc. Could put under Skills. - Benefits: 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." No specific benefits listed. So we should NOT create Benefits section because no specific content. Similarly Pay: they mention salary range but not specific numbers; they say "estimated salary range displayed ... dependent upon ...". That's vague; we should not create Pay section unless posting actually states them. It does not give actual numbers, just says competitive compensation. So we should not include Pay. - Schedule: not mentioned; full-time, on-site. Could infer schedule but not explicit. Probably not include Schedule. Thus sections: About the role (position description), Responsibilities, Requirements (maybe combine qualifications and requirements?), Qualifications (maybe separate?), Skills (maybe extract). But we must avoid thin sections. Let's think: The posting has "Qualifications and Requirements:" with many bullet points. Could treat that as Requirements. Then "Preferred Qualifications:" could be under Qualifications or Skills. Could combine. Better: Use sections: About the role (position description), Responsibilities, Requirements (includes citizenship, clearance, degree, experience, etc), Skills (technical skills: languages, databases, web server, etc). We'll avoid duplication. We need to preserve all substantive information. So we must include all bullet points from Qualifications and Requirements and Preferred Qualifications somewhere. Let's extract bullet points from Qualifications and Requirements: - U.S. citizenship - Current U.S. government security clearance or eligibility to obtain a clearance - B.S. degree required - 2-4 years of experience in software development including: - Experience with relational databases designing data tables, creating and executing SQL programmatically, and coding for long term database performance - Excellent knowledge of Web server application development utilizing HTML - Experience with more of the following server-side implementation languages: PHP/node JS/Go - Excellent knowledge of the following C/C++ and Java for target Linux platforms - Excellent network programming with client/server experience - Good knowledge of VMs, containers and virtual environments - Good knowledge of Client/Server architectures - Good understanding of IP networks - Experience practicing effective time management - Ability to take initiative - Ability to work under pressure, meet deadlines, and deliver with high quality - Ability to problem solve and work with minimum supervision - Ability to learn fast and work in a team environment - Effective written and verbal English communication skills are a must - Availability to work on-site at The Colony office - Availability to travel estimated up to 10% Preferred Qualifications: - Experience developing software for telecommunications a plus - Good knowledge of wireless technologies and related protocols (NR, LTE, GSM) is a plus - Understanding of peer-to-peer encryption is a plus - Understanding Information Assurance requirements on products is a plus Also note: Individuals with disabilities... contact info (we should drop as boilerplate? It's contact for accommodation; maybe keep? It's not EEO boilerplate but it's accommodation contact. Might be considered part of application instructions? It's not application instructions but contact for assistance. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is accommodation contact; not exactly EEO but could be considered part of application instructions. Safer to drop. Also "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." That's benefits but vague; we should not create Benefits section. Now Duties and Responsibilities bullet points: - Work with the R&D Project Manager to plan and report status of projects - Work with the R&D team to design, implement, and function test the products - Work with the R&D teams on product releases, features, requirements, and test tools - Interact with Managers and Project Managers and others, as required, to meet project schedules - Communicate effectively with technical and non-technical personnel - Be proactive in keeping skillsets up to date Now About the role: Position Description paragraph: "Oceus is hiring a Software Engineer with mid-level experience to join their staff. The team is focused on R&D software development as part of our product development team. We specialize in 5G NR and 4G LTE products and solutions. This is an exciting time to be part of Oceus working on 5G and various hardware and software configurations to support our unique customer requirements. This position will report to the R&D Director." We'll put that under About the role. Now we need to decide headings: About the role, Responsibilities, Requirements, Skills. Possibly also Qualifications? But we have Requirements covering qualifications; Skills could be technical skills extracted. However we might double-count. Could combine Requirements and Skills into one section? But instruction: prefer few substantive sections over many thin ones. We have enough content for each. Let's allocate: - About the role: paragraph. - Responsibilities: ul of duties. - Requirements: ul of mandatory qualifications (citizenship, clearance, degree, experience, etc). This includes many bullet points; we can keep them. - Skills: ul of technical skills (languages, databases, web server, networking, VMs, etc) plus maybe preferred qualifications? But preferred qualifications are extra; could be under Skills as "Preferred" but we could also include them under Skills as bullet points with note "(preferred)". However we must not invent placeholder text. We can include them as bullet points without labeling preferred; just list them. That preserves info. Thus Skills section will include: - Experience with relational databases designing data tables, creating and executing SQL programmatically, and coding for long term database performance - Excellent knowledge of Web server application development utilizing HTML - Experience with more of the following server-side implementation languages: PHP/node JS/Go - Excellent knowledge of the following C/C++ and Java for target Linux platforms - Excellent network programming with client/server experience - Good knowledge of VMs, containers and virtual environments - Good knowledge of Client/Server architectures - Good understanding of IP networks - Experience developing software for telecommunications - Good knowledge of wireless technologies and related protocols (NR, LTE, GSM) - Understanding of peer-to-peer encryption - Understanding Information Assurance requirements on products But note some of these overlap with Requirements (like databases, web server, languages, etc). To avoid duplication, we could separate: Requirements includes citizenship, clearance, degree, years experience, time management, initiative, etc. Skills includes technical abilities. However the qualifications list includes both technical and soft skills. We'll split accordingly. Let's list Requirements (mandatory): - U.S. citizenship - Current U.S. government security clearance or eligibility to obtain a clearance - B.S. degree required - 2-4 years of experience in software development - Experience practicing effective time management - Ability to take initiative - Ability to work under pressure, meet deadlines, and deliver with high quality - Ability to problem solve and work with minimum supervision - Ability to learn fast and work in a team environment - Effective written and verbal English communication skills are a must - Availability to work on-site at The Colony office - Availability to travel estimated up to 10% Note: The "2-4 years of experience in software development including:" is followed by sub-bullets that are technical; we will move those to Skills. Thus Requirements list as above. Skills list: - Experience with relational databases designing data tables, creating and executing SQL programmatically, and coding for long term database performance - Excellent knowledge of Web server application development utilizing HTML - Experience with more of the following server-side implementation languages: PHP/node JS/Go - Excellent knowledge of the following C/C++ and Java for target Linux platforms - Excellent network programming with client/server experience - Good knowledge of VMs, containers and virtual environments - Good knowledge of Client/Server architectures - Good understanding of IP networks - Experience developing software for telecommunications - Good knowledge of wireless technologies and related protocols (NR, LTE, GSM) - Understanding of peer-to-peer encryption - Understanding Information Assurance requirements on products Now Responsibilities list as earlier. Now About the role paragraph. Now ensure we don't include any boilerplate. Also we should not include headings for empty sections. Now produce HTML fragment:

About the role

Oceus is hiring a Software Engineer with mid-level experience to join their staff. The team is focused on R&D software development as part of our product development team. We specialize in 5G NR and 4G LTE products and solutions. This is an exciting time to be part of Oceus working on 5G and various hardware and software configurations to support our unique customer requirements. This position will report to the R&D Director.

Responsibilities

• Work with the R&D Project Manager to plan and report status of projects
• Work with the R&D team to design, implement, and function test the products
• Work with the R&D teams on product releases, features, requirements, and test tools
• Interact with Managers and Project Managers and others, as required, to meet project schedules
• Communicate effectively with technical and non-technical personnel
• Be proactive in keeping skillsets up to date

Requirements

• U.S. citizenship
• Current U.S. government security clearance or eligibility to obtain a clearance
• B.S. degree required
• 2-4 years of experience in software development
• Experience practicing effective time management
• Ability to take initiative
• Ability to work under pressure, meet deadlines, and deliver with high quality
• Ability to problem solve and work with minimum supervision
• Ability to learn fast and work in a team environment
• Effective written and verbal English communication skills are a must
• Availability to work on-site at The Colony office
• Availability to travel estimated up to 10%

Skills

• Experience with relational databases designing data tables, creating and executing SQL programmatically, and coding for long term database performance
• Excellent knowledge of Web server application development utilizing HTML
• Experience with more of the following server-side implementation languages: PHP/node JS/Go
• Excellent knowledge of the following C/C++ and Java for target Linux platforms
• Excellent network programming with client/server experience
• Good knowledge of VMs, containers and virtual environments
• Good knowledge of Client/Server architectures
• Good understanding of IP networks
• Experience developing software for telecommunications
• Good knowledge of wireless technologies and related protocols (NR, LTE, GSM)
• Understanding of peer-to-peer encryption
• Understanding Information Assurance requirements on products