Interview Q&A

Short answer: Use HTTPS Implement authentication & authorization (e.g., JWT) Sanitize inputs to prevent XSS/SQLi Rate-limit requests Use helmet for HTTP headers: const helmet = require('helmet'); app.use(helmet());

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use tools like Apache JMeter, k6, or Artillery to simulate many users and measure performance. Ecosystem & Tools

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: You can use validation libraries to ensure incoming data is valid. 📌 Example with express-validator: npm install express-validator const { body, validationResult } = require('express-validator'); app.post('/users', body('email').isEmail(), (req, res) => { const errors = validationResult(req);

Example code

if (!errors.isEmpty()) return res.status(400).json({ errors: errors.array() }); res.send('User created'); });

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Node Version Manager lets you install and switch between Node.js versions easily.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: pp.post('/users', body('email').isEmail(), (req, res) => { const errors = validationResult(req); if (!errors.isEmpty()) return res.status(400).json({ errors: errors.array() }); res.send('User created'); }); pp.post('/users', body('email').isEmail(), (req, res) => { const errors = validationResult(req); if (!errors.isEmpty())… return res.status(400).json({…… errors: errors.array() }); res.send('User created'); }); pp.

Explain a bit more

post('/users', body('email').isEmail(), (req, res) => { const errors = validationResult(req); if (!errors.isEmpty()) return res.status(400).json({ errors: errors.array() }); res.send('User created'); }); pp.post('/users', body('email').isEmail(), (req, res) => { const errors = validationResult(req); if (!errors.isEmpty())… return res.status(400).json({ errors: errors.array() }); res.send('User created'); });

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: express-validator Joi yup zod All support schema-based and custom validations.

Real-world example (ShopNest)

Express middleware authenticates JWT, then the /orders route handler creates the order.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Uses semantic versioning: MAJOR.MINOR.PATCH. New major versions can include breaking changes.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: ll support schema-based and custom validations.

Real-world example (ShopNest)

Express middleware authenticates JWT, then the /orders route handler creates the order.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Typical options include: JWT tokens OAuth API keys Sessions (less common for APIs) 📌 Usually, the client includes a token in the Authorization header: Authorization: Bearer <token> The server verifies the token on every request.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: npm: Default Node package manager. yarn: Faster installs, better caching. pnpm: Efficient disk usage by linking packages.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: uthorization: Bearer <token> The server verifies the token on every request.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Babel: Transpiles modern JS to compatible versions. TypeScript: Adds static typing and compiles to JS.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: JWT (JSON Web Token) is a compact, URL-safe token used for securely transmitting information. Consists of Header, Payload, and Signature Used to verify user identity and permissions 📌 Generate: const jwt = require('jsonwebtoken'); const token = jwt.sign({ id: user.id }, 'secret', { expiresIn: '1h' }); 📌 Verify: jwt.verify(token, 'secret');

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use the multer middleware: npm install multer 📌 Example: const multer = require('multer'); const upload = multer({ dest: 'uploads/' }); app.post('/upload', upload.single('file'), (req, res) => { res.send('File uploaded'); });

Example code

Use the multer middleware: npm install multer 📌 Example: const multer = require('multer');
const upload = multer({ dest: 'uploads/' }); app.post('/upload', upload.single('file'), (req, res) => { res.send('File uploaded'); });

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: pp.post('/upload', upload.single('file'), (req, res) => { res.send('File uploaded'); }); pp.post('/upload', upload.single('file'), (req, res) => { res.send('File uploaded'); }); pp.post('/upload', upload.single('file'), (req, res) => { res.send('File uploaded'); }); pp.post('/upload', upload.single('file'), (req, res) => { res.send('File uploaded'); });

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use testing frameworks: Jest or Mocha for unit tests Supertest for HTTP API testing 📌 Example with Supertest: const request = require('supertest'); request(app) .get('/api/users') .expect(200) .then(res => { console.log(res.body); });

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Rate limiting prevents abuse by limiting the number of requests a user can make in a given time. 📌 Use express-rate-limit: npm install express-rate-limit const rateLimit = require('express-rate-limit'); const limiter = rateLimit({ windowMs: 15 * 60 * 1000, max: 100 // limit per IP }); app.use(limiter);

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use the morgan middleware: npm install morgan const morgan = require('morgan'); app.use(morgan('dev')); Logs every request with method, status, time, etc.

Example code

Use the morgan middleware: npm install morgan const morgan = require('morgan'); app.use(morgan('dev')); Logs every request with method, status, time, etc.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: pp.use(morgan('dev')); Logs every request with method, status, time, etc. pp.use(morgan('dev')); Logs every request with method, status, time, etc. pp.use(morgan('dev')); Logs every request with method, status, time, etc. pp.use(morgan('dev')); Logs every request with method, status, time, etc.

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Use plural nouns in endpoints (/users, not /user) Use proper HTTP methods Send meaningful status codes Keep URLs simple and consistent Use pagination for large data Protect with authentication/authorization Use versioning (/api/v1/...) Validate and sanitize all inputs NPM and module-related Node.js interview questions

Real-world example (ShopNest)

A ShopNest BFF in Node.js aggregates catalog and price APIs for the React storefront.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Negotiate before you resign, not after. Your leverage is a clean handover plan plus a new employer willing to wait—or partially buy out the notice. Most Indian IT firms (TCS, Infosys, Wipro) will consider 60→45 or 90→60 days when the project risk is low and your manager sponsors the request.

Why this matters in Notice Period

A 90-day clause is common for senior roles and service companies. HR cannot usually change policy alone; your reporting manager’s sign-off matters more than an emotional appeal.

Step-by-step approach

1. Read your appointment letter: notice period, garden leave, PTO adjustment, and buyout clause.
2. Get your new offer letter with a realistic joining date (add 2-week buffer beyond expected release).
3. Draft a 1-page transition plan: open tickets, KT owners, release calendar, and critical client calls.
4. Meet your manager privately first—ask what minimum handover they need, not “please waive everything.”
5. Email HR with manager CC: requested last working day, transition summary, and willingness for partial buyout if needed.
6. Confirm release date in writing before telling the new company your final join date.

Real-world example

Rahul, a 5 YOE .NET developer at Infosys, received a Flipkart offer needing join in 55 days while his notice was 90. He listed 3 modules he owned, proposed 4 KT sessions, and offered to finish a sprint-critical API before exit. His manager agreed to sponsor 60-day release; HR approved because the account lead signed off. Rahul paid no buyout and joined on time.

What to say / email template

Subject: Request for notice period discussion — Rahul Sharma (Emp ID: 12345)

Dear [Manager Name],

Thank you for the opportunities on [Project/Account]. I have accepted an offer elsewhere and will submit formal resignation shortly. My contractual notice is 90 days; the new employer has requested joining by [date].

I prepared a transition plan (attached) covering KT, open defects, and release ownership. I am requesting support for an early release of [X days / target LWD: DD-MMM-YYYY], subject to HR policy.

I am committed to a professional handover and will remain fully available until my last working day.

Regards,
Rahul

Numbers & benchmarks

• Service companies: 90 days common for 3–8 YOE; product startups often expect 30–45 days.
• Realistic reduction: 90→60 or 90→45 days when KT is documented—not 90→15 without buyout.
• Buyout cost (if allowed): often 1–3 months basic salary—negotiate with new employer as joining bonus.

Mistakes to avoid

• Resigning first, then begging for reduction—always align with manager before HR.
• Bad-mouthing the company or threatening to leave immediately.
• Promising a join date to the new employer before written release approval.
• Skipping KT documentation—managers reject early release when bus factor is you.

The sentence that works: “I want to protect the account and leave on good terms—here is how I will hand over in X weeks.”

Short answer: Reduction means proving the business can run without you in fewer days. Combine manager sponsorship, documented KT, and optionally using accumulated leave or buyout. Target a specific last working day (LWD), not a vague “as soon as possible.”

Step-by-step approach

1. Calculate calendar days: 90 working days ≠ 90 calendar days—check if weekends/holidays count in your policy.
2. Identify low-risk period: post-release, between projects, or after major go-live.
3. Offer concrete KT: recordings, runbooks, shadow sessions, and access revocation checklist.
4. Ask HR about leave adjustment (paid leave during notice) vs buyout—policies differ by company.
5. Escalate politely if HR stalls: ask for policy reference and approval workflow in writing.
6. Keep performing normally—performance drops are a common reason managers block early release.

Real-world example

Ananya, QA lead at TCS with 90-day notice, wanted to join a Bangalore product startup in 70 days. She created Confluence pages for 40 test cases, paired a junior QA for 2 weeks, and proposed LWD after the UAT sign-off. Account manager agreed; HR reduced notice to 75 days and allowed 5 days of earned leave in the notice window.

Numbers & benchmarks

• Typical achievable reduction with good KT: 15–30 days off a 90-day notice.
• Leave during notice: many firms cap how many PTO days offset the notice period.

Mistakes to avoid

• Assuming all companies treat notice the same—MNC captives vs Indian service vs product differ widely.
• Going straight to HR bypassing your manager (manager can block silently).
• Using sick leave patterns to cut notice—can trigger compliance review.
• Sharing confidential client data in KT docs stored on personal drives.

If reduction is denied, ask: “What specific handover milestones would make a 60-day release acceptable?”

Short answer: Early release is a business decision, not a favor. You need manager + HR + sometimes client approval. Make it easy to say yes: low transition risk, no open escalations, and a replacement or clear backlog plan.

Step-by-step approach

1. Check if your project is in a critical phase—avoid requesting release during go-live week.
2. Identify who must approve: manager, HRBP, delivery head, sometimes client POC.
3. Submit resignation with professional tone; attach transition timeline.
4. Volunteer for overlap with your replacement or extended support calls (within policy).
5. If denied, ask for interim date review after milestone X is delivered.
6. Document all approvals—Relieving letter and experience letter dates must match LWD.

Real-world example

Vikram, DevOps engineer at Wipro, was on a 90-day notice. His pipeline work was automated; on-call was shared. He trained two teammates on Terraform modules and showed 30 days of clean incident history. Delivery manager approved 45-day release; client had no objection because KT was recorded.

What to say / email template

Talking point to manager:
"Our release is stable and documented. I propose LWD [date] after these 3 KT sessions. I can stay reachable on email for 2 weeks post-exit for critical questions if policy allows."

Mistakes to avoid

• Disengaging after resignation (“quiet quitting”)—guarantees denial.
• Demanding early release citing only personal reasons without handover plan.
• Accepting verbal OK without HR portal/email confirmation.
• Starting full-time work at the new company while still on old payroll—legal and tax risk.

Offer a 30-minute weekly KT call during part of your notice if the team is short-staffed—often unlocks flexibility.

Short answer: Sometimes yes—if your employment contract or HR policy allows notice buyout. You (or your new employer) pay compensation for unserved notice days, usually basic salary equivalent. Not all companies permit it; captives and banks often do not.

Step-by-step approach

1. Search offer letter for “notice buyout,” “payment in lieu of notice,” or “shortfall recovery.”
2. Ask HR explicitly: “Is buyout allowed for my band and account?”
3. Get the formula: basic only vs CTC vs fixed components—amounts vary hugely.
4. Negotiate with new employer: joining bonus or relocation can cover buyout cost.
5. Pay only after written approval and final settlement calculation from HR.
6. Keep receipts and F&F settlement sheet for tax and future employment verification.

Real-world example

Priya’s product company required 30-day join; her MNC had 60-day notice with buyout at 1 month basic (₹85,000). Flipkart added ₹1L joining bonus conditioned on start date. Priya paid buyout, joined on time, and claimed reimbursement per offer letter clause.

Numbers & benchmarks

• Buyout range: 0.5–3 months of basic/common salary depending on employer.
• Some firms allow new employer to pay directly to old HR—ask both sides.
• Recovery on absconding is often higher than voluntary buyout—never compare them equally.

Mistakes to avoid

• Assuming buyout is automatic—it is often discretionary.
• Paying buyout without formal HR letter (scams/fake HR requests—verify domain).
• Not clarifying if variable pay / bonus is forfeited on early exit.
• Skipping tax treatment discussion on buyout and F&F components.

Phrase to new employer: “My notice buyout is approximately ₹X—can we align joining bonus or one-time payment to offset this?”

Short answer: Email HR after your manager agrees in principle. Be factual: current notice, requested LWD, business justification (handover complete), and attach transition plan. HR responds to process and risk, not urgency alone.

Step-by-step approach

1. Never cold-email HR without manager alignment—get verbal or Teams approval first.
2. Use official HR ticket/portal if your company has one (TCS/Infosys often require this).
3. Include: employee ID, resignation date, contractual notice, requested LWD, manager name.
4. Attach KT checklist and confirmation that access/assets will be returned on LWD.
5. Ask for response timeline: “Kindly confirm by [date] so I can coordinate with the new employer.”
6. If rejected, request written reason citing policy clause for future reference.

Real-world example

Rahul’s manager agreed on Teams to support 60-day release. Rahul opened an HR ticket with screenshot of project KT completion and manager’s email. HR approved in 3 business days and updated LWD in the separation portal—avoiding confusion at full & final settlement.

What to say / email template

Dear HR Team,

I submitted resignation on [date]. Contractual notice period: 90 days (LWD [date]).

With manager [Name]’s support, I request LWD [new date] based on completed handover (KT doc attached, manager approval email attached).

Please confirm approval or advise additional steps.

Employee ID: ___
Regards, ___

Mistakes to avoid

• Emotional language or comparing yourself to others who “got 15 days.”
• Copying only HR without manager—request gets stuck or rejected.
• Missing attachments—HR will delay for “incomplete submission.”
• Calling HR daily—polite follow-up every 3–5 business days is enough.

Subject line that works: “Notice period reduction request — [Name] — [Emp ID] — Manager approved”