Think Of How You’Ll Win. Think Of How You’Ll Not Lose.

My two-step strategy for passing the interview: 1. Win. 2. Don’t lose. It sounds obvious, but the split was very helpful. I’d imagine “Where can I blow them away? Where can I really win?” For me, that was coding in Python. So I wanted to make sure to create and exploit situations to show that off. I wanted them to have some really positive things to say in the debrief. Then the other side was “How would I blow it?” There are some mistakes that can really outweigh the positives and sink you. I knew for Netflix that was not knowing the culture. Some others for me were sucking at SQL and not having good answers for some work history questions. So, I strengthened in these areas and didn’t lose. These things aren’t going to be yours, but just some examples to find your own.

This is a really god paradigm to think about when planning out projects.

Created from: Useful habits for a software engineer 202205212326

uid: 202205212334 tags: #insights #advice #career

Date

February 22, 2023

Up next

Schemas for notes is a great idea (In other words, representing information using a relational database is a generally good idea). Having templated notes for different concepts

Previously

Nothing good comes easy The thing I appreciate the most about Berkeley (and I’ve seen this in people that I’ve interviewed from Berkeley as well) is how Berkeley makes sure