Book Image

Cracking the IT Architect Interview

By : Paradkar
Book Image

Cracking the IT Architect Interview

By: Paradkar

Overview of this book

An architect attends multiple interviews for jobs or projects during the course of his or her career. This book is an interview resource created for designers, consultants, technical, solution, domain, enterprise, and chief architects to help them perform well in interview discussions and launch a successful career. The book begins by providing descriptions of architecture skills and competencies that cover the 12 key domains, including 350+ questions relating to these domains. The goal of this book is to cover all the core architectural domains. From an architect’s perspective, it is impossible to revise or learn about all these key areas without a good reference guide – this book is the solution. It shares experiences, learning, insights, and proven methodologies that will benefit practitioners, SMEs, and aspirants in the long run. This book will help you tackle the NFR domain, which is a key aspect pertaining to architecting applications. It typically takes years to understand the core concepts, fundamentals, patterns, and principles related to architecture and designs. This book is a goldmine for the typical questions asked during an interview and will help prepare you for success!
Table of Contents (9 chapters)

Summary

An architect is like a pilot. He does not look busy all the time, but he leveages years of expertise to monitor the situation and take immediate action in case of out-of-the-ordinary events. The project manager performs the management chores, freeing the architect from the hassles of operational tasks. The architect is responsible for the quality of the engagement and the delivery to business.

This will be difficult to achieve without authority and requisite skills, which is key to the success of any engagement. An excellent architect should be able to spot an issue in the landscape, get the team together, and, without picking victims, explain the issues and provide an elegant resolution. It is respectable for an architect to ask for help from his team. The team should feel they are part of the journey, but the architect should orchestrate these discussions and recommend the right road map.