Domain Architect

Job Description: These Domain Architect should have hands-on experience acting as Architects in their current 4-5 years of professional experience with background of being technological experts in Cloud [AWS services], Infosec, Microservices, APIs, Data and other integration patterns, etc. Looking for candidates who are skilled in enterprise application portfolio management, technology portfolio management. Having experience with any EA framework such as TOGAF, Zachman, etc. as well as with any EAM tools such as LeanIX, Ardoc, ArchiMate, etc. Candidates should have great communication, solution providing and articulation skills who can not only provide technical solutions in the domain but can also have it communicated to high-level leadership, technical delivery as well as non-technical teams. Duration: 6 months of contract to permanent. Location: Plano, TX; (locally to Plano, TX) and willing to work on-site at least 3 days a week. Job Summary : Summarize the primary purpose of the job. Include a brief statement of why the job exists and what business impact it has on the department, other business units, and/orToyota. The Job Summary should capture typical expectations of the job, not individual performance contributions or one-off assignments.(1-2 paragraphs). The Domain Architecture Owner is responsible and accountable for all Architecture and design decisions within a Domain. They ensure proposed technology solutions are designed to meet or exceed functional requirements, non-functional requirements, adhere to the Architecture Standards, and aligns with the longer-term digital transformation strategy. The candidate would possess strong leadership, excellent oral and written communication skills, and a proven ability to present and discuss technical, functional, and managerial information clearly and concisely to various stakeholders from Business Executives to Developers. Expertise in architecting and developing secure, scalable, reliable, fault-tolerant distributed applications. The Domain Architecture Owners partner with their assigned Domains to drive key technology decisions. They create and maintain business architecture artifacts and domain technology roadmaps. Job Accountabilities: Accountabilities should be grouped into blocks of 10% to 25% of time. If any activity is 5% or less, combine it with related activities. If any activity is more than 25%, break it down into smaller activities. Begin each job accountability with an action word such as develop, analyze, coordinate, advice, approve, manage, lead, etc. Primary Job Accountabilities % of Time Domain Leadership Engagement Engage with the domain as part of the Domain Leadership Team. Drive consensus among the leadership on Technology Strategy. Validate technology feasibility of business case and concept proposals 10% Engagement on assigned Domain OKRs and other miscellaneous projects Work with domain stakeholders to understand business requirements. Ensure all designs are approved per architecture guidelines and standards. 15% Supporting Solution Architecture Partner with Solution Architects to create High level design. Validate low level designs presented by Solution architects. Provide guidance and thought leadership to drive fit for purpose solutions. Mentor Solution Architects 15% Creating and maintaining Business capabilities and target state technology architecture Create business capability maps by interviewing various business stakeholders. Perform capability assessments on new projects and initiatives. Create various relevant capability heatmaps to help create technology roadmaps. Create value streams for the domain. 15% Documenting Key decisions, artifacts, or other items as required Capture decisions, risks, impediments, and open items on any design items being discussed. Capture proper evidence of decisions. Ensure consensus of all relevant stakeholders is captured. 15% Architecture Governance Provide oversight on all high level and low-level designs presented in Domain Architecture Office Hours. Approve designs that meet gating criteria. Make decisions using approved processes such as buy-vs-build. Represent the domain in all architectural governance routines. 20% Cross Domain collaboration Work with other SME/Domain Architects to drive design consensus. Collaborate with other domain architects and domain architecture leader to identify cross domain impact on design. Provide education on any reusable design aspects that can be used across domains. Collaborate on other cross-domain initiatives. 10% Requirements: Knowledge and Skills Describe the minimum education and experience required or preferred to perform this job. Include any licenses, certifications, or specialized skills that are either required or preferred to perform the job. Education - Required Preferred - Degree, High School Education or Equivalent Associate Two-Year College Degree, Four-Year College Degree (BA or BS), Advanced Degree.