Domain Architect

Duration: 6 months of contract to permanent.

Location: Plano TX; Should be local to Plano TX and willing to work onsite at least 3 days a week.

Interview process

1. 1. 45minute MS TEAMs video interview with the Hiring Manager and team.
   2. Technical 4560 minute preferably inperson or MS TEAMs video interview with the Hiring Manager and team.

Domain Architect

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 nonfunctional requirements adhere to the Architecture Standards and aligns with the longerterm 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 faulttolerant 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.

What youll be doing:

1. 1. Be part of the Domain leadership team to create technology strategy and influence technology direction.
   2. Responsible and accountable for all architecture functions within the domain.
   3. Collaborate with other stakeholders and architects to drive consensus.
   4. Responsible for creating and maintaining Business Capability map for the domain.
   5. Creates and maintains Technology Strategy current and target State architectures for the domain.
   6. Participates in all Crossdomain architecture routines.
   7. Support solution architecture to create application high level and lowlevel designs and document the necessary artifacts.
   8. Other activities as assigned by the Domain Architecture Leader.

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
o Engage with the domain as part of the Domain Leadership Team.
o Drive consensus among the leadership on Technology Strategy.
o Validate technology feasibility of business case and concept proposals.

10%

Engagement on assigned Domain OKRs and other miscellaneous projects
o Work with domain stakeholders to understand business requirements.
o Ensure all designs are approved per architecture guidelines and standards.

15%

Supporting Solution Architecture
o Partner with Solution Architects to create High level design.
o Validate low level designs presented by Solution architects.
o Provide guidance and thought leadership to drive fit for purpose solutions.
o Mentor Solution Architects

15%

Creating and maintaining Business capabilities and target state technology architecture
o Create business capability maps by interviewing various business stakeholders.
o Perform capability assessments on new projects and initiatives.
o Create various relevant capability heatmaps to help create technology roadmaps.
o Create value streams for the domain.

15%

Documenting Key decisions artifacts or other items as required
o Capture decisions risks impediments and open items on any design items being discussed.
o Capture proper evidence of decisions.
o Ensure consensus of all relevant stakeholders is captured.

15%

Architecture Governance
o Provide oversight on all high level and lowlevel designs presented in Domain Architecture Office Hours.
o Approve designs that meet gating criteria.
o Make decisions using approved processes such as buyvsbuild.
o Represent the domain in all architectural governance routines.

20%

Cross Domain collaboration
o Work with other SME/Domain Architects to drive design consensus.
o Collaborate with other domain architects and domain architecture leader to identify cross domain impact on design.
o Provide education on any reusable design aspects that can be used across domains.
o Collaborate on other crossdomain initiatives.

10%

• Requirements:

Challenges Examples

Approach / Solution

Describe two to three most common challenges this job faces and how they may be solved.

1. There are multiple vendors development teams and business users involved to create and finalize endtoend technical solutions. It can be challenging to ensure that everyone is aligned and working together effectively.

Should understand current and future IT technical offerings and identify appropriate solutions that are fit for purpose. They should establish clear communication channels to guide and mentor involved parties in the ongoing collection development review and adoption of architecture standards and best practices.

2. Designing too close to a delivery sprint will lead to a potential compromise on architectural standards and best practices.

Early engagement with key stakeholders and understanding requirements and viewpoints will help create a design that can be better aligned with the delivery timelines.

3. Vendor engagements without proper technical due diligence can impact domains strategic goals.

Enable decisioning of product selection through proper technology duediligence and alignment with business and technology strategy.

DecisionMaking

Describe what kind of decisions this job will regularly make and be held accountable for.

1. Articulating and solving critical business problems while demonstrating a strong business acumen.

2. Owning and managing the full technology architecture and the relevant parts of SDLC.

3. Approving system design as changes/enhancements are designed that are alignment with Architecture standards and guidelines.

Working Relationships

Describe the jobholders most frequent internal and/or external contacts. Do not include contacts with the direct manager/supervisor or subordinates.

Contact (e.g. Asst. Legal Counsel ITX external vendor)

Purpose of Contact

Frequency (e.g. daily weekly quarterly)

1. Solution & SME Architects

Coordination of system solutions

Weekly

2. Platform Teams (Platform Cloud Infosecurity governance SRE)

Coordination of system solutions

As needed

3. Design Stakeholders

(Factory Leaders)

Coordination of architecture and development walkthrough and signoffs

As needed

4. Domain Leadership

Create and maintain Capability maps and technology strategy

Weekly

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 TwoYear College Degree

FourYear College Degree (BA or BS)

Advanced Degree. Specify:

Experience Subject Matter Expertise

Required

Preferred

Work Experience

02 years of work experience

02 years of relevant work experience (in similar field and/or industry)

25 years of relevant / progressive work experience (in similar field and/or industry)

510 years of relevant / progressive work experience (in similar field and/or industry)

10 years of relevant / progressive work experience (in similar field and/or industry)

Licenses Certifications & Specialized Skills IH1 (if applicable)