everprep

3m read · 503 words

An ever growing list of things to revise everyday, because I want them to stay in my brain.

Heavily written by LLMs and my own brain-dumps.

Highly unpolished infodump. Not intended for public use.


I'm easily one of the top engineers in every company I've worked for or consulted. And have been regularly told this by heads of various departments.

On top of that, I never put any effort or focus into finding a good full time job. And that has led me here.

Still having to study for interviews is a failure, and a pathetic state to be in.

Everprep exists to prevent this.

Daily revision of everprep keeps you warmed up.

I can be laid off in the morning and crack an interview in the same afternoon. There is no need for "I need 2 weeks to study".

That's the magic of being ready.

These notes are to be revised everyday. They will keep my knowledge sharp and interview ready. 365 days of the year.
Once used to the info, revision barely takes 20mins/day, because maintenance is a very low effort thing.

If I think - "but interview questions don't correspond to real world skill" - then that's the failure of the industry itself.


If the industry is gonna gatekeep jobs with its interview games, then that's actually easy mode for me, and I'm gaming the industry back.

By narrowing the game, it has made it easier for me to get in even into positions I may not be competent enough for. It cuts both ways.

In choosing a more restricted game, the companies have ended up giving me (and people like me) a very distinct advantage.

Everprep. Everready.

Dump to process

Knowledge holes

Product sense


Metrics to start out with
- Engagement metrics
- Retention metrics
- Monetization metrics
- Activation metrics

Segmentation - segment problem across various dimentions
- Geographic, time etc
- Platforms (android, ios, web etc)

Sys design stuff

Build data model for swiggy/zomato/ig/social media apps

Make star schema

Made some bridge tables for handling many to many relationships

Implementation of scd - practice writing queries for their implementation

Consider sources like cdc. Design system around capturing cdc ingestion, storage, transformation, building the data mart.

Misc

Must know

overkill

External resources dump

Colophon 503 words · 3m read
Written as a markdown note in Obsidian. Built into this page by a Python script on 2026-10-02.

Pages