Responsibilities
- Own architecture for VA IT programs: reference architectures, integration patterns, platform decisions, and roadmaps — with clear documentation of trade-offs.
- Write proof-of-concept code and hands-on prototypes to de-risk architectural decisions and validate solutions before they reach customers.
- Represent Credence technically to VA stakeholders (OIT, EHRM, VHA) — in RFI responses, oral presentations, and relationship-building touchpoints.
- Contribute to capture strategy for VA opportunities — technical volume authorship, win-theme development, technical Q&A, and customer discovery.
- Provide architectural guidance and technical mentorship to Credence engineering teams as they come into VA delivery work.
- As the practice matures, review and validate solution designs from delivery teams against Credence's architectural standards and VA compliance requirements.
- Partner with our VA practice lead on customer engagements and on positioning Credence's AI-native capabilities for VA modernization.
- Document architectural decisions, integration contracts, and technical standards so engineering teams can execute against them with clarity.
Team
Structure: Flat, empowered capture and delivery culture; senior technical leaders are active in winning and delivering work. This is a senior individual contributor role with no direct reports initially, but will become the technical center of gravity as the VA practice grows.
Additional Information
- Understanding of Agile, Service-Oriented Architecture, DevOps, Automated Testing and Deployment, Microservices, and Containerization.
- Demonstrated experience designing and de-risking large, complex solutions — preferably in cloud and/or container environments.
- Certifications: Technical certifications such as AWS Solutions Architect, Azure Solutions Architect, or similar are valued but not required. Non-technical certifications (PMP, ITIL) are not weighted.
- Communication & Soft Skills: Excellent oral and written communication — comfortable briefing senior VA stakeholders and defending architectural decisions in technical review.
- Critical thinking and the ability to look at problems from multiple angles.
- Comfort with ambiguity and a bias toward action in a fast-moving, capture-driven environment.
