Priyadharshini

Full Stack Engineer · writing since 2 Jun
Day 27 of 30Open to roles
Day 18 · public proof
Their logs15
P
PriyadharshiniFull Stack EngineerFree write · 18 Sept
P
PriyadharshiniFull Stack EngineerFree write · 10 Sept
P
PriyadharshiniFull Stack EngineerDecided · 7 Sept
P
PriyadharshiniFull Stack EngineerFree write · 5 Sept
P
PriyadharshiniFull Stack EngineerFree write · 4 Sept
P
PriyadharshiniFull Stack EngineerFree write · 2 Sept
P
PriyadharshiniFull Stack EngineerBuilt · 31 Aug
◈ Open to sharpen
P
PriyadharshiniFull Stack EngineerFree write · 29 Aug
P
PriyadharshiniFull Stack EngineerBuilt · 25 Aug
P
PriyadharshiniFull Stack EngineerFree write · 23 Aug
P
PriyadharshiniFull Stack EngineerBuilt · 22 Aug
P
PriyadharshiniFull Stack EngineerLearned · 17 Aug
P
PriyadharshiniFull Stack EngineerLearned · 17 Aug
P
PriyadharshiniFull Stack EngineerLearned · 17 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.
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 thinks, mapped · lit by their own logs · 5 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
Showing — it’s in their logs; tap to see them allno %, no rank — evidence, not a score.
Milestones1 earned
Day 10 · Aug 26
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 →

Want a page like this?
Write what you tried, a few lines a day. People who’d hire you read it.
Start your Proof