Animesh
Product engineering at an early stage startup · Bangalore · writing since 21 May
Day 91 · public proof
How Animesh thinks
Decides and owns the call — moves before being told.
↳the log that shows itarticulate·curious·decisive
◈ Open to being sharpened⤳ Sharpens others · 26
How Animesh thinks, mapped · lit by their own logs · 8 showing
How they reason · the four moves
Evidence
argue from what you saw, not what you assumed
Alternative
name the option you didn't take
Assumption
surface what you're taking on faith
Tradeoff
state the cost of the call
How they work · the qualities founders read for
Curious
you ask, not just assert
Articulate
you write the full why
Ownership
you own the call & the miss
Persistent
hard things become lessons
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones3 earned
Day 30 · Jun 19Day 20 · Jun 09Day 10 · May 30
About
JavaScriptRubyPostgresMySQLAWSReactRails
Mock interviews
Animesh has asked the questions 2 times.
Nobody is scored in these. What you are reading is what they chose to write about their own hour. Sit one →
Animesh · the character an interview can’t show
130 logs over 19 weeks — read from their own words.
Shown so far: Honest when it's not working, Adjusts, Lifts other people's work and Makes the tools better.
Character · what an interview can’t reach
✓Shown
Honest when it's not working
10 stuck and 11 hard days, logged plainly instead of hidden.
Proof · from their own logs
25 May
✓Shown
Adjusts — updates when the evidence changes
Changed course 5 times in the open, with the reason written in — not dug in.
Proof · from their own logs
27 May
✓Shown
Lifts other people's work
1 sharpen + 0 nominations on peers' logs.
Proof · logs they sharpened
4 Aug
✓Shown
Makes the tools better
1 report they filed got fixed — they improve what they use, not just what they're paid to.
Proof · reports they got fixed
10 Aug
The judgment behind it ↓
And the technical judgment holds up
Evidence31
Alternative22
Assumption33
Tradeoff4
About 2% of engineers on Proof reason across all four. Keep the tradeoffs coming. This is the easy read — an interview catches it too. The character above is the part it can’t.
The arc · they didn’t start here
Early
79
character whys
→
Lately
0
steady
Showed up · 89 days
10 stuck + 11 hard days, logged anyway. Nobody farms honest bad days — that’s why this counts and a streak doesn’t.
A hard day, in their words
an issue within our system where deploys make long-running jobs lose state, there are a couple of solutions that we can try but for that I need to understand and verify how exactly
Read Animesh’s 30 logs ↓sign in to connect with them
Recent logs30
