Required Skills & Experience
- 4+ years of experience in Solution Architecture, high-level Systems Analysis, or Architecture Documentation
- Experience documenting complex custom software environments and application ecosystems
- Strong experience creating capability maps, application inventories, architecture diagrams, system context diagrams, and dependency mappings
- Experience developing Product Breakdown Structures (PBS) and documenting application capabilities, modules, features, and ownership
- Working knowledge of requirements management, epics, user stories, source code repositories, test cases, defects, and software development lifecycle artifacts
- Experience building traceability models between business capabilities, requirements, engineering deliverables, and testing artifacts
- Strong stakeholder engagement skills with the ability to gather and document institutional or tribal knowledge from product, architecture, development, testing, and business teams
Nice to Have Skills & Experience
- Experience with LeanIX or other Enterprise Architecture repository tools.
- Familiarity with V-Model development and validation methodologies.
- Experience reviewing source code and technical artifacts to understand system behavior.
- Experience leveraging AI-assisted discovery techniques, documentation mining, dependency analysis, or source code analysis tools.
- experience at a company that sells a software and/or Entitlement & Licensing experience
Job Description
Insight Global is looking to add an Enterprise Architect to their clients team to support architecture documentation and traceability for a business-critical custom entitlement, licensing and provisioning application landscape. This person will partner with product owners, architects, developers, testers, and business stakeholders to create a comprehensive understanding of the current application landscape. They will review existing architecture artifacts, documentation, epics and stories, source code repositories, test assets, and system diagrams to understand how the platform functions today. They will conduct discovery sessions with key stakeholders to capture undocumented knowledge, document application capabilities and ownership structures, and create a current-state architecture baseline that clearly illustrates applications, services, integrations, data objects, data flows, dependencies, and system interactions. They will also be resposible for developing and maintaining a Product Breakdown Structure (PBS), mapping business capabilities, modules, features, ownership, and application relationships to create a centralized source of truth for both technical and non-technical stakeholders. Additionally, they will establish traceability between product capabilities, requirements, epics, user stories, code repositories, testing artifacts, defects, and validation evidence while identifying areas where documentation, ownership, or traceability is missing. The ultimate goal is to leave behind clear, maintainable documentation that improves transparency, supports onboarding, and enables teams to understand how the application ecosystem operates without relying on tribal knowledge or individual subject matter experts.