Job Title

Your main responsibilities

·       General SAFe Train Specific Activities

§  Plan and Design a unique Architecture model which will not only adoptable for all the competency Centres but also will ensure the custom requirements from all of them are met.  E.g., Flexible enough to work with different Content Management Systems or having an operational model that supports both On-Premises and Cloud or accommodating Airline’s Middleware and Airlines Extension layer for handling airline specific business logic etc.

§  Work with the technical experts of each competency center to create a synergy among them.

§  Define a standard approach for handling Non-Functional Requirements (NFRs) across Competency Centers (CCs).

§  Participate in all the solution discussions and create awareness among the experts about not to repeat (duplicate) anything.

·       Handling of PI Planning & PI Event

§  Preparing the Architecture Runway for the Train that will ensure the interests of the different types of CCs/Teams are addressed

§  Identifying the Transversal/NFR objectives that will enable CCs to address their Technical Debt, Technical Migrations that are very much Needed, Software version upgrade to liaise with Security, Improve the Developer Experience by addressing/resolving their pain points etc.

§  Align with the stakeholders on the selected objectives - SMs, Team Leads, Dev Managers, CC Owners, Division Head etc.

§  Tracking all the Program Increment (PI) objectives throughout the PI and ensure to its (logical) closure

§  Keep the Management up to date about the status of committed & uncommitted Objectives of that particular PI

§  Highlight the Risks well in advance and ensure that is raised in the leadership forums

§  Track the dependencies from other Trains that are delivered on time and raise it to the Leadership forum if not.

·       Handling the "Virtual" System Team

§  Definition: System Team comprises of Technical Experts from different CCs, who work together to handle Transversal and NFR activities at Train level

§  As a System Architect and as a owner of "Virtual System Team"

ü  Identify the Technical and NFR objectives that can address both CC as well as Organizational interests (as part of PI planning)

ü  Categorize them into different EPIC/Features/User Stories

ü  Work with PM and Align the objectives in different Sprints based on the available resource/bandwidth

ü  Running regular Virtual System Team catchup with the primary goals of,

·       Capture the status of the on-going Sprint

·       Discuss Risk/blockers

·       Discuss Global Initiatives around - Security, Quality and DevOps

ü  Collaborate with the CC Owners to address the Community of Practices objectives

ü  Sharing the knowledge regarding the Architectural Decisions that are made across Digital

ü  Study and help CCs Technically ready for any Organizational move / migration (E.g. Private/Public Cloud Migration)

·       Handling Individual CCs

§  CCs in ART are very different in nature and each having unique Technical Stack.  Hence not every Transversal / NFR items identified at Train level would be applicable to all CCs

·       Understand the Technical Stack and Dedicated Features of every CC in the Train

·       Having a periodic communication with CC's Architect/Technical Experts (E.g., Virtual System Team catchup)

·       Participate in a meeting with the Airline customers for any new requirements that needs Architectural Change or has Security Concerns or needs a quick POC etc.

·       Discuss with Technical Experts from each CC and prioritise the CC Specific Transversal/NFR, Technical Dept or Stack migrations

·       Handling the Community of Practice:

§  Active participation in all the CoP activities - Architect Community, Security CoP, Quality CoP, DevExp CoP, DevOps CoP, Performance CoP, Private/Public Cloud, Data/Analytics, Pelican or API Extensions etc.

§  Follow the recommendation laid out by these CoPs and try to look out every opportunity to include them in the SDL of the CC's.

§  Certain recommendations from these CoP would need urgent attention and action (like Security, Quality, Performance). Bring those items to the Train's stakeholders notice and ensure that they are addressed asap.

·       Collaboration

§  As a System Architect collaboration with other Train(s) Leadership is required at every stage of the Program Increment (PI) Lifecycle

·       Participating in Weekly Sync-up with other Train's leadership and be aligned with them

·       Participate in weekly System Architects Forum and share the updates

·       Participate in weekly Architecture Community and understand the changes that are going thru across Digital

·       Share the knowledge with the Train's Management, Leadership and Stakeholder

About the ideal candidate

·       Minimum of 12+ years of experience with technical hands-on in full-stack development & helping other team members

·       Technical Expertise:

§  JAVA, J2EE

§  Web Technologies - Angular, OOJS

§  Exposure to Python, Scala

§  Cloud (OpenShift/Kubernetes/Docker)

§  Databases – MS SQL, Oracle, NoSQL

§  HDFS, Apache Spark

·       Detailed Tech Stack:

§  Excellent command on OOPs in Java, Angular. Knowledge in JavaScript / HTML is good to have.

§  Good skills in Unix environment 

§  Good knowledge and demonstrable experience in Cloud based development (Docker container technology in Kubernetes / OpenShift preferred)

§  Good Knowledge on NoSQL Database (Couchbase Preferred)

§  Hands on experience of using data structures, extended libraries in JAVA with knowledge in Design patterns

§  Excellent knowledge in microservices and their design patterns (Knowledge on Quarkus Microservice framework would be a plus)

§  Experience in XML, RestAPI is mandatory and Edifact is good to have

§  Good Experience with Troubleshooting and monitoring tools (Yourkit, Grafana, JMeter Preferred)

§  Experience with Continuous Integration and Continuous deployment is a plus (Jenkins Preferred)

§  Deep understanding of non-functional requirements (NFR) and/or underlying technologies impacting final solution

§  Strong communication abilities to convey technical information to stakeholders and / or be able to influence technical decisions

§  Awareness of latest technology trends and standards in the industry.

Processes

·       Agile (Scrum) methodology

·       Good Troubleshooting skills, Good Communication Skills

·       Perform Code reviews

·       Weekly reports on status of the items worked

Proposals, implementations of best processes and standard practices within the team

Diversity & Inclusion

Amadeus aspires to be a leader in Diversity, Equity and Inclusion in the tech industry, enabling every employee to reach their full potential by fostering a culture of belonging and fair treatment, attracting the best talent from all backgrounds, and as a role model for an inclusive employee experience.  

Amadeus is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to gender, race, ethnicity, sexual orientation, age, beliefs, disability or any other characteristics protected by law.