Capital Technology Group
Full Stack Engineer
About this role
Capital Technology Group seeks a Solutions Architect III to design and lead secure, scalable technical solutions for federal modernization initiatives. This remote role focuses on end-to-end architecture across applications, cloud infrastructure, APIs, and enterprise systems while mentoring engineering teams and partnering with cross-functional stakeholders.
What you'll do
- Design end-to-end technical solutions spanning applications, integrations, cloud infrastructure, and enterprise platforms
- Translate business and mission requirements into scalable architecture strategies and standards
- Lead architecture discussions, design reviews, and solution decision-making across teams
- Guide API architecture design for REST and GraphQL services with focus on security and scalability
- Define architecture patterns, engineering best practices, and modernization strategies
- Mentor engineering teams and provide architectural leadership across federal programs
What they're looking for
- Java, Spring Boot, Groovy, OpenJDK
- Frontend architecture (Angular, React, TypeScript, JavaScript)
- GraphQL and REST API design
- Database design (MySQL, PostgreSQL)
- AWS or Azure cloud platforms
- Microservices and event-driven architecture
- DevSecOps, CI/CD pipelines, and secure application design
- Technical communication and stakeholder management
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Capital Technology Group
Capital Technology Group builds secure, scalable technology solutions for federal government modernization initiatives, with particular expertise in Identity & Access Management systems. The company is hiring quality assurance and solutions architecture roles to lead technical delivery on mission-critical government programs.
View all jobs at Capital Technology GroupLikely interview questions
- Walk us through how you've designed an end-to-end solution involving multiple systems, APIs, and cloud infrastructure. What were the key architectural decisions and tradeoffs you made?
- Describe your experience architecting REST and GraphQL APIs. How do you decide between these approaches for different use cases?