Resume Tips ⭐
- 1 page (senior 2 max)
- Quantify impact (reduced latency 40%, $100K saved)
- Action verbs (Built, Led, Optimized)
- Tailor to JD (keyword match)
- PDF, ATS-friendly (no images for text)
- GitHub + LinkedIn + portfolio link
- Tech stack section
- No "References available on request"
Resume Format (STAR)
• Built real-time analytics dashboard using React + WebSocket, reducing page load from 3s to 400ms, serving 50K DAU. Format: (Situation/Task) Action → Result + Metrics
Cover Letter
Skipped many companies। Use when: career change, senior role, dream company।
Interview Stages
- Resume screen
- Recruiter chat (30m) — culture, compensation
- Technical phone screen (45-60m) — 1 coding problem
- Take-home assignment (optional, 2-8h)
- Onsite loop (4-6 interviews):
- 2 Coding (algorithm)
- 1 System Design (senior)
- 1 Behavioral
- 1 Domain/deep dive
- 1 Hiring manager
- Offer → Negotiation
Coding Interview Prep ⭐
Topics
- Array, String
- Hashmap, Set
- Linked List, Stack, Queue
- Tree (BST, traversal)
- Graph (BFS, DFS)
- Binary Search
- Two Pointer, Sliding Window
- Recursion, Backtracking
- Dynamic Programming
- Heap, Trie, Union-Find (advanced)
Resources
- LeetCode (top 150 problems)
- NeetCode roadmap (YouTube)
- Cracking the Coding Interview
- Elements of Programming Interviews
- Mock interview — Pramp, interviewing.io
Coding Interview Framework
- Understand — repeat problem, ask edge cases
- Examples — work through 1-2 manually
- Approach — explain brute force first, then optimize
- Complexity — time/space Big-O
- Code — clean, named variables, modular
- Test — walk through with example
- Edge cases — empty, single, duplicate, overflow
System Design Interview ⭐
Framework
- Clarify scope (functional + NFR)
- Capacity estimate
- API design
- Data model
- High-level architecture
- Deep dive (interviewer picks component)
- Scale, bottleneck, trade-off
Common Questions
- Design URL shortener, Twitter, Instagram
- Design chat (WhatsApp)
- Design ride-sharing (Uber)
- Design rate limiter
- Design distributed cache
- Design search autocomplete
- Design news feed
- Design video streaming
Behavioral Interview — STAR Method ⭐
Situation — context Task — what needed to be done Action — what YOU did (not "we") Result — outcome (with metrics) Example: "Tell me about a conflict" S: Teammate disagreed on architecture choice T: Needed to decide before sprint planning A: I prepared comparison doc (pros/cons), proposed POC for both approaches, presented to team R: Team chose approach B based on data; shipped 2 weeks faster, no regret decision
Common Behavioral Questions
- Tell me about yourself (2-min pitch)
- Why this company?
- Strengths / weaknesses
- Difficult teammate / conflict
- Biggest failure and lesson
- Proudest project
- How you handle disagreement with manager
- Ambiguous requirements
- Missed deadline
- Gave/received difficult feedback
- Why leave current job
Prepare Stories Bank
5-7 strong stories covering: leadership, conflict, failure, technical depth, cross-team, customer impact।
Questions to Ask Interviewer ⭐
- What does a typical day look like?
- Current biggest technical challenge?
- How is success measured for this role?
- What's the onboarding like?
- Team structure, remote policy?
- Engineering culture (testing, code review, on-call)?
- Growth opportunities?
- Why did you join? What do you love?
❌ Salary, perks (save for recruiter/offer stage)।
Salary Negotiation ⭐
- Never give first number (say "competitive", "market rate")
- Research (levels.fyi, Glassdoor, Payscale)
- Evaluate total comp (base + bonus + equity + signing)
- Multiple offers = leverage
- Negotiate EVERYTHING (base, equity, signing, remote, start date)
- Get in writing
- Polite, professional, not aggressive
- They WILL increase (never hurt to ask)
Script
"Thank you for the offer! I am excited about the role. Based on my experience and market data, I was expecting base closer to X. Is there room to move?"
Compensation Components
- Base salary
- Sign-on bonus (1-time)
- Annual bonus (% of base)
- Stock (RSU/options, 4-year vest)
- 401k match / PF
- Health insurance
- Remote stipend, learning budget
Red Flags to Watch
- Rushed process, no time to think
- Won't share salary range
- High turnover on team
- Bad reviews on Glassdoor
- Interview process chaotic/rude
- Refuse to put in writing
- Bait-and-switch role
First 90 Days on New Job
- 30 days: learn (code, team, product)
- 60 days: contribute small PRs
- 90 days: own feature/project
- Build relationships (coffee chats)
- Ask questions, don't over-promise
- Document what you learn (next hire thanks)
Continuous Interview
Even happy-এ quarterly interview — market value track, negotiation leverage, skill sharp।
🎓 Congratulations!
এই ৫০ topic master করলে you are not just a coder — you are a Software Engineer. Keep learning, keep building, keep sharing!