Test Engineer (Mid Level)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to extract substantive content: About Us, Position Overview, Security Clearance Requirement, Location, Travel, Job Type, etc. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can decide which sections to include based on content.
We have:
- About Us: description of mission, team, etc. Could map to "About the role"? Actually "About Us" is about company. Could be "About the role"? But we have "Position Overview". Could use "About the role" for position overview. Or we could have separate sections: "About Us" not in list but we can still use
About Us? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? Likely we should stick to those headings. So we need to map content to those headings.
We have:
- Position Overview: description of test engineer role. Could go under "About the role".
- Responsibilities: there are bullet lists for Staff Level and Senior Level responsibilities. We can combine? The posting includes responsibilities for both levels. We could have a Responsibilities section with combined list (maybe separate subheadings? but we should not create extra headings beyond allowed? Could still have Responsibilities and then - items.
- Requirements: includes Universal Position Requirements: U.S. Citizenship, Current secret security clearance (or ability to obtain), Bachelor of Science degree in Computer Science/Telecommunications or related field. Also Security Clearance Requirement: Current clearance or ability obtain a secret clearance. Also Location: Local to The Colony, TX to support on-site work. Travel: Up to 50%. Job Type: Full Time offering competitive salary and eligibility for company benefits. Also Preferred Qualifications: Current U.S. Government Security Clearance is preferred. Also Techno-Functional Competency Requirements (list). Also Core Technical Knowledge Requirements (list). Also Preferred Technical Skills (list). Also Level Breakdown & Tiered Qualifications (Staff Level and Senior Level) with experience, skill focus, etc. Those could be under Requirements or Qualifications.
- Qualifications: could include Preferred Qualifications, Level Breakdown, etc.
- Skills: could include Techno-Functional Competency Requirements, Core Technical Knowledge Requirements, Preferred Technical Skills.
- Benefits: The posting mentions "eligibility for company benefits", "competitive salary and eligibility for company benefits", "Our Test Engineers support...". 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." Also "Salary ranges are advertised based on good faith estimates...". So we have some benefits info but not specific details. The instruction says never create Benefits section unless posting actually states them. It does state eligibility for company benefits, competitive compensation and benefits. That's enough to include a Benefits section with generic statement? But we must not include filler like "commensurate with experience". The posting says "eligibility to participate in the company's benefits program" and "competitive compensation and benefits". That's substantive enough? Might be considered vague but it's stated. We'll include a Benefits section with a
summarizing that.
- Pay: The posting mentions "competitive salary", "Salary ranges are advertised based on good faith estimates...". It does not give actual numbers. It says "estimated salary range displayed in this posting is dependent upon...". This is somewhat vague but it's stating that salary range is displayed (though not given). The instruction says never create Pay section unless posting actually states them. It does mention salary ranges are advertised based on good faith estimates, but does not give actual numbers. Might be considered placeholder? It says "The estimated salary range displayed in this posting is dependent upon position requirements, individual qualifications, education, experience, location, and other job-related factors." This is not a specific number but indicates that a range is displayed (though we don't see it). Since we don't have actual numbers, maybe we should not create Pay section to avoid filler. Safer to omit Pay.
- Schedule: Not mentioned besides full-time. Could infer schedule but not explicit. So omit Schedule.
Thus we will have sections: About the role (Position Overview), Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't repeat job title as heading. We'll not include "Test Engineer (Mid Level)" as heading.
We need to preserve all substantive information. Must not invent or summarize away detail. We need to include details like location, travel, security clearance, citizenship, degree, etc.
We need to format lists with
- . For prose, use
.
We need to avoid boilerplate: EEO, diversity statement, application instructions, contact info for disabilities, legal statements, etc. Remove those.
We need to remove duplicated lines.
Let's extract content:
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. For more information, please visit us at https://oceus.io"
We could put this under About the role? Or maybe we could have a separate About Us section but not in allowed headings. Since we must use headings from list, we could put this under About the role (makes sense as overview of company and role). But the Position Overview already describes role. We could combine both.
Better: Use About the role for Position Overview (role description). And maybe include About Us as a separate
before headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. ...). Likely they expect only those headings. To be safe, we will use only those headings and embed About Us content within About the role or maybe as a preceding
without heading? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other headings, but to follow the pattern we should use those. We'll include About the role heading and put both company mission and position overview inside.
Now Responsibilities: We have responsibilities for Staff Level and Senior Level. We could combine them into a single list, but we might lose distinction. However we can keep both as separate maybe with a note? But we cannot add extra headings for Staff vs Senior. We could just list all responsibilities as items, preserving both sets. That would be substantive.
Let's extract responsibilities:
Staff Level responsibilities:
- Execute testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure performance, reliability, and functional accuracy.
- Configure, integrate, and verify solution components in lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Support solution security and compliance activities by implementing STIG and RMF requirements under guidance from senior engineers.
- Work directly with customers and internal teams to gather technical details, communicate findings, and ensure issues are clearly understood by both technical and non-technical stakeholders.
- Contribute to knowledge sharing and team development by documenting test procedures, results, and best practices.
- Collaborate with project managers, engineering teams, vendors, and support personnel to meet delivery timelines and ensure high-quality technical outcomes.
- Partner with Oceus Customer Support to investigate escalated issues, reproduce defects, and help drive accurate, timely resolutions.
Senior Level responsibilities:
- Lead advanced testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure high performance, reliability, and functional correctness.
- Independently configure, integrate, and verify complex solution components in both lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Drive security and compliance efforts by implementing STIG and RMF requirements, providing technical guidance to mid-level engineers, and ensuring test environments follow secure configuration practices.
- Serve as a senior technical resource for customers and internal teams, clearly communicating test findings, system behaviors, and root cause analyses to technical and non-technical stakeholders.
- Develop and improve test procedures, validation frameworks, and best practice documentation to enhance repeatability, consistency, and engineering efficiency across the team.
- Collaborate proactively with project managers, engineering teams, vendors, and cross functional partners to ensure testing milestones support delivery schedules and solution quality requirements.
- Work closely with Oceus Customer Support to investigate escalated issues, reproduce complex defects, and deliver accurate, timely resolutions while improving overall system testability.
We'll combine these into a single list.
Now Requirements: Universal 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.
Also Security Clearance Requirement: Current clearance or ability obtain a secret clearance (duplicate). Location: Local to The Colony, TX to support on-site work. Travel: Up to 50%. Job Type: Full Time offering competitive salary and eligibility for company benefits.
Also Preferred Qualifications: Current U.S. Government Security Clearance is preferred.
We'll include these in Requirements section as list items.
Now Qualifications: Could include Level Breakdown & Tiered Qualifications (Staff Level and Senior Level) with experience, skill focus, etc. Also Preferred Qualifications (already maybe in Requirements). We'll treat Qualifications as the experience/skill focus details.
We'll extract Staff Level qualifications:
- Experience: 2-4 years of engineering experience related to computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Solid IP networking foundation; hands on experience with Cisco routing and switching at or near the CCNA skill level.
- Working knowledge of STIG, RMF, or secure system implementation principles, with willingness to grow expertise.
- Strong written and verbal communication skills, especially for documenting test results and explaining technical details.
- Ability to work effectively across engineering teams, manage multiple technical inputs, and support collaborative problem solving.
- Strong analytical and diagnostic skills with the ability to isolate root causes in complex systems.
- Broad understanding of telecommunications concepts, protocols, and integrated technologies.
Senior Level qualifications:
- Experience: 5–7 years of engineering experience in computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Strong IP networking background with hands on experience in Cisco routing and switching; CCNA level capability required, CCNP-level skills preferred for complex troubleshooting scenarios.
- Solid understanding and practical experience with STIG, RMF, or secure system implementation practices, with ability to independently apply and validate compliance requirements.
- Excellent written and verbal communication skills for documenting test results, authoring technical procedures,
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to extract substantive content: About Us, Position Overview, Security Clearance Requirement, Location, Travel, Job Type, etc. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide which sections to include based on content. We have: - About Us: description of mission, team, etc. Could map to "About the role"? Actually "About Us" is about company. Could be "About the role"? But we have "Position Overview". Could use "About the role" for position overview. Or we could have separate sections: "About Us" not in list but we can still use
About Us? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? Likely we should stick to those headings. So we need to map content to those headings.
We have:
- Position Overview: description of test engineer role. Could go under "About the role".
- Responsibilities: there are bullet lists for Staff Level and Senior Level responsibilities. We can combine? The posting includes responsibilities for both levels. We could have a Responsibilities section with combined list (maybe separate subheadings? but we should not create extra headings beyond allowed? Could still have Responsibilities and then - items.
- Requirements: includes Universal Position Requirements: U.S. Citizenship, Current secret security clearance (or ability to obtain), Bachelor of Science degree in Computer Science/Telecommunications or related field. Also Security Clearance Requirement: Current clearance or ability obtain a secret clearance. Also Location: Local to The Colony, TX to support on-site work. Travel: Up to 50%. Job Type: Full Time offering competitive salary and eligibility for company benefits. Also Preferred Qualifications: Current U.S. Government Security Clearance is preferred. Also Techno-Functional Competency Requirements (list). Also Core Technical Knowledge Requirements (list). Also Preferred Technical Skills (list). Also Level Breakdown & Tiered Qualifications (Staff Level and Senior Level) with experience, skill focus, etc. Those could be under Requirements or Qualifications.
- Qualifications: could include Preferred Qualifications, Level Breakdown, etc.
- Skills: could include Techno-Functional Competency Requirements, Core Technical Knowledge Requirements, Preferred Technical Skills.
- Benefits: The posting mentions "eligibility for company benefits", "competitive salary and eligibility for company benefits", "Our Test Engineers support...". 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." Also "Salary ranges are advertised based on good faith estimates...". So we have some benefits info but not specific details. The instruction says never create Benefits section unless posting actually states them. It does state eligibility for company benefits, competitive compensation and benefits. That's enough to include a Benefits section with generic statement? But we must not include filler like "commensurate with experience". The posting says "eligibility to participate in the company's benefits program" and "competitive compensation and benefits". That's substantive enough? Might be considered vague but it's stated. We'll include a Benefits section with a
summarizing that.
- Pay: The posting mentions "competitive salary", "Salary ranges are advertised based on good faith estimates...". It does not give actual numbers. It says "estimated salary range displayed in this posting is dependent upon...". This is somewhat vague but it's stating that salary range is displayed (though not given). The instruction says never create Pay section unless posting actually states them. It does mention salary ranges are advertised based on good faith estimates, but does not give actual numbers. Might be considered placeholder? It says "The estimated salary range displayed in this posting is dependent upon position requirements, individual qualifications, education, experience, location, and other job-related factors." This is not a specific number but indicates that a range is displayed (though we don't see it). Since we don't have actual numbers, maybe we should not create Pay section to avoid filler. Safer to omit Pay.
- Schedule: Not mentioned besides full-time. Could infer schedule but not explicit. So omit Schedule.
Thus we will have sections: About the role (Position Overview), Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't repeat job title as heading. We'll not include "Test Engineer (Mid Level)" as heading.
We need to preserve all substantive information. Must not invent or summarize away detail. We need to include details like location, travel, security clearance, citizenship, degree, etc.
We need to format lists with
- . For prose, use
.
We need to avoid boilerplate: EEO, diversity statement, application instructions, contact info for disabilities, legal statements, etc. Remove those.
We need to remove duplicated lines.
Let's extract content:
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. For more information, please visit us at https://oceus.io"
We could put this under About the role? Or maybe we could have a separate About Us section but not in allowed headings. Since we must use headings from list, we could put this under About the role (makes sense as overview of company and role). But the Position Overview already describes role. We could combine both.
Better: Use About the role for Position Overview (role description). And maybe include About Us as a separate
before headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. ...). Likely they expect only those headings. To be safe, we will use only those headings and embed About Us content within About the role or maybe as a preceding
without heading? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other headings, but to follow the pattern we should use those. We'll include About the role heading and put both company mission and position overview inside.
Now Responsibilities: We have responsibilities for Staff Level and Senior Level. We could combine them into a single list, but we might lose distinction. However we can keep both as separate maybe with a note? But we cannot add extra headings for Staff vs Senior. We could just list all responsibilities as items, preserving both sets. That would be substantive.
Let's extract responsibilities:
Staff Level responsibilities:
- Execute testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure performance, reliability, and functional accuracy.
- Configure, integrate, and verify solution components in lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Support solution security and compliance activities by implementing STIG and RMF requirements under guidance from senior engineers.
- Work directly with customers and internal teams to gather technical details, communicate findings, and ensure issues are clearly understood by both technical and non-technical stakeholders.
- Contribute to knowledge sharing and team development by documenting test procedures, results, and best practices.
- Collaborate with project managers, engineering teams, vendors, and support personnel to meet delivery timelines and ensure high-quality technical outcomes.
- Partner with Oceus Customer Support to investigate escalated issues, reproduce defects, and help drive accurate, timely resolutions.
Senior Level responsibilities:
- Lead advanced testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure high performance, reliability, and functional correctness.
- Independently configure, integrate, and verify complex solution components in both lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Drive security and compliance efforts by implementing STIG and RMF requirements, providing technical guidance to mid-level engineers, and ensuring test environments follow secure configuration practices.
- Serve as a senior technical resource for customers and internal teams, clearly communicating test findings, system behaviors, and root cause analyses to technical and non-technical stakeholders.
- Develop and improve test procedures, validation frameworks, and best practice documentation to enhance repeatability, consistency, and engineering efficiency across the team.
- Collaborate proactively with project managers, engineering teams, vendors, and cross functional partners to ensure testing milestones support delivery schedules and solution quality requirements.
- Work closely with Oceus Customer Support to investigate escalated issues, reproduce complex defects, and deliver accurate, timely resolutions while improving overall system testability.
We'll combine these into a single list.
Now Requirements: Universal 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.
Also Security Clearance Requirement: Current clearance or ability obtain a secret clearance (duplicate). Location: Local to The Colony, TX to support on-site work. Travel: Up to 50%. Job Type: Full Time offering competitive salary and eligibility for company benefits.
Also Preferred Qualifications: Current U.S. Government Security Clearance is preferred.
We'll include these in Requirements section as list items.
Now Qualifications: Could include Level Breakdown & Tiered Qualifications (Staff Level and Senior Level) with experience, skill focus, etc. Also Preferred Qualifications (already maybe in Requirements). We'll treat Qualifications as the experience/skill focus details.
We'll extract Staff Level qualifications:
- Experience: 2-4 years of engineering experience related to computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Solid IP networking foundation; hands on experience with Cisco routing and switching at or near the CCNA skill level.
- Working knowledge of STIG, RMF, or secure system implementation principles, with willingness to grow expertise.
- Strong written and verbal communication skills, especially for documenting test results and explaining technical details.
- Ability to work effectively across engineering teams, manage multiple technical inputs, and support collaborative problem solving.
- Strong analytical and diagnostic skills with the ability to isolate root causes in complex systems.
- Broad understanding of telecommunications concepts, protocols, and integrated technologies.
Senior Level qualifications:
- Experience: 5–7 years of engineering experience in computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Strong IP networking background with hands on experience in Cisco routing and switching; CCNA level capability required, CCNP-level skills preferred for complex troubleshooting scenarios.
- Solid understanding and practical experience with STIG, RMF, or secure system implementation practices, with ability to independently apply and validate compliance requirements.
- Excellent written and verbal communication skills for documenting test results, authoring technical procedures,
Responsibilities and then - items.
- Requirements: includes Universal Position Requirements: U.S. Citizenship, Current secret security clearance (or ability to obtain), Bachelor of Science degree in Computer Science/Telecommunications or related field. Also Security Clearance Requirement: Current clearance or ability obtain a secret clearance. Also Location: Local to The Colony, TX to support on-site work. Travel: Up to 50%. Job Type: Full Time offering competitive salary and eligibility for company benefits. Also Preferred Qualifications: Current U.S. Government Security Clearance is preferred. Also Techno-Functional Competency Requirements (list). Also Core Technical Knowledge Requirements (list). Also Preferred Technical Skills (list). Also Level Breakdown & Tiered Qualifications (Staff Level and Senior Level) with experience, skill focus, etc. Those could be under Requirements or Qualifications.
- Qualifications: could include Preferred Qualifications, Level Breakdown, etc.
- Skills: could include Techno-Functional Competency Requirements, Core Technical Knowledge Requirements, Preferred Technical Skills.
- Benefits: The posting mentions "eligibility for company benefits", "competitive salary and eligibility for company benefits", "Our Test Engineers support...". 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." Also "Salary ranges are advertised based on good faith estimates...". So we have some benefits info but not specific details. The instruction says never create Benefits section unless posting actually states them. It does state eligibility for company benefits, competitive compensation and benefits. That's enough to include a Benefits section with generic statement? But we must not include filler like "commensurate with experience". The posting says "eligibility to participate in the company's benefits program" and "competitive compensation and benefits". That's substantive enough? Might be considered vague but it's stated. We'll include a Benefits section with a
summarizing that.
- Pay: The posting mentions "competitive salary", "Salary ranges are advertised based on good faith estimates...". It does not give actual numbers. It says "estimated salary range displayed in this posting is dependent upon...". This is somewhat vague but it's stating that salary range is displayed (though not given). The instruction says never create Pay section unless posting actually states them. It does mention salary ranges are advertised based on good faith estimates, but does not give actual numbers. Might be considered placeholder? It says "The estimated salary range displayed in this posting is dependent upon position requirements, individual qualifications, education, experience, location, and other job-related factors." This is not a specific number but indicates that a range is displayed (though we don't see it). Since we don't have actual numbers, maybe we should not create Pay section to avoid filler. Safer to omit Pay.
- Schedule: Not mentioned besides full-time. Could infer schedule but not explicit. So omit Schedule.
Thus we will have sections: About the role (Position Overview), Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't repeat job title as heading. We'll not include "Test Engineer (Mid Level)" as heading.
We need to preserve all substantive information. Must not invent or summarize away detail. We need to include details like location, travel, security clearance, citizenship, degree, etc.
We need to format lists with
- . For prose, use
.
We need to avoid boilerplate: EEO, diversity statement, application instructions, contact info for disabilities, legal statements, etc. Remove those.
We need to remove duplicated lines.
Let's extract content:
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. For more information, please visit us at https://oceus.io"
We could put this under About the role? Or maybe we could have a separate About Us section but not in allowed headings. Since we must use headings from list, we could put this under About the role (makes sense as overview of company and role). But the Position Overview already describes role. We could combine both.
Better: Use About the role for Position Overview (role description). And maybe include About Us as a separate
before headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. ...). Likely they expect only those headings. To be safe, we will use only those headings and embed About Us content within About the role or maybe as a preceding
without heading? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other headings, but to follow the pattern we should use those. We'll include About the role heading and put both company mission and position overview inside.
Now Responsibilities: We have responsibilities for Staff Level and Senior Level. We could combine them into a single list, but we might lose distinction. However we can keep both as separate maybe with a note? But we cannot add extra headings for Staff vs Senior. We could just list all responsibilities as items, preserving both sets. That would be substantive.
Let's extract responsibilities:
Staff Level responsibilities:
- Execute testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure performance, reliability, and functional accuracy.
- Configure, integrate, and verify solution components in lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Support solution security and compliance activities by implementing STIG and RMF requirements under guidance from senior engineers.
- Work directly with customers and internal teams to gather technical details, communicate findings, and ensure issues are clearly understood by both technical and non-technical stakeholders.
- Contribute to knowledge sharing and team development by documenting test procedures, results, and best practices.
- Collaborate with project managers, engineering teams, vendors, and support personnel to meet delivery timelines and ensure high-quality technical outcomes.
- Partner with Oceus Customer Support to investigate escalated issues, reproduce defects, and help drive accurate, timely resolutions.
Senior Level responsibilities:
- Lead advanced testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure high performance, reliability, and functional correctness.
- Independently configure, integrate, and verify complex solution components in both lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Drive security and compliance efforts by implementing STIG and RMF requirements, providing technical guidance to mid-level engineers, and ensuring test environments follow secure configuration practices.
- Serve as a senior technical resource for customers and internal teams, clearly communicating test findings, system behaviors, and root cause analyses to technical and non-technical stakeholders.
- Develop and improve test procedures, validation frameworks, and best practice documentation to enhance repeatability, consistency, and engineering efficiency across the team.
- Collaborate proactively with project managers, engineering teams, vendors, and cross functional partners to ensure testing milestones support delivery schedules and solution quality requirements.
- Work closely with Oceus Customer Support to investigate escalated issues, reproduce complex defects, and deliver accurate, timely resolutions while improving overall system testability.
We'll combine these into a single list.
Now Requirements: Universal 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.
Also Security Clearance Requirement: Current clearance or ability obtain a secret clearance (duplicate). Location: Local to The Colony, TX to support on-site work. Travel: Up to 50%. Job Type: Full Time offering competitive salary and eligibility for company benefits.
Also Preferred Qualifications: Current U.S. Government Security Clearance is preferred.
We'll include these in Requirements section as list items.
Now Qualifications: Could include Level Breakdown & Tiered Qualifications (Staff Level and Senior Level) with experience, skill focus, etc. Also Preferred Qualifications (already maybe in Requirements). We'll treat Qualifications as the experience/skill focus details.
We'll extract Staff Level qualifications:
- Experience: 2-4 years of engineering experience related to computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Solid IP networking foundation; hands on experience with Cisco routing and switching at or near the CCNA skill level.
- Working knowledge of STIG, RMF, or secure system implementation principles, with willingness to grow expertise.
- Strong written and verbal communication skills, especially for documenting test results and explaining technical details.
- Ability to work effectively across engineering teams, manage multiple technical inputs, and support collaborative problem solving.
- Strong analytical and diagnostic skills with the ability to isolate root causes in complex systems.
- Broad understanding of telecommunications concepts, protocols, and integrated technologies.
Senior Level qualifications:
- Experience: 5–7 years of engineering experience in computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Strong IP networking background with hands on experience in Cisco routing and switching; CCNA level capability required, CCNP-level skills preferred for complex troubleshooting scenarios.
- Solid understanding and practical experience with STIG, RMF, or secure system implementation practices, with ability to independently apply and validate compliance requirements.
- Excellent written and verbal communication skills for documenting test results, authoring technical procedures,
summarizing that. - Pay: The posting mentions "competitive salary", "Salary ranges are advertised based on good faith estimates...". It does not give actual numbers. It says "estimated salary range displayed in this posting is dependent upon...". This is somewhat vague but it's stating that salary range is displayed (though not given). The instruction says never create Pay section unless posting actually states them. It does mention salary ranges are advertised based on good faith estimates, but does not give actual numbers. Might be considered placeholder? It says "The estimated salary range displayed in this posting is dependent upon position requirements, individual qualifications, education, experience, location, and other job-related factors." This is not a specific number but indicates that a range is displayed (though we don't see it). Since we don't have actual numbers, maybe we should not create Pay section to avoid filler. Safer to omit Pay. - Schedule: Not mentioned besides full-time. Could infer schedule but not explicit. So omit Schedule. Thus we will have sections: About the role (Position Overview), Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to ensure we don't repeat job title as heading. We'll not include "Test Engineer (Mid Level)" as heading. We need to preserve all substantive information. Must not invent or summarize away detail. We need to include details like location, travel, security clearance, citizenship, degree, etc. We need to format lists with
- . For prose, use
. We need to avoid boilerplate: EEO, diversity statement, application instructions, contact info for disabilities, legal statements, etc. Remove those. We need to remove duplicated lines. Let's extract content: 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. For more information, please visit us at https://oceus.io" We could put this under About the role? Or maybe we could have a separate About Us section but not in allowed headings. Since we must use headings from list, we could put this under About the role (makes sense as overview of company and role). But the Position Overview already describes role. We could combine both. Better: Use About the role for Position Overview (role description). And maybe include About Us as a separate
before headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use
for section headings (e.g. ...). Likely they expect only those headings. To be safe, we will use only those headings and embed About Us content within About the role or maybe as a preceding
without heading? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot have other headings, but to follow the pattern we should use those. We'll include About the role heading and put both company mission and position overview inside. Now Responsibilities: We have responsibilities for Staff Level and Senior Level. We could combine them into a single list, but we might lose distinction. However we can keep both as separate
- maybe with a note? But we cannot add extra headings for Staff vs Senior. We could just list all responsibilities as items, preserving both sets. That would be substantive.
Let's extract responsibilities:
Staff Level responsibilities:
- Execute testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure performance, reliability, and functional accuracy.
- Configure, integrate, and verify solution components in lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Support solution security and compliance activities by implementing STIG and RMF requirements under guidance from senior engineers.
- Work directly with customers and internal teams to gather technical details, communicate findings, and ensure issues are clearly understood by both technical and non-technical stakeholders.
- Contribute to knowledge sharing and team development by documenting test procedures, results, and best practices.
- Collaborate with project managers, engineering teams, vendors, and support personnel to meet delivery timelines and ensure high-quality technical outcomes.
- Partner with Oceus Customer Support to investigate escalated issues, reproduce defects, and help drive accurate, timely resolutions.
Senior Level responsibilities:
- Lead advanced testing, validation, and troubleshooting activities for end-to-end customer solutions to ensure high performance, reliability, and functional correctness.
- Independently configure, integrate, and verify complex solution components in both lab and onsite environments using Oceus Networks products, third party technologies, and customized packages.
- Drive security and compliance efforts by implementing STIG and RMF requirements, providing technical guidance to mid-level engineers, and ensuring test environments follow secure configuration practices.
- Serve as a senior technical resource for customers and internal teams, clearly communicating test findings, system behaviors, and root cause analyses to technical and non-technical stakeholders.
- Develop and improve test procedures, validation frameworks, and best practice documentation to enhance repeatability, consistency, and engineering efficiency across the team.
- Collaborate proactively with project managers, engineering teams, vendors, and cross functional partners to ensure testing milestones support delivery schedules and solution quality requirements.
- Work closely with Oceus Customer Support to investigate escalated issues, reproduce complex defects, and deliver accurate, timely resolutions while improving overall system testability.
We'll combine these into a single
- list.
Now Requirements: Universal 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.
Also Security Clearance Requirement: Current clearance or ability obtain a secret clearance (duplicate). Location: Local to The Colony, TX to support on-site work. Travel: Up to 50%. Job Type: Full Time offering competitive salary and eligibility for company benefits.
Also Preferred Qualifications: Current U.S. Government Security Clearance is preferred.
We'll include these in Requirements section as list items.
Now Qualifications: Could include Level Breakdown & Tiered Qualifications (Staff Level and Senior Level) with experience, skill focus, etc. Also Preferred Qualifications (already maybe in Requirements). We'll treat Qualifications as the experience/skill focus details.
We'll extract Staff Level qualifications:
- Experience: 2-4 years of engineering experience related to computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Solid IP networking foundation; hands on experience with Cisco routing and switching at or near the CCNA skill level.
- Working knowledge of STIG, RMF, or secure system implementation principles, with willingness to grow expertise.
- Strong written and verbal communication skills, especially for documenting test results and explaining technical details.
- Ability to work effectively across engineering teams, manage multiple technical inputs, and support collaborative problem solving.
- Strong analytical and diagnostic skills with the ability to isolate root causes in complex systems.
- Broad understanding of telecommunications concepts, protocols, and integrated technologies.
Senior Level qualifications:
- Experience: 5–7 years of engineering experience in computer technology, telecommunications, or related systems testing roles.
- Skill Focus: Strong IP networking background with hands on experience in Cisco routing and switching; CCNA level capability required, CCNP-level skills preferred for complex troubleshooting scenarios.
- Solid understanding and practical experience with STIG, RMF, or secure system implementation practices, with ability to independently apply and validate compliance requirements.
- Excellent written and verbal communication skills for documenting test results, authoring technical procedures,