Freelancers using LangChain in IndiaFreelancers using LangChain in India
Technical Writer (1.5M+ reads) & Open Source Developer
$10k+
Earned
23x
Hired
56
Followers
Technical Writer (1.5M+ reads) & Open Source Developer
Building Production-Grade AI Agents & RAG Systems
13
Followers
Building Production-Grade AI Agents & RAG Systems
AI Agents & LLM Systems · Ex-Amazon & Microsoft · 10+ Years
5.0
Rating
1
Followers
AI Agents & LLM Systems · Ex-Amazon & Microsoft · 10+ Years
I’m an AI & Machine Learning engineer with expertise in deve
I’m an AI & Machine Learning engineer with expertise in deve
Cover image for What your attention heatmap isn't
What your attention heatmap isn't telling you Everyone's staring at attention heatmaps and calling it "interpretability." Almost nobody's asking whether a single attention map actually tells you what the model used to make its decision. It doesn't. Not on its own. A raw attention map from layer 8 shows you what layer 8 attended to. It says nothing about how that signal got mixed, diluted, or overwritten by every layer before and after it. Attention rollout fixes this — and I built a walkthrough to show why it matters. Here's what makes it more than a "pretty heatmap" demo: Instead of visualizing one layer's attention, I traced how information actually flows through the full transformer stack. → Every layer's attention matrix is extracted, per head, per token → Multi-head attention is averaged, then combined with the residual connection (identity + attention) — this is the step most tutorials skip, and it's the one that actually matters → The combined matrices are matrix-multiplied layer by layer, rolling attention forward from input to output → The result: a single map showing genuine token-to-token influence across the entire network, not just one layer's snapshot The overlay shows you everything: → Per-layer attention vs. rolled-out attention, side by side → Token importance scores overlaid directly on the input text → A comparison view: which tokens raw attention says "matter" vs. which ones rollout says actually matter → Head-level breakdown so you can see which heads specialize vs. which are noise No black box. No "trust me, the model looked here." Just linear algebra, applied honestly across every layer instead of cherry-picking one. Built with PyTorch + HuggingFace Transformers + Matplotlib. Runs on any pretrained transformer, fully offline. ⚠️ Important: attention rollout is an approximation, not ground truth. It assumes attention is the primary information pathway, which ignores MLP layers and can still mislead for very deep models. Treat it as a debugging lens, not proof of causality.
0
26
Design, Build, AI, Automation
$50k+
Earned
17x
Hired
5.0
Rating
61
Followers
Design, Build, AI, Automation
Cover image for DailyCue — AI-Powered Decision Support
DailyCue — AI-Powered Decision Support for Recruitment Teams URL: https://dailycue.tech One-liner Shipped a recruitment SaaS MVP in 3 days — AI that tells recruiters exactly who to call today, and why. Project Overview Most recruitment teams don't have a lead problem. They have a prioritisation problem. CRMs are full, but consultants still rely on gut feel to decide where to focus each day — which means high-value opportunities get buried and revenue stays unpredictable. DailyCue connects to a recruitment CRM and uses AI to surface daily, prioritised actions for each consultant: who to contact, what the context is, and why now. It replaces the daily morning scramble with a clear, data-driven cue. What I Built CRM data ingestion pipeline with normalisation and deduplication AI prompt layer (GPT-4) generating personalised daily action lists per consultant Tiered Stripe billing in GBP with seat-based pricing JobAdder marketplace OAuth integration for one-click CRM connection Serverless architecture on Vercel with Inngest for background job processing Landing page, onboarding flow, and trial signup How I Shipped It Initial version went live in 3 days. I then iterated directly with real recruitment users, refining the AI prompts based on actual usage feedback until the output matched how experienced consultants naturally think about their pipeline. The product continued to evolve through multiple rounds of user testing and positioning pivots. Tech Stack Next.js · Supabase · PostgreSQL · OpenAI API · Stripe · Inngest · Vercel · JobAdder API
1
2
185
Cover image for Converc — Turn Website Visitors
Converc — Turn Website Visitors Into Live Conversations URL: https://converc.com One-liner Built a real-time browser-based calling platform from scratch — MVP live in 5 days. Project Overview Converc solves a problem that costs B2B companies revenue every day: high-intent visitors land on your site, can't get a human immediately, and leave. It embeds a call widget that connects visitors to sales reps in real time — no booking links, no forms, no friction. I architected and built the full product: a Next.js frontend, Supabase backend with Row Level Security, and WebRTC-powered peer-to-peer audio calling that works entirely in the browser with no native app required. The stack was chosen for performance, low latency, and the ability to ship fast without sacrificing production quality. What I Built WebRTC call engine with real-time signalling via Supabase Realtime Embeddable call widget (drop-in script for any website) Agent dashboard with live call status, queue management, and session history Webhook integration layer for CRM and Slack notifications on call events OAuth-based authentication with Google and dev/prod environment separation Supabase RLS policies enforcing strict data isolation between workspaces How I Shipped It The core MVP — widget, signalling, agent dashboard, and working calls — was shipped in 5 days using Cursor with Claude as the AI pair programmer. Post-MVP work covered Google Safe Browsing clearance, Slack App submission, analytics scoping, and hardening the auth and security model for production. Tech Stack Next.js · Supabase · PostgreSQL · WebRTC · Vercel · Tailwind CSS
0
148