Self-Introduction & Intro Video

Opening (15s): "Hi, I'm Arvind Sharma — full-stack engineer, five-plus years, currently at 1Finance through NeoSOFT. Mostly Go on the backend and Next.js on the front."

What I own (30s): "The 1Finance website runs on a Go/Fiber platform with around thirty namespaces. I'm a team contributor, and several modules are mine end-to-end — Magazine with its CSV export and encryption backfill, the In-the-News V3 admin pipeline, HR Conclave, Master Class with OTP enrollment, and QFA. I also handle the sitemap generators and the CSV bulk imports. Magazine is the one I'd point at — registrations, CSV export, and a one-time backfill that re-encrypted legacy plaintext rows, written to be idempotent so a re-run was safe."

Where I've gone deeper (35s): "More recently I've been contributing to India HR Conclave — a gated community for HR professionals, where members are approved rather than just signing up, and they blog, answer each other's questions and refer peers in. Engagement runs on a points feature, and points are literally money — a rupee each, redeemable for vouchers. I didn't design it, but it changed how I think about correctness, because a growth feature that pays real money is a fraud surface. Balances are a cache over an append-only ledger, every movement carries a deterministic idempotency key, and credits are applied by an event consumer — so an approval and the money moving fail independently."

How I work (20s): "Day to day the patterns are consistent — Fiber router groups per feature, a DB-backed JWT middleware with per-endpoint permission strings, static-token auth for internal endpoints, and running two API versions side by side during a migration. That's how the HR Conclave V2 speaker cards shipped while V1 still served the live event site."

Before this (15s): "WooCommerce platforms with payment gateway integration at Thinkbar, and WordPress sites at Visualytes — where I worked directly with clients and learned to turn vague asks into shipped features."

What I want next (10s): "A role with deeper architectural ownership, Go-native engineering, and enough Next.js scope to keep growing on the frontend."

Use the 60s version. Skip deep tech — years of experience, current role, motivation for switching, one or two ownership highlights. Describe the community platform in plain product language ("a private network for HR professionals, with a rewards feature that pays out vouchers") rather than naming Kafka or ledgers; a recruiter is screening for fit and clarity, not architecture.

Use the 90s version. Lead with modules you own — Magazine's encryption backfill and the In-the-News V3 pipeline are the cleanest ownership stories you have. Bring the HR community platform in as where your systems thinking grew, explicitly as a contributor. EMs are calibrating scope of ownership, and overstating it is the fastest way to fail that calibration.

Use the 2-minute version. This is the audience for "a growth feature whose currency is real money is a fraud surface" — then idempotency, append-only ledgers, and why credits happen off the request path. Frame it as "here is how the system I work in handles this, and here is why I think that's right," which shows judgment without claiming the design.

Lead with product impact and shipping speed. Mention working directly with clients at Visualytes. Emphasise that you own features end-to-end across the stack — smaller companies are buying breadth and autonomy more than depth in any one layer.

Use the 60–90s script. Don't recite your resume top-to-bottom — give the module-ownership highlight reel and stop. Silence after 60 seconds is fine; they will ask.

Reverse chronological. Spend 70% on the current role (1Finance through NeoSOFT). Group earlier roles briefly. Be precise about scope: "I'm a team contributor — here's what I personally own," and separately, "here's a system I contribute to."

"I've grown a lot at 1Finance — from writing endpoints to owning whole modules. I'm looking for deeper architectural ownership and a Go-native engineering culture, ideally with stronger Next.js scope so I keep growing on the frontend too." Never badmouth your current employer.

Pick something you personally own, because this question always ends in a depth probe: Magazine's idempotent encryption backfill, the In-the-News V3 admin pipeline, or HR Conclave V2 speaker cards shipped alongside V1 without breaking the live site. Save the HR community platform for "what's the most interesting system you've worked in" — a different question, and one you can answer honestly as a contributor.