Welcome back, Arvind

This is your personal interview preparation hub built from your resume — covering every technology, project, and achievement you mentioned. Use the left navigation to read materials, take quizzes, and rehearse your self-introduction.

Questions Reviewed

—

Latest Quiz Score

Study Days

Your Resume Snapshot (corrected)

Role: Full-Stack Software Engineer • 5+ years
Current: Software Engineer @ NeoSOFT Technologies (Client: 1Finance) • Jan 2023–Present
Position: Team contributor on the 1Finance website Go/Fiber platform
Stack: Golang/GoFiber, Node.js/NestJS, PostgreSQL, Redis, Docker, Next.js, React
Modules you own end-to-end: Magazine, In-the-News V3, HR Conclave admin (V1 + V2 speaker cards), Master Class events & OTP enrollment, QFA, App Reviews + MoneySigns, App FAQ, Header Search, Ticker, Sitemap generators, CSV bulk imports
Latest system (contributor, not architect): India HR Conclave — a gated HR community platform (hrbackend/v2). Members are approved, not open-signup; they profile, blog, ask and answer questions, request workshops and refer peers. Its engagement layer is a points feature where 1 point = ₹1, redeemable for vouchers — built on Go microservices behind a Fiber v3 gateway, Postgres, Kafka and a Next.js 16 admin dashboard

Your Real Patterns (from the codebase)

When asked "walk me through your architecture", lean on these patterns you actually work with daily:

Fiber router groups for namespacing — feature roots, nested admin groups, V1 and V3 coexistence during migrations
CheckUserDataBase middleware — DB-backed JWT with per-endpoint RBAC permission strings (e.g. ManageInTheNews, ManageHrConclaveSpeakers)
StaticTokenAuth middleware — for internal endpoints like encryption backfill scripts and FAQ public access
Body validator middleware per resource — ValidateInNewsBody, ValidateHrConclaveSpeakerBody, etc.
Encryption backfill scripts — gated by static token, idempotently re-encrypt legacy plaintext rows (you did this for Magazine and HR Conclave)

On the HR community platform the patterns go a level deeper. You contributed there rather than designing it, so present these as "how that system handles it, and why I think that's right":

One write path for money — ledger.Apply locks the member row, checks a deterministic idempotency key before the sufficiency check, and applies a relative balance + ? update
Append-only by trigger — the database rejects UPDATE/DELETE on the ledger; corrections are reversing rows
Transactional outbox — the event row is written in the same transaction as the state change; a relay publishes it to Kafka
The event is a trigger, never the authority — consumers re-read the source row before acting
Ambiguity is a state — pending_reconciliation when a provider times out, instead of guessing refund or confirm

The one-line reframe that makes this land

The 1Finance modules show breadth — CRUD, RBAC, encryption backfills, migrations done safely, and they are genuinely yours. The HR community platform shows depth, and the way to introduce it is not "a rewards platform":

"It's a gated community for HR professionals, and its growth feature pays out real money — a point is a rupee — so a mechanic that looks like gamification is built with financial-grade discipline."

That sentence answers the "isn't this over-engineered?" objection before it is asked, and it opens onto everything worth discussing: idempotency, at-least-once delivery with idempotent effects, saga compensation, and what to do when a provider's answer is ambiguous.

Keep the scope honest — you contributed to that system, you did not architect it. Lead with the two or three pieces that are actually yours, then the systems observations land as understanding rather than borrowed credit.

Open the HR Community Platform deep dive →

How to use this hub

Start with Self-Introduction — rehearse the 60s/90s/2-min scripts until they feel natural.
Read materials topic-by-topic — each section has key concepts, examples, and gotchas.
Test yourself — take the quizzes; the system tracks your score and weak areas.
Practice the question bank — 330+ Q&As filterable by topic and difficulty.
Rehearse STAR stories — your behavioral answers based on real projects.

Recommended 14-Day Sprint

If your interview is within 2 weeks, follow this:

Days	Focus	Outcome
1–2	Self-intro + Golang deep dive	Confident intro, Go fundamentals locked
3–4	PostgreSQL + Redis + Query Optimization	Database mastery, latency stories ready
5–6	Microservices + REST + JWT + Docker	API design fluency
7–8	Next.js + React + Frontend system design	Frontend confidence
9–10	System Design + Fintech scenarios	Whiteboard scenarios practiced
11–12	Behavioral + STAR + mock interviews	Stories polished
13–14	HR community platform deep dive + take all quizzes	Senior-signal system story locked, weak areas reviewed