Priyadharshini

Full Stack Engineer · writing since 2 Jun
Day 3 of 30Open to roles
Day 18 · public proof
How Priyadharshini thinks
Makes the thinking legible — says clearly what most people can't.
the log that shows it
articulate·curious·decisive
◈ Open to being sharpened
How Priyadharshini think, mapped · lit by their own logs · 5 showing
How you 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 you work · the qualities founders read for
Curious
you ask, not just assert
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones1 earned
Day 10 · Aug 26
The climbYou're moving.
The shape of your 15 entries
beta · being tuned

You're moving.

2 Jun18 Sept
up when you grow · flat when you hold steady · a dip when you go quiet — it’s the shape of your work, not a score.
decided · I decided to plan to…2 Jun18 Sept
Then → now
Then you were No code today weirdly one of….
Now: I decided to plan to write….
Every valley named in your own words. Nobody can fake a climb.
About

Full-stack engineer (TypeScript/React/Node, plus Python/Django and Ruby on Rails) with 4 years at Drylogics, most recently cutting a production LLM pipeline's cost 40% via a benchmarked model swap and flag-gated shadow-mode rollout. Open to backend/full-stack + LLM integration roles.

JavaScriptTypeScriptReactNext.jsNode.jsPythonDjangoPostgresRedisDockerLLMs / GenAI
🎓 M.Sc · Government Arts College · 2022
Mock interviews
16 Sept · Haripriya asked

Had a mock interview today with Hari Priya, which was arranged by Proof founder Radhakrishnan and she is someone with over ten years of experience. Really useful session overall. Started with my self introduction, walked through my background and experience. She gave me feedback on how I framed that, said I could sharpen the approach a bit. Then she moved into scenario questions. Asked me about a tough production issue I'd handled and how I managed it on my own. Also asked about my experience with technical design decisions, the kind of calls I've made in that space. She was clearly trying to map out my strengths and weaknesses. One thing she picked up on, I have a strong math background from my master's degree. She said that's actually a solid differentiator and told me to weave it into my introduction as a real strength, not just a footnote. Beyond that, she gave me some broader advice. Said I should be ready to talk about how I use AI in my day to day workflow, not just as a buzzword but practically, how it speeds up my work and fits into how I build things. Told me to prepare that as its own area before the next round. Overall takeaway, good session. Need to rework my intro to lead with the math strength, and build out a real answer on AI tooling in my workflow.

Nobody is scored in these. What you are reading is what they chose to write about their own hour. Sit one →

Priyadharshini · the character an interview can’t show

15 logs over 16 weeks — read from their own words.

+ Only points up
Character · what an interview can’t reach
Priyadharshini has written 15 logs so far — not enough yet to read a way of working from. The logs themselves are the thing to read.
The judgment behind it ↓
And the technical judgment holds up
Evidence
7
Alternative
8
Assumption
4
Tradeoff
2
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.
Showed up · 13 days
0 stuck + 0 hard days, logged anyway. Nobody farms honest bad days — that’s why this counts and a streak doesn’t.
Read Priyadharshini’s logs →sign in to connect with them
Recent logs15
P
Full Stack Engineer
Free write18 Sept
P
Full Stack Engineer
Free write10 Sept
P
Full Stack Engineer
Decided7 Sept
P
Full Stack Engineer
P
Full Stack Engineer
P
Full Stack Engineer
P
Full Stack Engineer
Built31 Aug
◈ Open to sharpen
P
Full Stack Engineer
P
Full Stack Engineer
Built25 Aug
P
Full Stack Engineer
P
Full Stack Engineer
Built22 Aug
P
Full Stack Engineer
Learned17 Aug
P
Full Stack Engineer
Learned17 Aug
P
Full Stack Engineer
Learned17 Aug
Free write2 Jun 2026
No code today weirdly one of my better days.Spent it all reading and figuring things out. Four messy things this morning, four clear plans by evening. Best part: something I thought was a whole build turned out to be two lines — the fieldalready existed, I just wasn't searching the right name. Classic.Also made myself not jump into coding before the requirements were confirmed. Felt slow, but right.Quiet day. But the unknowns are gone. Tomorrow I build.