An IBM Z Architect is a leader in the definition and architecture of an end-to-end solution including the IBM Z platform. During construction, a Z Architect is the advocate for the client and guides the technical team. The Z Architect defines the structures of solutions and architectures to address client business strategy & problems; understands client needs and business constraints, works in levels of abstraction, applies industry knowledge, and leverages appropriate business elements and IT to address those needs; ensures viability of the proposed solutions – conducting solution assurance assessments; identifies and mitigates potential risks to the success of the project; pro-actively mediates resolutions to project conflict; and documents architectural decisions across the above elements. The Z Architect’s work is focused on the front end of the solution lifecycle: listening to stakeholders, understanding their business problem, their requirements, making trade-offs between the business requirements, constraints of the system, and concerns of the various stakeholders and systematically forming incrementally more detailed definitions of the structures of a solution — an architecture. Guides Functional Objectives or Technologies.

Skills:

Environment:
Professional knowledge related to incumbent’s function/business unit and its processes.

Communication/Negotiation:
Advises other professionals. Effectively utilize group dynamics. Negotiates to define approaches and goals.

Problem Solving:
Recognizes complex problems related to functional objectives. Applies creativity and judgment to developmental work on different projects within the business environment. Analyzes situations and implement solutions, or develop new system elements, procedures, or processes.

Contribution/Leadership:
Provides ongoing technical/operational guidance to lead professional work teams, conducts special projects, or manages department(s) (national or international). Understands department/ functional mission and vision. Utilizes expertise to directly influence people outside department or function. Sometimes no precedent exists. Defines and decides objectives within specified business concept or project and may have responsibility for tools and assigned resources.

Impact on Business/Scope:
Accountable for department results and for activities and/or projects involving multi-functional teams.
Activities are subject to business measurements, impact customer satisfaction, and impact project costs or expenses. Regularly participates in overall functional program planning.