> Markdown version of [/jobs/ext/4730531-backend-software-developer-ts-sci-fsp](https://www.wearedevelopers.com/jobs/ext/4730531-backend-software-developer-ts-sci-fsp). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Backend Software Developer TS/SCI (FSP) - **Company:** IBM - **Location:** Appomattox, VA, United States - **Contract:** Permanent contract - **Skills:** Testing (Software), Clean Code Principles, Java (Programming Language), Agile Methodology, Amazon Web Services, Confluence, JIRA, Unit Testing, C++ (Programming Language), Cloud Engineering, Software Quality, Code Reuse, Code Review, Relational Databases, Python (Programming Language), PostgreSQL, Secure Coding, Software Engineering, Backend, Git, Integration Tests, Information Technology, Software Version Control, Programming Languages - **Published:** November 15, 2026 - **Apply:** https://www.dice.com/job-detail/17078405-1e8b-4805-9298-d012f2f22cfa ## About the Role Bachelor's Degree Preferred education Master's Degree Required technical and professional expertise * U.S. Citizen with an active TS/SCI clearance and in-scope Full-Scope Polygraph (FSP) required on Day 1; must work 5 days/week in a SCIF in Annapolis Junction, MD. * Bachelor's degree in Computer Science, Software Engineering, or a related technical field, with 10+ years of software development experience, preferably in federal or defense environments. * 1+ year of hands-on AWS experience and proficiency in one or more programming languages, such as Java, Python, or C++. * Experience with relational databases such as PostgreSQL, secure coding practices, and development within classified environments. * Strong understanding of the Software Development Life Cycle (SDLC), Agile methodologies, and Git/version control. Preferred technical and professional experience * 1+ year of software engineering experience with AWS classified cloud architecture, including analyzing user requirements and developing software designs and algorithms within system constraints. * Experience with software testing and quality control, including developing/executing test procedures and validating new or modified software. * Experience with Jira and/or Confluence and creating clear technical documentation to support software development activities., Being an IBMer means you'll be able to learn and develop yourself and your career, you'll be encouraged to be courageous and experiment everyday, all whilst having continuous trust and support in an environment where everyone can thrive whatever their personal or professional background. Our IBMers are growth minded, always staying curious, open to feedback and learning new information and skills to constantly transform themselves and our company. They are trusted to provide on-going feedback to help other IBMers grow, as well as collaborate with colleagues keeping in mind a team focused approach to include different perspectives to drive exceptional outcomes for our customers. The courage our IBMers have to make critical decisions everyday is essential to IBM becoming the catalyst for progress, always embracing challenges with resources they have to hand, a can-do attitude and always striving for an outcome focused approach within everything that they do. Are you ready to be an IBMer? ## Description Seeking a versatile backend software developer with TS/SCI US Government security clearance and FSP to join a small agile team designing, developing, and maintaining secure, scalable software solutions for government customers. The team is fast-paced, collaborative, and cohesive, and depends on team members to communicate openly and to design solutions and deliver quality models on a regular, aggressive clip. The software developer will translate mission requirements into technical specifications and implement robust, maintainable code. Conduct code reviews, unit testing, and integration testing to ensure software quality and security compliance. Provide input to the system design, to include hardware/software trade-odds, software reuse, use of COTS/GOTS in place of new development, and requirements analysis and synthesis from system level to individual software components.