Captivation Software
Software Engineer 3 -AWS/Docker/Kubernetes/Java/JavaScript/MongoDB/Elasticsearch
About this role
Captivation Software seeks a Senior Software Engineer to develop backend web services and full-stack solutions for metadata management in mission-critical analytic workflows. This role requires 20 years of software engineering experience, current Top Secret/SCI clearance, and expertise across AWS, Docker, Kubernetes, Java, JavaScript, MongoDB, and Elasticsearch.
What you'll do
- Design and develop backend web services and server infrastructure for metadata capture, tracking, and management
- Build full-stack solutions with primary focus on backend systems and secondarily on functional UI components
- Integrate open-source tools and frameworks including AWS, Docker, Kubernetes, Spring, and JMS
- Implement and manage data storage solutions using MongoDB, Elasticsearch, PostgreSQL, and MySQL
- Support mission analytic workflow processes through robust software architecture
- Collaborate with team to deliver solutions on time while maintaining code quality and innovation
What they're looking for
- Java
- JavaScript
- AWS
- Docker
- Kubernetes
- MongoDB
- Elasticsearch
- Spring Framework
Opens the official application on the employer’s site. No login required.
Captivation Software
Captivation Software builds high-performance computing and secure analytics infrastructure for mission-critical government programs, specializing in HPC testing, enterprise dataflow architectures, and cleared defense systems. The company is hiring senior test engineers, systems engineers, and technical leaders with deep expertise in Linux, cloud infrastructure, and security clearances to validate systems and architect solutions for intelligence community operations.
View all jobs at Captivation SoftwareLikely interview questions
- Walk us through your experience architecting and deploying containerized applications using Docker and Kubernetes in production environments.
- Describe a complex metadata management system you've built—how did you design the data model and what databases did you choose and why?