Ignore the title for now and read through it, I believe there are excellent tips in note taking and how to process the notes to really excel in your studies.
If you're already working you have to adapt that system into something that works for you best, some use a bullet journal or audio notes and process them differently.
One really interesting approach (that I wasn't able to implement yet in full form) is to take creative notes (called sketchnotes). This works well if you're a visual person.
A great book on this would be The Sketchnote Handbook by Mike Rohde.
I agree with the people who answered before me. The smaller the startup the more important your side project could be. The bigger the company, the more streamlined the hiring process and the more likely that you would encounter puzzles etc.
I'd say if you're going for FAANG-type companies, definitely prepare for the puzzles and quizzes, but for a more smaller one (let's say sub-100 people) go for the side project approach.
Exceptions do apply obviously: I've had friends who got hired at FAANG because of a side project that grew and got the attention of the engineers at said company.
I started out in product management, junior level. Then product owner (focus mobile) later on head of product and then c-level.
Developers (or PMs) who are interested in the business they work in and participate actively tend to get promoted/pushed. You have to understand the business perspective if you want to move up and get away from the thought of "I'm just here to develop and if I make the product great, everyone will recognize my talent/skill"
No I get it, you're right. It's not that I'm counting them out, it's more of an advantage that people with side projects tend to have, but it's super individual and my opinion is just one of many.
For those who feel like a side project needs to be successful or reach a certain amount of revenue/lines of code/users to be successful in your eyes: Don't feel pressured.
In my career (granted not a long one, but made it to C-Level in a startup after about 5-7 years) I've always used them to show my interest and learning skill to do something. It didn't matter whether it had 1 user or 1 million, employers were always very impressed and it always gives you an advantage during interviewing. Most of those have also been with very little or no code at all.
I'm normally prioritising people with side projects in the recruiting process vs. people who only did school -> work
I'd argue that only the last two questions are relevant.
- Both web and smartphone apps can create this kind of revenue.
- The tech stack is 99% irrelevant unless the end customer depends on it, which in 99% of the times, isn't the case.
Thanks!