Early, and documenting it.

The three projects are real. The details are not filled in yet: the stacks, links, metrics, certificates, and LeetCode numbers are placeholders, and they are marked as such. Nothing on this site claims a user count, a latency, a test count, or a certificate that has not been added.

That is deliberate. A portfolio for someone at the start of their career has a credibility problem, and the fastest way to lose an interview is to invent a number that falls apart under one follow-up question. The structure is here; the evidence goes in as it becomes real.

Why the receipts

Every claim should have a source. If the page says “Postgres”, the schema should be one click away. If it says “tested”, the test should be one click away. Right now the ledger links to placeholders, which is honest about where the work is.

The same rule applies to the case studies: the Outcome and Process tabs are there, but the paragraphs are prompts until the real story is written. No adjectives, no invented users, no “passionate”.

Certifications and practice

Certifications and LeetCode are part of the plan, but the names, issuers, years, and numbers are not on the site yet. The home page has three certificate slots and one LeetCode card; both are marked as pending. Add the real ones, or delete the slots.

What I'm looking for

A junior full-stack role on a team with code review, real users, and someone who will tell me when my schema is wrong. I am in West Bengal, open to remote, and available immediately. I would rather own a small feature end to end than watch a large one from the sidelines.

Colophon

Next.js with MDX case studies and hand-written CSS, exported as static files and deployed on Cloudflare Pages. Green on black by default, with a light theme that is a real token set. Newsreader for display, Inter for text, JetBrains Mono for the ledger.

The only live data on the site is the visitor-weather demo in the Mobile Weather case study: with permission, the browser shares coordinates with Open-Meteo and the forecast is fetched in the tab. There is no analytics script, no cookie banner, and no stored visitor data.