I was interviewed by two technical interviewers. One focused primarily on behavioural questions, while the other handled the technical discussion.

Unfortunately, I found the overall experience quite challenging for reasons beyond the technical difficulty. The technical discussion became increasingly tense, and at times I felt the interviewer was more focused on proving my answers wrong than understanding my reasoning or perspective.

A significant portion of the discussion focused on software architecture and design patterns, including questions about what the “best” design pattern is. I explained that I don't believe there is a universally best design pattern, as architectural decisions depend heavily on the specific problem, requirements, scalability, maintainability, and team context. However, this perspective did not seem to be well received.

There were also moments that made me question the interviewer's familiarity with the iOS topics being discussed. For example, during a discussion about when to use Apple's Combine framework, I referred to publishers, which are a fundamental concept in Combine, but the interviewer appeared unfamiliar with the term.

Communication was also occasionally difficult during the behavioural section, which affected the flow of the conversation.

Overall, I found the interview unnecessarily confrontational rather than collaborative. Technical interviews can and should involve challenging discussions and differing opinions, but I believe the goal should be to understand how a candidate thinks and approaches problems, rather than creating an environment where the interviewer and candidate appear to be arguing against each other. The experience became uncomfortable enough that I seriously considered ending the interview early.

Which software architecture is better and why: MVC, MVVM or MVVM-C?

When starting a new iOS project, which design pattern would you choose: MVC, MVVM or MVVM-C?

Is the MVC design pattern compatible with SwiftUI projects?