Skip to content
View hemv-857's full-sized avatar
🎯
Focusing
🎯
Focusing

Highlights

  • Pro

Block or report hemv-857

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
hemv-857/README.md

Hi, I'm Hemang Varshney 👋

Software developer working across quant finance, real-time systems, and AI tooling.
I write code; occasionally it works.

📈 Live: my chances of getting hired

Hire probability 3.51% (analyst rating: SELL). 135 commits in 4 sessions · 34/day · never missed a day. Streak: 4.

4 sessions · 100% hit rate · best streak 4 · 1 exact / 1 near / 2 beat / 0 miss

📊 2026-09 earnings report: 1 session, 0% hit rate, probability -0.2pts. The alpha is imaginary but the vibes are quarterly-confirmed.

Date (IST) Forecast Shipped Result Δ pts Hire probability
2026-10-04 (today) 11–43 ⏳ Market open
2026-10-03 11–43 38 ✅ Exact hit +0.88 3.51%
2026-10-02 4–42 43 🚀 Beat +1.01 2.63%
2026-10-01 5–42 4 🟢 Near hit +0.10 1.62%
2026-09-30 5–42 50 🚀 Beat +1.10 1.52%
How does this work? (a.k.a. why is this in my README)
  • Every day at 00:05 IST a GitHub Action forecasts a range for the day: the 7 day trailing window, trimmed — the smallest and largest are dropped, so one monster day can’t turn every forecast into a shrug. It lands about half the time.
  • Counts are the commits that still exist on my repos' default branches, so git log agrees with me. GitHub's contribution graph never retracts a commit — rebased and amended work stays counted forever, and it claimed 74 for a day with 38 commits in it.
  • The next midnight it fetches my real commit count and settles the trade.
  • Points follow the work: 0 for a day with no commits, up to 1 for matching the top of the range, and up to 1.5 for beating it. Streaks add a small bonus.
  • Landing inside the range is a hit, 1 under is a near miss, further under is -0.25, and no commits on a day that expected work is -0.5.
  • Shipping more is never punished. Beating the top of the range is the best possible day, and the score keeps climbing with the overshoot.
  • Market manipulation means one thing only: 10+ commits within 60 minutes in this profile repo — the only way to game the contribution graph. Overachieving a low forecast across real repos is not a crime. Penalty: -1.5 pts.
  • Visitors: 👍/👎 on today's voting issue to predict whether the bot hits. No prize, just bragging rights.
  • Monthly: on the 1st, an earnings report summarises the previous month.
  • Probability is 100% fiction. The 100% real part: I actually ship code, and I'm actually looking for a job.

🛠 Stack

Languages

Python TypeScript Rust

Frameworks & Tools

FastAPI Next.js React Prisma Tailwind CSS D3.js Redis PostgreSQL Docker

AI & Data

LLM Qdrant MCP WebSocket

Domains

Quant Finance Fintech Security

📫 Reach me

Pinned Loading

  1. rzp-recovery-agent rzp-recovery-agent Public

    Recovers failed Razorpay payments using randomized control groups to measure true incremental lift

    Python

  2. Codeinsight Codeinsight Public

    Codebase Q&A and architecture visualization tool — ask questions about any repo in plain English

    Python

  3. cognitive-convergence-detector cognitive-convergence-detector Public

    Tracks when institutional trading signals converge — a marker of crowded positioning and systemic risk

    HTML

  4. mcp-vetter-agent mcp-vetter-agent Public

    AI agent that audits MCP servers for security issues before you connect to them

    TypeScript

  5. ORION ORION Public

    Geopolitical risk dashboard tracking energy supply chains and global conflicts in real time

    TypeScript

  6. rmt-covariance rmt-covariance Public

    Covariance matrix cleaning using Random Matrix Theory vs Ledoit-Wolf, with walk-forward backtests

    Python