Engineer
Product engineering at an early stage startup · Bangalore · writing since 21 May
Day 37 · public proof
How Engineer thinks
Decides and owns the call — moves before being told.
↳the log that shows itarticulate·curious·decisive
⤳ Sharpens others · 2
How Engineer thinks, mapped · lit by their own logs · 7 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
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
JavaScriptRubyPostgresMySQLAWSReact
Engineer · the character an interview can’t show
50 logs over 6 weeks — read from their own words.
Shown so far: Honest when it's not working.
Character · what an interview can’t reach
✓Shown
Honest when it's not working
3 stuck and 10 hard days, logged plainly instead of hidden.
Proof · from their own logs
25 May
The judgment behind it ↓
And the technical judgment holds up
Evidence4
Alternative5
Assumption3
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
149
character whys
→
Lately
133
steady
Showed up · 37 days
3 stuck + 10 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 Engineer’s 30 logs ↓sign in to connect with them
Their logs30
▶ Played as a game · Pick & Defend
Theory let's you know what's possible, but learning only happens when you experience the failure modes yourself · I'll know I was right in 2 weeks if: I come out with a project and learnings that will help me make better decisions this project and others
▶ Played as a game · Pick & Defend
For me atleast, since I've worked with React before, I'd pick it cuz I can push more features while not going down deep rabbit holes, as much fun as they are · I'll know I was right in 2 weeks if: I have the product I had in my head on my phone
Built22 Jun 2026
I built an improved way to filter Coexistence and Cloud API number WhatsApp templates
Quiet day21 Jun 2026
—
Learned20 Jun 2026
I learned it's nice to love your customers, but it's not required from Seth Godin's blog titled "Love your customers"
Built19 Jun 2026
I built a way to make it easier to link a WhatsApp Business number using 1 click connect
Thinking18 Jun 2026
I'm thinking about a pull request I should have split into smaller PRs because it would have made it easier to make progress
it would have made it easier to make progress
Built17 Jun 2026
I built a fix for a script that we (me or my colleagues) run when we migrate WhatsApp templates associated with a particular phone number - it was an unhandled error that might have confused any new person going through the runbook
Figuring out17 Jun 2026
I want to figure out how to build taste - caring for the end user can take you far but being able to take a call on the UI you present to the user with confidence is something I still can't do
Built16 Jun 2026
I built a way for our customer to be able to embed our web widget on multiple domains instead of just one and give them the ability to manage the allowed domains from our in-app developers screen
Learned15 Jun 2026
I learned Data science without a data foundation is hopeless from Ajay Gore's blog titled "What's hopeless in product engineering"
Quiet day14 Jun 2026
Scrolled hackernews and got resume reviewed
Quiet day13 Jun 2026
Recuperated and reflected on the week
Flagged12 Jun 2026
I flagged a failing deployment because it blocked a feature delivery for a customer
it blocked a feature delivery for a customer
Built11 Jun 2026
I built an update to our embeddable widget to simplify navigation options and shipped it to npm
Flagged10 Jun 2026
a broken test on CI that got merged because it would break existing Shopify MCP integration
it would break existing Shopify MCP integration
Built9 Jun 2026
an update to the model, both my mental model and the data model, for considering a customer service window (more simply a conversation window) opened
Flagged8 Jun 2026
a possibly incorrect assumption because it would have changed the scope of tasks in our sprint
it would have changed the scope of tasks in our sprint
Thinking7 Jun 2026
We often think about how others might be thinking or feeling about us when we need to reach out - that creates an invisible wall.
Learning to unlearn creating the wall in the 1st place can take some time.
Free write6 Jun 2026
Carving out time for yourself can make you feel guilty but it's something you have to do to continue operating at a decent level
Learned5 Jun 2026
You get better clients by becoming the kind of freelancer that better clients want to hire from Seth Godin's blob titled "Freelancer empathy"
Built4 Jun 2026
a scaffold for WhatsApp Business app users to be able to connect their phone to the platform - the 1st cut that got shipped was obviously not perfect but the basics were there
Decided3 Jun 2026
not to support string "True" as a value for a key in the payload in one of our APIs over proper JSON true because that's sloppy API design that I don't want me or future colleagues to support.
that's sloppy API design that I don't want me or future colleagues to support.
Built2 Jun 2026
a new editor for WhatsApp template body for the product and shipped it - nothing interesting, but did give some time to polish the mark-up styling, which felt nice. Hopefully adds enough value for the users - not the styling bit but the updated editing UX.
Flagged1 Jun 2026
the regressions we're introducing and follow up fix PRs we're deploying as part of our moving fast because I'd like us to move fast and be correct rather than moving fast and breaking things.
I'd like us to move fast and be correct rather than moving fast and breaking things.
Want a page like this?
Write what you tried, a few lines a day. People who’d hire you read it.
Start your Proof