For the people who hire
Stop reading résumés.
Read the work.
Engineers here write what they built, what they decided and where they got stuck — every day. You read that before you know their name.
In the order a buyer actually reads.
Not ours — theirs. A founder who hires from here gave us the order, word for word: the working outcome first, the code next, the reasoning third. A log written for a role can be performed. A running thing cannot.
A Spring Boot-based hotel booking system designed to handle reservations and prevent double bookings.
“Today I worked on LLM streaming with LangGraph and Streamlit. I explored how chatbot.stream() sends the LLM response step by step and how stream_mode="messages" provides message chunks. I also used st.write_stream() to display the response in real time. Still building and improving every day”
Written 18 Sept 2026 · unedited
This is for tracking my job hunt
“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.”
Written 18 Sept 2026 · unedited
for people who easily lose track of time.
“overcommunicate if you must, but ensure both the parties have clear understanding of the scope before touching the project.”
Written 18 Sept 2026 · unedited
Four steps. No sales call.
You get access — free, and in under a minute.
You read 254 engineers with their names still hidden.
You post a role, and people raise a hand in writing.
You keep the read — the record stays, whether you hire now or in six months.
Read the pool tonight.
Free, and nothing here charges you. It is a hiring surface, so we ask for a work email — RK reads the list. Names stay hidden until you flag someone and RK makes the introduction by hand. Nobody is scored, ranked or sorted for you.