Software Architect Interview Questions

Following is a list of questions that I was asked in an interview for the position of C++  Software Architect.

 I'll add full context and explanation along with my answers sometime later. For now just note that subsequent questions were follow-up of answers to previous questions and each of the following question were asked in exact same order I have written here:

  1. Tell me about your company, its products & services and explain your role.
    In brief, my answer included creating/preparing architecture and high level and low level designs 
  2. What do you mean, when you say high level design and what do you mean by low level design
  3. What are the differences between high and low level designs?
  4. What are the differences between high level design and architecture?
  5. What are the differences between low level design and architecture?
  6. What is the intent of Software Architecture, High level Design and Low level Design?
  7. What do you do once you are done with High level design?
  8. What do you do once you are done with Low level design?
  9. What are the 3 main things that an architecture that you create, should have? Why?
  10. How important is the need to be aware of current trends?
  11. Who all are the stakeholders when you discuss your system architecture?
  12. Why did you include QA/testing team in stakeholders list?
  13. How many architects were there for the product/feature that you designed and implemented?
  14. How do you ensure that the architectures prepared by different architects for different parts converge?
  15. What are the top 3 traits any Software Architect must have?
  16. Explain the architecture of your company's product, if its not something that is confidential?
  17. Can you explain the architecture of system/feature/product that you designed, if its not confidential. 
  18. How is a layered architecture different from n-tier architecture?

Comments

Post a Comment

Popular posts from this blog

Pixel perfect typography in HTML : canvas or span?

The support for rich typographic features for Web is increasing continuously. Support for web fonts with @font-face rules and open type features was a big leap forward. For some beautiful examples see  Awwwards  typography section: https://www.awwwards.com/websites/typography/ But its still well behind the high end capabilities of page layout design and publishing desktop applications such as QuarkXPress , Adobe InDesign , Scribus , Serif PagePlus/Upcoming Affinity Publisher etc. Text with rich typographic control provided in these kind of applications cannot be represented on Web with simple mapping of objects to html elements and properties/attributes to css styles. So I was tasked with a similar requirement: The rich typographic contents of the page layout and designs of the application must appear pixel-perfect in html browser and different e-readers. The analysis narrowed down to a couple of ways Having usual <p> and <span> elements and controlling their po
Read more

What every developer / programmer must know about Unicode / Floating Point / Memory / DBMS/ CSS/ Your Topic Here

In this post, I intend to compile a list of links to resouces on What everyone should know about different technologies and concepts. So reader, please suggest topics and the article/book/video link in comments, I'll update the list attributing you as contributor. Thanks Updated: 01-Mar-2019 (Added Memory entry) Updated: 17-Jan-2019 (Added DBMS entry) Unicode The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) - An eassy by  JoelSpolsky . Floating Point What Every Computer Scientist Should Know About Floating-Point Arithmetic  - IEEE 754 article by David Goldberg What Every Programmer Should Know About Floating-Point Arithmetic - Explains concepts of above paper, making it accessible to novices. Memory What Every Programmer Should Know About Memory - By Ulrich Drepper .NET What Great .NET Developers Ought To Know - Article by  Scott Hanselman .
Read more