Skip to contentSkip to footer

Senior Software Architect Interview Questions

Salaries
Interviews

2,179 senior software architect interview questions shared by candidates

First Phone Interview: Behavioral question- Tell me about how you were curious (obviously about an area of work or technology), the expectation also seemed, what you did and apply as part of being curious. Technical questions: What is the cloud, later prompts about what are the advantages, later another question about its difference with co-location (where you rent data center space and gear). How would you design a 3 tier application in the cloud. How would you scale and make the application HA, reliant and secure. Block, Object and File stores and when would you use them (EBS, S3 and EFS). Relational and no sql dbs, when would you use them. Name and explain networking protocols- I offered tcp, udp, icmp, I should have added enveloping IP, snmp, ftp etc. but did not think of it at the time. Difference between a level 4 and level 7 firewall, checked if I knew of the OSI model. Types or RAIDs. NAS and SAN. Types of KV, memory DBs. Difference between symmetric and asymmetric encryption. What does networking and security in the cloud look like- VPCs, subnets, SGs, resources and privileges based policy constructs, nacls, routes, AWS inspector, guard duty, VPC flow logs, cloudtrail etc. How would you convince a legacy on-prem data center stake holder to move to the cloud and address security, reliability, performance, cost etc. concerns. I touched on API Gwy, AWS WAF, Lambda, Route53, ALB and some other features as part of my responses. Second Interview: Tell me of a time when you had to disagree with your supervisor and what was the outcome. Tell me of a time when you had to disagree with your peers and what was the outcome. Tell me of a time when you opted or pushed for a solution that was good for the long run but had resistance upfront. Tell me of a time when you trouble shot two or more issues that were symptomatically not related but had a common cause that was not apparent initially and how did you drill down and resolve the root cause. The more the tell me's wore on I felt like I was composing more than telling it like it was and for one instance I was grabbing frantically for an answer.
avatar

Senior Solutions Architect

Interviewed at Amazon

3.5★
Dec 13, 2018

First Phone Interview: Behavioral question- Tell me about how you were curious (obviously about an area of work or technology), the expectation also seemed, what you did and apply as part of being curious. Technical questions: What is the cloud, later prompts about what are the advantages, later another question about its difference with co-location (where you rent data center space and gear). How would you design a 3 tier application in the cloud. How would you scale and make the application HA, reliant and secure. Block, Object and File stores and when would you use them (EBS, S3 and EFS). Relational and no sql dbs, when would you use them. Name and explain networking protocols- I offered tcp, udp, icmp, I should have added enveloping IP, snmp, ftp etc. but did not think of it at the time. Difference between a level 4 and level 7 firewall, checked if I knew of the OSI model. Types or RAIDs. NAS and SAN. Types of KV, memory DBs. Difference between symmetric and asymmetric encryption. What does networking and security in the cloud look like- VPCs, subnets, SGs, resources and privileges based policy constructs, nacls, routes, AWS inspector, guard duty, VPC flow logs, cloudtrail etc. How would you convince a legacy on-prem data center stake holder to move to the cloud and address security, reliability, performance, cost etc. concerns. I touched on API Gwy, AWS WAF, Lambda, Route53, ALB and some other features as part of my responses. Second Interview: Tell me of a time when you had to disagree with your supervisor and what was the outcome. Tell me of a time when you had to disagree with your peers and what was the outcome. Tell me of a time when you opted or pushed for a solution that was good for the long run but had resistance upfront. Tell me of a time when you trouble shot two or more issues that were symptomatically not related but had a common cause that was not apparent initially and how did you drill down and resolve the root cause. The more the tell me's wore on I felt like I was composing more than telling it like it was and for one instance I was grabbing frantically for an answer.

Viewing 401 - 410 interview questions

Glassdoor has 2,179 interview questions and reports from Senior software architect interviews. Prepare for your interview. Get hired. Love your job.