The architectural interviews were mostly focused on if I still was technical or if I'd completely lost touch with what's going on on the front line. There were questions about testing, testing boundaries, testing ideology, and practices. As well as questions regarding architecture for designing a single system to manage all the elevators in the city. It was very open ended. I enjoyed brain storming around the concept.
What Verticals do I feel most comfortable representing?
How did you standardize across iOS and Android user experiences?
What % of the time do you currently spend coding?
They asked a lot about my job history, and how I made things scale. (Which was basically a load balancer, and sharding). When asked very specifically about how to scale something beyond that this didn't seem to suffice for an answer.
What intrigues you to join Salesforce?
Questions around Leadership style, technology/business centricity?
How would you design a fault-tolerant system for a mission-critical application?
Walk us through your management style? How do you handle conflict? How do you measure performance?
Couple of questions on consistency, availability and partition tolerance.
Viewing 1311 - 1320 interview questions