Software Developer I/II
Zekiah Technologies · Dahlgren, VA · Yesterday
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role? The description includes "Description" paragraph. We can treat that as About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
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. 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.
We need to include sections for content we have: Description (maybe About the role), Responsibilities, Requirements, Clearance Requirements, Benefits, About Us (maybe not needed but could be About the role? Actually About Us is separate but could be considered part of description). The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely we should stick to those. However we have sections like Clearance Requirements and About Us. Could we incorporate Clearance Requirements into Requirements? Possibly as a sub-list? But we need to preserve all substantive information. Could add a section "Clearance Requirements" as its own heading, though not in the example list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. But better to keep to those examples if possible. Clearance Requirements could be part of Requirements (maybe as a bullet). About Us could be part of About the role? But we have a description paragraph that already describes the opportunity. The About Us section is separate marketing. Could we omit About Us? It's substantive but maybe not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep About Us content. Could we put it under a heading "About the company" or "About Us"? Not in examples but we can add. However they said prefer a few substantive sections over many thin ones. Could combine About Us into About the role? Might be okay.
Let's decide sections: About the role (includes description paragraph and maybe About Us). Responsibilities (list). Requirements (list includes experience, skills, education, clearance). Benefits (list). Possibly also Qualifications? But Requirements already covers qualifications. We could skip Qualifications.
We need to avoid duplication: The responsibilities list has many items, some duplicated (e.g., "Perform validation and verification testing" appears twice? Actually list includes "Unit and integration testing", "Verification and validation testing", "Peer test application updates", "Perform validation and verification testing" again later. We should preserve all substantive information but we can deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Removing duplicates could be considered summarizing away detail? It's ambiguous. Safer to keep duplicates as they appear? But they said remove duplicated lines (in boilerplate). That refers to boilerplate duplicated lines, not necessarily content duplicates. However the responsibilities list has duplicate "Perform validation and verification testing". That's likely a mistake in the posting. Should we keep both? It's not boilerplate; it's duplicate content. I'd keep one instance to avoid redundancy, but that could be considered summarizing away detail. However the instruction about removing duplicated lines likely refers to boilerplate duplicates like EEO statements. I'd keep both? Might look odd. I'd keep one to avoid unnecessary repetition but still preserve the info. I'd note that it's duplicate but we can keep one.
Let's extract content.
Description paragraph: "We have an opportunity for an enthusiastic Software Developer with a desire to grow while working with a skilled and highly motivated team on leading-edge work. Our team provides IT services for systems engineering and information management systems to multiple major DoD programs. Each team member has opportunities to take on responsibilities according to their experience level and professional growth goals. Our staff mentors one another in their areas of expertise, continuously enhancing the synergistic capabilities of the team."
About Us: "Here at Zekiah, our journey is about enhancing our warfighters’ superiority by developing and integrating forward-thinking communication and technology systems. Each team member plays an important role in making this possible by bringing their skills and knowledge to help our customers tackle their challenges, devise innovative solutions, and support their critical missions. We take care of our employees through a balanced work-life, fair salaries, great benefits, and giving them a voice."
We could combine these under About the role.
Responsibilities list (as given):
- Develop high-quality software design and architecture
- Identify, prioritize, and execute tasks in the software development life cycle
- Develop tools and applications by producing clean, efficient code
- Design relational databases
- Requirements analysis
- Unit and integration testing
- Verification and validation testing
- Peer test application updates
- Automate tasks through appropriate tools and scripting
- Review and debug code
- Perform validation and verification testing (duplicate)
- Collaborate with internal teams and vendors to fix and improve products
- Document development phases and monitor systems
- Ensure software is up-to-date with the latest technologies
- Write and maintain application documentation
- Work in Windows, Unix, and Linux environments
- Work in a SCIF environment
We could deduplicate the verification and validation testing line (keep one). Also maybe combine "Unit and integration testing" and "Verification and validation testing" but keep separate.
Requirements list:
- Two (2) years of professional technical experience in the form of employment history
- Experience and strong desire to invent new ways of approaching problems and developing innovative applications
- Strong skills in debugging and troubleshooting applications to facilitate fixes and improvements
- Ability to communicate ideas to coders, teammates, and management
- Experience working as part of a team of developers, coders, testers, and CM specialists
- Experience with the military/DoD is a bonus, but not required
- Experience using an Agile development approach is beneficial
- Familiarity with geospatial web-based map development is a bonus, but not required
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain, is highly desired
- BSc/BA in Computer Science, Engineering, or a related field preferred, (High School Diploma or Associate Degree acceptable for well-experienced candidates)
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain within 90 days of the start date (duplicate of previous? Actually first says highly desired, second says willingness to obtain within 90 days. Could combine but keep both? Might be redundant. We'll keep both but maybe combine into one bullet: "CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain (highly desired; required within 90 days of start)". That preserves info without duplication. Might be okay.
- The successful candidate will have (at least) 2 years of experience in ONE of the following: C/C++, C#.NET, Java, Python, Amazon Web Services, PHP, Data Science (with coding experience), Experience with WPF libraries, data access libraries (such as MVC)
We need to preserve that list.
Clearance Requirements:
- This position requires an active Secret clearance.
- To be considered for this position, an applicant must be a U.S. Citizen and hold an active Secret security clearance (or higher).
- Travel Required: No
- Potential for Telework: No
We can include Travel and Telework under Clearance Requirements or separate. Since they are not Pay/Schedule/Benefits, we can include them under a section like "Additional Details". But we could add a heading "Clearance & Logistics". However we prefer few sections. Could add a subsection under Requirements? Might be okay to add a heading "Clearance Requirements". We'll do that.
Benefits:
- We offer health, dental, vision, life, and supplemental insurance for full-time employees and their families.
- We also offer holiday and vacation pay, sick leave, performance-based bonuses, a company-matched retirement plan, and an education reimbursement program.
- Explore our benefits and work culture at https://www.zekiah.com/careers.
We should keep the URL as a link? Probably just plain text.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not include / or markdown.
Let's craft:
About the role
We have an opportunity for an enthusiastic Software Developer with a desire to grow while working with a skilled and highly motivated team on leading-edge work. Our team provides IT services for systems engineering and information management systems to multiple major DoD programs. Each team member has opportunities to take on responsibilities according to their experience level and professional growth goals. Our staff mentors one another in their areas of expertise, continuously enhancing the synergistic capabilities of the team.
Here at Zekiah, our journey is about enhancing our warfighters’ superiority by developing and integrating forward-thinking communication and technology systems. Each team member plays an important role in making this possible by bringing their skills and knowledge to help our customers tackle their challenges, devise innovative solutions, and support their critical missions. We take care of our employees through a balanced work-life, fair salaries, great benefits, and giving them a voice.
Responsibilities
- Develop high-quality software design and architecture
- Identify, prioritize, and execute tasks in the software development life cycle
- Develop tools and applications by producing clean, efficient code
- Design relational databases
- Requirements analysis
- Unit and integration testing
- Verification and validation testing
- Peer test application updates
- Automate tasks through appropriate tools and scripting
- Review and debug code
- Collaborate with internal teams and vendors to fix and improve products
- Document development phases and monitor systems
- Ensure software is up-to-date with the latest technologies
- Write and maintain application documentation
- Work in Windows, Unix, and Linux environments
- Work in a SCIF environment
Requirements
- Two (2) years of professional technical experience in the form of employment history
- Experience and strong desire to invent new ways of approaching problems and developing innovative applications
- Strong skills in debugging and troubleshooting applications to facilitate fixes and improvements
- Ability to communicate ideas to coders, teammates, and management
- Experience working as part of a team of developers, coders, testers, and CM specialists
- Experience with the military/DoD is a bonus, but not required
- Experience using an Agile development approach is beneficial
- Familiarity with geospatial web-based map development is a bonus, but not required
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain (highly desired; required within 90 days
for prose. Do NOT repeat the job title as a heading. 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. We need to include sections for content we have: Description (maybe About the role), Responsibilities, Requirements, Clearance Requirements, Benefits, About Us (maybe not needed but could be About the role? Actually About Us is separate but could be considered part of description). The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely we should stick to those. However we have sections like Clearance Requirements and About Us. Could we incorporate Clearance Requirements into Requirements? Possibly as a sub-list? But we need to preserve all substantive information. Could add a section "Clearance Requirements" as its own heading, though not in the example list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. But better to keep to those examples if possible. Clearance Requirements could be part of Requirements (maybe as a bullet). About Us could be part of About the role? But we have a description paragraph that already describes the opportunity. The About Us section is separate marketing. Could we omit About Us? It's substantive but maybe not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep About Us content. Could we put it under a heading "About the company" or "About Us"? Not in examples but we can add. However they said prefer a few substantive sections over many thin ones. Could combine About Us into About the role? Might be okay.
Let's decide sections: About the role (includes description paragraph and maybe About Us). Responsibilities (list). Requirements (list includes experience, skills, education, clearance). Benefits (list). Possibly also Qualifications? But Requirements already covers qualifications. We could skip Qualifications.
We need to avoid duplication: The responsibilities list has many items, some duplicated (e.g., "Perform validation and verification testing" appears twice? Actually list includes "Unit and integration testing", "Verification and validation testing", "Peer test application updates", "Perform validation and verification testing" again later. We should preserve all substantive information but we can deduplicate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Removing duplicates could be considered summarizing away detail? It's ambiguous. Safer to keep duplicates as they appear? But they said remove duplicated lines (in boilerplate). That refers to boilerplate duplicated lines, not necessarily content duplicates. However the responsibilities list has duplicate "Perform validation and verification testing". That's likely a mistake in the posting. Should we keep both? It's not boilerplate; it's duplicate content. I'd keep one instance to avoid redundancy, but that could be considered summarizing away detail. However the instruction about removing duplicated lines likely refers to boilerplate duplicates like EEO statements. I'd keep both? Might look odd. I'd keep one to avoid unnecessary repetition but still preserve the info. I'd note that it's duplicate but we can keep one.
Let's extract content.
Description paragraph: "We have an opportunity for an enthusiastic Software Developer with a desire to grow while working with a skilled and highly motivated team on leading-edge work. Our team provides IT services for systems engineering and information management systems to multiple major DoD programs. Each team member has opportunities to take on responsibilities according to their experience level and professional growth goals. Our staff mentors one another in their areas of expertise, continuously enhancing the synergistic capabilities of the team."
About Us: "Here at Zekiah, our journey is about enhancing our warfighters’ superiority by developing and integrating forward-thinking communication and technology systems. Each team member plays an important role in making this possible by bringing their skills and knowledge to help our customers tackle their challenges, devise innovative solutions, and support their critical missions. We take care of our employees through a balanced work-life, fair salaries, great benefits, and giving them a voice."
We could combine these under About the role.
Responsibilities list (as given):
- Develop high-quality software design and architecture
- Identify, prioritize, and execute tasks in the software development life cycle
- Develop tools and applications by producing clean, efficient code
- Design relational databases
- Requirements analysis
- Unit and integration testing
- Verification and validation testing
- Peer test application updates
- Automate tasks through appropriate tools and scripting
- Review and debug code
- Perform validation and verification testing (duplicate)
- Collaborate with internal teams and vendors to fix and improve products
- Document development phases and monitor systems
- Ensure software is up-to-date with the latest technologies
- Write and maintain application documentation
- Work in Windows, Unix, and Linux environments
- Work in a SCIF environment
We could deduplicate the verification and validation testing line (keep one). Also maybe combine "Unit and integration testing" and "Verification and validation testing" but keep separate.
Requirements list:
- Two (2) years of professional technical experience in the form of employment history
- Experience and strong desire to invent new ways of approaching problems and developing innovative applications
- Strong skills in debugging and troubleshooting applications to facilitate fixes and improvements
- Ability to communicate ideas to coders, teammates, and management
- Experience working as part of a team of developers, coders, testers, and CM specialists
- Experience with the military/DoD is a bonus, but not required
- Experience using an Agile development approach is beneficial
- Familiarity with geospatial web-based map development is a bonus, but not required
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain, is highly desired
- BSc/BA in Computer Science, Engineering, or a related field preferred, (High School Diploma or Associate Degree acceptable for well-experienced candidates)
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain within 90 days of the start date (duplicate of previous? Actually first says highly desired, second says willingness to obtain within 90 days. Could combine but keep both? Might be redundant. We'll keep both but maybe combine into one bullet: "CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain (highly desired; required within 90 days of start)". That preserves info without duplication. Might be okay.
- The successful candidate will have (at least) 2 years of experience in ONE of the following: C/C++, C#.NET, Java, Python, Amazon Web Services, PHP, Data Science (with coding experience), Experience with WPF libraries, data access libraries (such as MVC)
We need to preserve that list.
Clearance Requirements:
- This position requires an active Secret clearance.
- To be considered for this position, an applicant must be a U.S. Citizen and hold an active Secret security clearance (or higher).
- Travel Required: No
- Potential for Telework: No
We can include Travel and Telework under Clearance Requirements or separate. Since they are not Pay/Schedule/Benefits, we can include them under a section like "Additional Details". But we could add a heading "Clearance & Logistics". However we prefer few sections. Could add a subsection under Requirements? Might be okay to add a heading "Clearance Requirements". We'll do that.
Benefits:
- We offer health, dental, vision, life, and supplemental insurance for full-time employees and their families.
- We also offer holiday and vacation pay, sick leave, performance-based bonuses, a company-matched retirement plan, and an education reimbursement program.
- Explore our benefits and work culture at https://www.zekiah.com/careers.
We should keep the URL as a link? Probably just plain text.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We must not include / or markdown.
Let's craft:
About the role
We have an opportunity for an enthusiastic Software Developer with a desire to grow while working with a skilled and highly motivated team on leading-edge work. Our team provides IT services for systems engineering and information management systems to multiple major DoD programs. Each team member has opportunities to take on responsibilities according to their experience level and professional growth goals. Our staff mentors one another in their areas of expertise, continuously enhancing the synergistic capabilities of the team.
Here at Zekiah, our journey is about enhancing our warfighters’ superiority by developing and integrating forward-thinking communication and technology systems. Each team member plays an important role in making this possible by bringing their skills and knowledge to help our customers tackle their challenges, devise innovative solutions, and support their critical missions. We take care of our employees through a balanced work-life, fair salaries, great benefits, and giving them a voice.
Responsibilities
- Develop high-quality software design and architecture
- Identify, prioritize, and execute tasks in the software development life cycle
- Develop tools and applications by producing clean, efficient code
- Design relational databases
- Requirements analysis
- Unit and integration testing
- Verification and validation testing
- Peer test application updates
- Automate tasks through appropriate tools and scripting
- Review and debug code
- Collaborate with internal teams and vendors to fix and improve products
- Document development phases and monitor systems
- Ensure software is up-to-date with the latest technologies
- Write and maintain application documentation
- Work in Windows, Unix, and Linux environments
- Work in a SCIF environment
Requirements
- Two (2) years of professional technical experience in the form of employment history
- Experience and strong desire to invent new ways of approaching problems and developing innovative applications
- Strong skills in debugging and troubleshooting applications to facilitate fixes and improvements
- Ability to communicate ideas to coders, teammates, and management
- Experience working as part of a team of developers, coders, testers, and CM specialists
- Experience with the military/DoD is a bonus, but not required
- Experience using an Agile development approach is beneficial
- Familiarity with geospatial web-based map development is a bonus, but not required
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain (highly desired; required within 90 days
headings and - for lists,
for prose.
We must not include / or markdown.
Let's craft:
About the role
We have an opportunity for an enthusiastic Software Developer with a desire to grow while working with a skilled and highly motivated team on leading-edge work. Our team provides IT services for systems engineering and information management systems to multiple major DoD programs. Each team member has opportunities to take on responsibilities according to their experience level and professional growth goals. Our staff mentors one another in their areas of expertise, continuously enhancing the synergistic capabilities of the team.
Here at Zekiah, our journey is about enhancing our warfighters’ superiority by developing and integrating forward-thinking communication and technology systems. Each team member plays an important role in making this possible by bringing their skills and knowledge to help our customers tackle their challenges, devise innovative solutions, and support their critical missions. We take care of our employees through a balanced work-life, fair salaries, great benefits, and giving them a voice.
Responsibilities
- Develop high-quality software design and architecture
- Identify, prioritize, and execute tasks in the software development life cycle
- Develop tools and applications by producing clean, efficient code
- Design relational databases
- Requirements analysis
- Unit and integration testing
- Verification and validation testing
- Peer test application updates
- Automate tasks through appropriate tools and scripting
- Review and debug code
- Collaborate with internal teams and vendors to fix and improve products
- Document development phases and monitor systems
- Ensure software is up-to-date with the latest technologies
- Write and maintain application documentation
- Work in Windows, Unix, and Linux environments
- Work in a SCIF environment
Requirements
- Two (2) years of professional technical experience in the form of employment history
- Experience and strong desire to invent new ways of approaching problems and developing innovative applications
- Strong skills in debugging and troubleshooting applications to facilitate fixes and improvements
- Ability to communicate ideas to coders, teammates, and management
- Experience working as part of a team of developers, coders, testers, and CM specialists
- Experience with the military/DoD is a bonus, but not required
- Experience using an Agile development approach is beneficial
- Familiarity with geospatial web-based map development is a bonus, but not required
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain (highly desired; required within 90 days
for prose. We must not include / or markdown. Let's craft:
About the role
We have an opportunity for an enthusiastic Software Developer with a desire to grow while working with a skilled and highly motivated team on leading-edge work. Our team provides IT services for systems engineering and information management systems to multiple major DoD programs. Each team member has opportunities to take on responsibilities according to their experience level and professional growth goals. Our staff mentors one another in their areas of expertise, continuously enhancing the synergistic capabilities of the team.
Here at Zekiah, our journey is about enhancing our warfighters’ superiority by developing and integrating forward-thinking communication and technology systems. Each team member plays an important role in making this possible by bringing their skills and knowledge to help our customers tackle their challenges, devise innovative solutions, and support their critical missions. We take care of our employees through a balanced work-life, fair salaries, great benefits, and giving them a voice.
Responsibilities
- Develop high-quality software design and architecture
- Identify, prioritize, and execute tasks in the software development life cycle
- Develop tools and applications by producing clean, efficient code
- Design relational databases
- Requirements analysis
- Unit and integration testing
- Verification and validation testing
- Peer test application updates
- Automate tasks through appropriate tools and scripting
- Review and debug code
- Collaborate with internal teams and vendors to fix and improve products
- Document development phases and monitor systems
- Ensure software is up-to-date with the latest technologies
- Write and maintain application documentation
- Work in Windows, Unix, and Linux environments
- Work in a SCIF environment
Requirements
- Two (2) years of professional technical experience in the form of employment history
- Experience and strong desire to invent new ways of approaching problems and developing innovative applications
- Strong skills in debugging and troubleshooting applications to facilitate fixes and improvements
- Ability to communicate ideas to coders, teammates, and management
- Experience working as part of a team of developers, coders, testers, and CM specialists
- Experience with the military/DoD is a bonus, but not required
- Experience using an Agile development approach is beneficial
- Familiarity with geospatial web-based map development is a bonus, but not required
- CompTIA Security+, equivalent or higher (such as CISSP), or willingness to obtain (highly desired; required within 90 days