Book Image

Cracking the IT Architect Interview

By : Sameer Paradkar
Book Image

Cracking the IT Architect Interview

By: Sameer 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 (14 chapters)

Dos and dont's for interviews

This section describes the do's and dont's while preparing for an architect job interview:

  • Collect great examples from the past: Consolidate the key engagement case studies you have done in the past. Articulate all details about the processes, methodologies, and frameworks required for building enterprise/solution architecture. Collate key case studies in the area of data, application, business, and infrastructure architecture, and the work done in the NFRs domain.

  • Speak the language of business: An EA or SA needs to connect with strategic business stakeholders. Make sure the discussions don't emphasize technology jargon as the business stakeholders do interviews for these key positions and may not be able to relate to jargon. An SME in this position who fears not being at your knowledge level will be intimidated. Make sure that any questions you ask come as inquisitive and not condescending.

  • Share vision and critical decisions: EAs have to share the vision...