Engineering video
0:59 · 23 July 2023
Being cornered in technical discussions can cause people to become defensive or irritated, which can cost them the opportunity. A better strategy is to be directly honest about what you know and do not know, such as admitting when you have not worked with a specific architecture while offering a reasonable guess based on related principles.
Hear it at 0:04 →Senior developer type, treat auto-handler, kill them with kindness. Many times in a technical interview or a technical discussion, you will find yourself cornered with questions. You see, some developers feel the need to be the smartest in the room, and they will try to prove their superiority by turning the technical interview into an FBI-style interrogation. Most people in these scenarios will get defensive and even irritated, which will send the wrong vibes and might cost you the job.
A much better strategy would be direct honesty, tell them what you know and what you don't. As for their advice, if they ask you, how would you architect a micro frontend application and you never architected one? Tell the truth, I've never really worked in a micro frontend scenario before, but hey, my best guess is that we should use the same principles people used in microservices in the backend, such as domain driven design, because micro frontends mimic them in many ways.
This approach shows that you are confident in what you know and what you don't, and it also invites the interviewer to be part of the process, which disarms the whole situation. Try it and thank me when you get the job.
