Radhakrishnan
Senior Software Engineer · Bengaluru · writing since 21 Apr
Open to roles
6 months on Proof
■ weeks with logs■ quiet week
132 logs · 26 say why
How Radhakrishnan thinks
Asks the question others skipped — then owns the answer, and can say why.
↳the log that shows itarticulate·curious·decisive
◈ Open to being sharpened⤳ Sharpens others · 8
How Radhakrishnan thinks, mapped · lit by their own logs · 6 showing
How they reason · the four moves
Alternative
name the option you didn't take
Assumption
surface what you're taking on faith
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
You update
change your mind on evidence
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones3 earned
Day 30 · Jun 25Day 20 · Jun 10Day 10 · May 09
About
JavaScriptReactNode.jsReact NativeiOSData engineeringUI / designC/C++AndroidDevOpsRisk AssessmentStakeholder ManagementAnalyticsJiraConfluenceFraud AnalysisRoot Cause AnalysisTest Driven Development
🎓 M.Sc software engineering · KCET · 2009
Careerself-reported
Jul 2021 – Present
Senior Software Engineer
H&M
Aug 2017 – May 2021
Software Engineering Lead
Foodhub
Jul 2016 – Jul 2017
Senior Software Engineer
Myntra
Sep 2015 – Jul 2016
Lead iOS Developer
Toovia
Nov 2012 – Aug 2015
Senior Software Developer
Ravy Technologies
Jan 2009 – Nov 2012
Senior Software Engineer
Aspire Systems
Mock interviews
Radhakrishnan has asked the questions 11 times.
27 Oct · Safal asked
No public reading from this one.
6 Oct · prachi asked
No public reading from this one.
29 Sept · Safal asked
No public reading from this one.
Nobody is scored in these. What you are reading is what they chose to write about their own hour. Sit one →
Radhakrishnan · the character an interview can’t show
132 logs over 29 weeks — read from their own words.
Shown so far: Honest when it's not working, Adjusts and Makes the tools better.
Character · what an interview can’t reach
✓Shown
Honest when it's not working
11 stuck and 6 hard days, logged plainly instead of hidden.
Proof · from their own logs
22 Apr
✓Shown
Adjusts — updates when the evidence changes
Changed course 2 times in the open, with the reason written in — not dug in.
Proof · from their own logs
10 May
✓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
20 Aug
The judgment behind it ↓
And the technical judgment holds up
Evidence1
Alternative12
Assumption4
Tradeoff0
The arc · they didn’t start here
Early
74
character whys
→
Lately
66
steady
Showed up · 70 days
11 stuck + 6 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
engaging the college students
Read Radhakrishnan’s 30 logs ↓sign in to connect with them
Their logs30
Whybecause it will break the trust on you,
Whybecause it is easy to do the changed
Whyit forces you to name the real drivers behind your decision instead of giving a vague or generic reason.
Whybecause the world is keeps changing because it is made up of factors
Whybecause most companies especially companies value people with whom we can collaborate
Whybecause new composer captures WHY and why is critical to get a jib
◈ Open to sharpen
Want a page like this?
Write what you tried, a few lines a day. People who’d hire you read it.
Start your Proof