IT Sector Mein Kaunsi Jobs Hain?
// JOBS MAP — EK DEGREE, 8 CAREER PATHS
IT sirf 'developer' nahi hai — 8 alag tracks hain, kuch mein coding kam bhi hai. Apna track pehchano:
💻
Software Developer
Code likhna — web, mobile, backend. Sabse bada job pool, sabse zyada competition bhi.
INTERVIEW FOCUSDSA, ek language deep, projects, SQL.
💰 ₹3.5–8 LPA
Full Role Guide niche padho →
🧪
QA / Tester
Manual + automation testing — developer se kam competition, stable demand. Non-CS branches ki favourite entry.
INTERVIEW FOCUSTesting concepts, Selenium, API testing, SQL.
💰 ₹3–5 LPA
Full Role Guide niche padho →
☁️
DevOps / Cloud
Deployment, CI/CD, AWS/Azure, servers — experience ke saath salary steep badhti hai.
INTERVIEW FOCUSLinux, Docker, ek cloud platform, networking basics.
💰 ₹4–8 LPA
Full Role Guide niche padho →
📊
Data Analyst
Data se insights — SQL, Excel, Power BI/Tableau, thoda Python. Non-coders ke liye best technical entry.
INTERVIEW FOCUSSQL strong, ek dashboard project, statistics basics.
💰 ₹3.5–7 LPA
Full Role Guide niche padho →
🎨
UI/UX Designer
Design thinking + Figma — non-coding creative path. Portfolio hi resume hai.
INTERVIEW FOCUSPortfolio (3 case studies), Figma, design process explain karna.
💰 ₹3–6 LPA
Full Role Guide niche padho →
🛠️
Technical Support
Application/product support — entry easy, L1→L2→L3 growth. Communication strong ho toh fast track.
INTERVIEW FOCUSCommunication, SQL basics, ticketing tools, troubleshooting mindset.
💰 ₹2.5–4.5 LPA
Full Role Guide niche padho →
📋
Business Analyst
Client requirements aur tech team ka bridge — domain + communication ka game.
INTERVIEW FOCUSRequirement gathering, user stories, SQL/Excel, domain knowledge.
💰 ₹4–8 LPA
Full Role Guide niche padho →
🔐
Cybersecurity
Security testing, SOC monitoring, compliance — demand supply se zyada hai.
INTERVIEW FOCUSNetworking, Linux, security basics, CEH/Security+ certification.
💰 ₹4–8 LPA
Full Role Guide niche padho →
Kaise choose karein: Coding pasand hai toh Developer/DevOps. Coding average hai par logic achha hai toh QA/Data Analyst. Baat-cheet strong hai toh BA/Support se enter karke domain expert bano. Sab tracks se product companies tak pahuncha ja sakta hai.
Fresher Technical Q&A
// 03 — 90% INTERVIEWS MEIN YAHI AATA HAI
OOP
OOP ke 4 pillars real example ke saath samjhao.
Encapsulation: data + methods ek class mein bandhna, private variables + getters/setters (jaise ATM — balance direct access nahi, methods se). Abstraction: complexity chhupana, sirf zaroori cheez dikhana (car ka accelerator — engine internals nahi dikhte). Inheritance: parent class ki properties child ko milna (Vehicle → Car). Polymorphism: ek naam, alag behaviour — overloading (compile time) aur overriding (runtime). Har pillar ke saath example bolo, definition akela weak lagta hai.
Abstract class aur interface mein difference?
Abstract class: partial implementation ho sakti hai, constructors ho sakte hain, ek hi extend hoti hai — "is-a" relationship with shared code. Interface: pure contract (Java 8 se default methods aa gaye, yeh mention karo), multiple implement ho sakte hain — capability define karta hai (Comparable, Serializable). Kab kya: common code share karna hai toh abstract class, sirf behaviour ka contract chahiye toh interface.
Overloading aur overriding mein difference?
Overloading: same class mein same naam ke methods, alag parameters — compile-time polymorphism. Overriding: child class parent ke method ko redefine karti hai, same signature — runtime polymorphism. Ek tricky follow-up: static methods override nahi hote (method hiding hota hai) — yeh pata hona senior-level detail hai.
DSA + Coding
Big-O notation kya hai? O(n) aur O(log n) ka difference?
Algorithm ke time/space growth ka measure input size ke saath. O(1) constant, O(log n) — har step mein problem aadhi (binary search), O(n) linear (ek loop), O(n²) nested loops, O(n log n) — efficient sorting (merge sort). Example se bolo: 10 lakh elements mein binary search sirf ~20 comparisons leta hai, linear search 10 lakh tak — yahi log n ka power hai.
Array mein duplicate kaise find karoge?
Teen approaches bolo — brute force: nested loop O(n²); sorting: sort karke adjacent compare O(n log n); best: HashSet mein daalte jao, agar already exist kare toh duplicate O(n) time O(n) space. Interviewer trade-off discussion chahta hai — "agar space constraint hai toh sorting, warna HashSet."
String reverse / palindrome check kaise karoge?
Two-pointer approach: ek pointer start se, ek end se — compare karte hue beech tak aao, O(n) time O(1) space. Built-in reverse se better yeh manually likhna aana chahiye. Follow-up ready rakho: case-insensitive aur special characters ignore karne wala version ("A man, a plan, a canal: Panama").
Stack aur queue ka difference + real use?
Stack LIFO (last in first out) — undo feature, browser back button, function call stack, expression evaluation. Queue FIFO — printer queue, BFS, message queues, request handling. Follow-up: "stack se queue kaise banaoge?" — do stacks use karke; yeh classic question hai, ek baar practice kar lo.
SQL & DBMS
Joins samjhao example ke saath.
INNER JOIN: dono tables mein matching rows hi. LEFT JOIN: left table ki saari rows + right se match (na mile toh NULL). RIGHT JOIN: ulta. FULL OUTER: dono ki saari. Example ready rakho: Employees aur Departments table — "woh employees jinka department assign nahi hai" = LEFT JOIN WHERE dept.id IS NULL. Ek query likhne ko bolenge, practice karke jao.
Second highest salary kaise nikaloge?
Classic question — 2-3 tarike batao: (1) SELECT MAX(salary) FROM emp WHERE salary < (SELECT MAX(salary) FROM emp); (2) LIMIT/OFFSET: ORDER BY salary DESC LIMIT 1 OFFSET 1; (3) DENSE_RANK() window function — duplicates handle karne ke liye best. Teeno bolne par interviewer samajh jaata hai ki SQL aati hai.
Index kya hai? Kab nahi lagana chahiye?
Index book ke index jaisa hai — full table scan ke bajay direct row tak pahunchna (B-tree structure). WHERE, JOIN, ORDER BY columns par lagate hain. Kab nahi: chhoti tables, jo columns rarely query hote hain, heavy INSERT/UPDATE tables (har write par index bhi update hota hai — write slow ho jaata hai). Primary key par index automatic hota hai.
Normalization kya hai?
Data redundancy kam karne ka process. 1NF: atomic values, no repeating groups. 2NF: 1NF + no partial dependency (composite key ke part par dependence nahi). 3NF: 2NF + no transitive dependency. Practical line: "reporting/analytics mein performance ke liye kabhi-kabhi denormalize bhi karte hain" — yeh bolne par real-world samajh dikhti hai.
Web
Browser mein URL type karne se page aane tak kya hota hai?
Classic question: (1) DNS lookup — domain se IP, (2) TCP connection + TLS handshake (HTTPS), (3) HTTP request server ko, (4) server process karke response deta hai (HTML), (5) browser parse karta hai — DOM banata hai, CSS/JS/images ke liye aur requests, (6) render. Har step ek line mein — 60 second ka crisp answer banao.
GET aur POST mein difference? Status codes batao.
GET: data URL mein, idempotent, cache hota hai, sensitive data nahi bhejte. POST: data body mein, create operations ke liye. Status codes: 200 OK, 201 Created, 301 redirect, 400 bad request, 401 unauthorized (login nahi), 403 forbidden (login hai par permission nahi), 404 not found, 500 server error. 401 vs 403 ka difference specifically poocha jaata hai.
Experienced Q&A
// 04 — PROJECTS + DESIGN + PRACTICES
Apna current project ka architecture explain karo.
Yeh experienced interview ka opening question hai — 2-minute pitch ready rakho: (1) Business problem kya solve karta hai, (2) tech stack + kyun (frontend, backend, DB, deployment), (3) aapka specific ownership, (4) ek technical challenge jo aapne solve kiya. Whiteboard/paper par boxes bana kar samjhao — data flow dikhao. Jo cheez aapne nahi ki, uska credit mat lo — cross-questions mein pakde jaoge.
API slow ho gayi hai production mein — kaise debug karoge?
Systematic: (1) Monitoring/APM se dekho — kaunsa endpoint, kab se, kitna slow. (2) Layer identify karo — DB query slow (EXPLAIN plan, missing index, N+1 queries)? External API call? App code (loops, serialization)? (3) Quick wins: caching, query optimize, pagination. (4) Load ka issue hai toh horizontal scaling/connection pool. Real example ke saath bolo — "hamare order API mein N+1 query issue tha, eager loading se 3 sec se 300ms kiya."
Monolith vs microservices — kab kya?
Monolith: ek codebase, ek deployment — simple, fast development, chhoti teams ke liye best. Microservices: services alag-alag deploy hoti hain — independent scaling, tech flexibility, lekin complexity (network calls, distributed transactions, monitoring) badh jaati hai. Mature answer: "start with monolith, extract services jab genuinely scale ya team-size demand kare — microservices default answer nahi hai." Yeh balanced view senior engineers ko pasand aata hai.
Git mein merge conflict kaise handle karte ho? Rebase vs merge?
Conflict tab jab same lines do branches mein change hui hon — file kholkar conflict markers resolve karo, test karo, commit. Merge: history preserve hoti hai, merge commit banta hai. Rebase: commits ko re-apply karke linear history — clean lekin shared branches par rebase mat karo (history rewrite ho jaati hai). Team practice bolo: feature branches, PR review, squash merge.
Code review mein kya dekhte ho?
(1) Correctness — logic + edge cases, (2) readability — naming, structure, (3) tests hain ya nahi, (4) security — input validation, SQL injection, secrets hardcoded toh nahi, (5) performance red flags — loop mein DB call. Culture wala point: "review mein code par comment karta hoon, person par nahi — aur nitpicks ko 'nit:' mark karta hoon." Yeh soft-skill signal strong hai.
Production bug aa gaya jo aapke code se tha — kya kiya?
Ownership dikhaao, defensiveness nahi: "Payment status update mein ek race condition thi jo load par hi dikhi. Pehle impact contain kiya (feature flag off), fix deploy kiya, phir RCA likha aur uss path par integration test add kiya taaki repeat na ho." Formula: contain → fix → learn → prevent. Blame kisi par nahi — process improvement par end karo.
💻 Software Developer — Complete Guide
Coding rounds, projects, Git, API design — developer interview ka core.
⬆ Jobs MapDSA preparation kaise karein — kaunse patterns pakke karne hain?
Random 500 problems nahi — patterns pakdo: (1) Two pointers (sorted array pairs, palindrome), (2) Sliding window (subarray/substring problems), (3) HashMap (frequency, two-sum family), (4) Binary search (sorted + "minimum/maximum possible" wale), (5) Stack (parentheses, next greater element), (6) BFS/DFS (tree/graph traversal), (7) Recursion + basic DP (fibonacci → climbing stairs → knapsack idea). Har pattern ke 8-10 problems = 70-80 problems total, aur 90% service + mid-level product interviews cover. Interview mein bolna: brute force → complexity → optimize — chup hokar sochna sabse bada minus hai.
Git ke daily commands aur workflow batao.
Team workflow: main/develop branch protected → feature branch banao → commits → push → Pull Request → review → merge. Commands table yaad rakho:
| Command | Kaam |
|---|
| git clone / pull | Repo laana / latest changes laana |
| git checkout -b feature/x | Nayi branch banana + switch |
| git add . / commit -m "" | Stage + commit (chhote, meaningful commits) |
| git push origin branch | Remote par bhejna |
| git merge / rebase | Branches jodna (shared branch par rebase nahi) |
| git stash / stash pop | Adhura kaam side mein rakhna |
| git log --oneline / diff | History / changes dekhna |
| git revert | Kisi commit ko safely undo (history rakh kar) |
Conflict aaya toh: file kholo, <<<< ==== >>>> markers ke beech sahi version rakho, test chalao, commit. "Conflict se darta nahi, samajh kar resolve karta hoon" — yeh confidence interview mein dikhna chahiye.
Achhi REST API kaise design karoge?
(1) Resources = nouns: /users, /orders — verbs nahi (/getUser ❌), (2) HTTP methods se action: GET (read), POST (create), PUT/PATCH (update), DELETE, (3) sahi status codes: 200/201/400/401/403/404/500, (4) versioning: /api/v1/, (5) pagination bade lists par (?page=2&limit=20), (6) filtering/sorting query params se, (7) consistent error format ({"error": {"code","message"}}), (8) auth — JWT/token header mein. Example bolo: "GET /users/5/orders?status=pending" — ek line mein poori design philosophy dikh jaati hai.
Production mein bug hai lekin locally reproduce nahi ho raha — approach?
(1) Exact context lo — kaunsa user, kaunsa input, kab, kis environment/browser mein, (2) logs/error tracking dekho (stack trace, request payload), (3) environment differences socho — data difference, config/env vars, timezone, concurrency/race condition, cache, (4) same data ke saath staging mein try karo, (5) nahi mile toh targeted logging add karke deploy karo aur pakdo. "Race condition ya data-specific issue sabse common hote hain jo locally nahi dikhte" — yeh insight bolo, debugging maturity dikhegi.
"Kaunsi language/framework best hai?" — kaise answer karoge?
Mature answer: "Language tool hai, problem-solving asli skill — main ek stack mein deep hoon (jaise Java+Spring ya JS+Node/React) aur naya stack 2-3 hafte mein pick kar leta hoon kyunki fundamentals same hain (data structures, HTTP, DB, OOP)." Fresher ke liye rule: EK language mein gehraai > teen mein surface knowledge. Resume par wahi likho jisme live code kar sako.
🧪 QA / Tester — Complete Guide
Developer se kam bheed, stable demand — non-CS ki favourite entry.
⬆ Jobs MapAgile team mein tester ka role kya hai?
Sprint planning mein stories ke acceptance criteria par sawal uthana (testing yahin se shuru hoti hai — requirement ambiguity sabse sasta bug hai), test cases story ke saath-saath likhna, dev-done hote hi turant testing (end mein dump nahi), automation regression ko sprint mein hi update karna, demo mein quality ka voice banna. "Tester quality ka gatekeeper nahi, quality ka enabler hai — poori team quality ki maalik hai" — yeh modern answer hai.
Ek perfect bug report mein kya hota hai?
Searchable title, environment (build no., browser/OS), numbered steps to reproduce, expected vs actual, severity + priority, screenshot/video, logs, reproducibility (5/5 ya intermittent 2/5). Golden test: "developer bina mujhse baat kiye reproduce kar le." Aur ek pro habit: duplicate check karke hi naya bug daalo.
Manual se automation mein kaise jaoge?
6-mahine ka realistic path: (1) ek language basics — Java ya Python (loops, OOP, collections), (2) Selenium/Playwright — locators, waits, interactions, (3) TestNG/PyTest — assertions, annotations, (4) POM framework khud banao apne kisi site par, (5) Git par daalo — yahi portfolio hai, (6) API automation (RestAssured/requests) add karo. Interview mein framework KHUD ka banaya hona 10 tutorials dekhne se zyada value rakhta hai.
Is field ki poori depth kahan milegi?
Aapke isi access mein
Software Testing / QA ki alag complete guide included hai — manual concepts, Selenium, API testing, aur 8 testing specializations (Automation/SDET, Performance, ETL...) ke role-wise deep guides ke saath.
→ QA/Testing Guide kholo — same key se khulegi.
☁️ DevOps / Cloud — Complete Guide
Linux, Docker, CI/CD, cloud — deployment ka poora game.
⬆ Jobs MapLinux ke kaunse commands roz lagte hain?
Yeh table DevOps entry ka minimum hai:
| Command | Kaam |
|---|
| tail -f app.log | Live logs dekhna (debugging ka #1 tool) |
| grep "ERROR" file | Logs mein pattern dhoondhna (-i, -r options) |
| ps aux | grep node | Process check karna |
| top / htop | CPU/memory kaun kha raha hai |
| df -h / du -sh * | Disk full kahan se hui |
| systemctl status/restart nginx | Services manage karna |
| chmod / chown | Permissions (755, 644 samjho) |
| scp / rsync | Servers ke beech files |
| curl -I url | Endpoint/headers test karna |
| ss -tlnp | Kaunsa port kaun sun raha hai |
Docker aur VM mein difference? Basic commands?
VM poora OS chalata hai (heavy, minutes mein boot), container sirf app + dependencies host ke kernel par (MBs, seconds mein start). Isliye ek server par dus containers aaram se. Commands: docker build -t app . (image banao Dockerfile se), docker run -d -p 8080:80 app, docker ps, docker logs -f id, docker exec -it id bash (andar ghusna), docker-compose up (multi-container). Dockerfile ke layers aur .dockerignore ka concept bhi bol do — image size optimize karna real skill hai.
CI/CD pipeline explain karo.
Code commit hote hi automatic chain: (1) Build — code compile/dependencies, (2) Test — unit + integration tests (fail = pipeline ruk gayi, kharab code aage nahi), (3) Artifact — Docker image bana kar registry mein push, (4) Deploy — staging par auto, production par approval ke saath, (5) Monitor — health checks, rollback ready. Tools: GitHub Actions/Jenkins/GitLab CI. Fayda ek line mein: "insaan ki galti hatao, release ka darr hatao — din mein 10 baar deploy possible." Ek chhota pipeline khud banake dikhana (GitHub Actions ka YAML) interview ka trump card hai.
Cloud basics — AWS ke core services?
EC2 (virtual server), S3 (file/object storage — website assets, backups), RDS (managed database), VPC + Security Groups (network + firewall — kaunsa port kisse khula), IAM (kaun kya access kar sakta hai — least privilege rule), CloudWatch (monitoring/logs), Load Balancer + Auto Scaling (traffic badhne par servers khud badhna). Free tier par khud ek app deploy karke jao — "maine EC2 par Nginx + app deploy ki, S3 mein backups rakhe" — yeh ek line certificates se zyada weight rakhti hai.
Production down hai — incident kaise handle karoge?
(1) Acknowledge + communicate (status update stakeholders ko), (2) blast radius dekho — sab down ya ek feature? (3) recent change check — last deploy? Config change? (80% incidents recent change se) → rollback fastest fix hai, (4) logs/metrics/alerts se isolate (CPU? memory? DB connections? disk full?), (5) fix/mitigate, (6) baad mein blameless RCA + action items (alert add karo, runbook likho). "Pehle service restore, phir root cause" — yeh priority order hi DevOps mindset hai.
📊 Data Analyst — Complete Guide
SQL, Excel, dashboards, business thinking — non-coders ki best technical entry.
⬆ Jobs MapSQL mein kya-kya aana chahiye analyst ke liye?
(1) Joins — saare types + kab kaunsa, (2) GROUP BY + HAVING (aggregation ke baad filter), (3) subqueries + CTE (WITH clause — readable queries), (4) window functions — ROW_NUMBER/RANK/DENSE_RANK (top-N per group: "har region ka top 3 product"), LAG/LEAD (month-over-month growth), (5) CASE WHEN (categorization), (6) date functions. Interview ka pakka pattern: "har category ka second highest" — window function se: ROW_NUMBER() OVER (PARTITION BY category ORDER BY sales DESC) = 2. Yeh ek query type 10 sawaalon ka jawab hai.
Portfolio ke liye dashboard project kaise banaoge?
(1) Public dataset lo (Kaggle — sales/ecommerce type), (2) pehle business questions likho — "kaunsa region girta ja raha hai? Kaunsa product margin khata hai?", (3) data clean karo (SQL/Excel — duplicates, nulls, formats), (4) Power BI/Tableau mein 1-page dashboard: 4-5 KPI cards + trend + breakdown charts + filters, (5) insights likho neeche — "West region ka 60% decline sirf 2 products se hai." Dashboard sundar banana aadha kaam hai — INSIGHT nikalna poora kaam. Interview mein yeh project screen-share karke 5 minute mein present karna practice karo.
Statistics ke basics jo poochhe jaate hain?
Mean vs median — outliers ho toh median sach bolta hai (salary data classic example: ek crorepati aa gaya toh mean uchhal gaya, median stable), percentiles (p90 response time ka matlab), correlation ≠ causation — "ice cream sales aur drowning saath badhte hain — dono ki wajah garmi hai, ek dusre ki nahi" — yeh example bolo, (basic) A/B testing ka concept — do versions ka controlled comparison. Deep math nahi — in concepts ki clear samajh analyst interview ke liye kaafi hai.
Case: "Pichle mahine sales 20% gir gayi — analysis kaise karoge?"
Structured drill-down bolo: (1) Verify — data issue toh nahi (tracking toota, ek din missing)? (2) Segment karo — region-wise, product-wise, channel-wise, customer-type-wise — girawat SAB jagah hai ya concentrated? (3) Concentrated hai toh us segment mein kya hua — price change, stock-out, competitor, seasonality (pichle saal ka same month compare)? (4) Sab jagah hai toh macro — market, season, apna koi policy change. (5) Findings ko ek line mein: "80% girawat North ke 2 distributors se hai jinka stock-out tha." Framework > jawab — interviewer approach sun raha hai.
Excel mein kya aana chahiye?
XLOOKUP/VLOOKUP + INDEX-MATCH (data milana), pivot tables (2 minute mein summary), SUMIFS/COUNTIFS, text cleaning (TRIM, TEXT-TO-COLUMNS, LEFT/RIGHT/MID), conditional formatting, remove duplicates, basic charts. Power Query ka naam lo (repeatable data cleaning — analyst ka secret weapon). "Excel mein main raw dump se pivot-ready data 10 minute mein bana leta hoon" — is confidence ke saath ek live test bhi de paoge toh job pakki.
🎨 UI/UX Designer — Complete Guide
Design process, portfolio case studies, Figma — non-coding creative path.
⬆ Jobs MapUX design process explain karo.
(1) Research — users se baat, competitor analysis, problem samjho (design shuru mat karo!), (2) Define — persona + user journey + pain points, (3) Information architecture — screens/flow ka structure, (4) Wireframes — low-fidelity layout (yahan iterate karna sasta hai), (5) Visual design — UI, design system ke saath, (6) Prototype — clickable flow, (7) Usability testing — 5 users se bhi 80% problems dikh jaati hain, (8) Handoff — dev ke liye specs. Process bolo with WHY — "wireframe pehle isliye ki layout ki galti wahan 10 minute mein fix hoti hai, code mein 10 din."
Portfolio case study kaise likhein?
Structure (2-3 case studies kaafi hain): Problem statement (kiska problem, kya problem) → aapka role → research findings (2-3 insights) → design decisions WITH REASONING ("CTA upar isliye rakha kyunki research mein users scroll nahi kar rahe the") → final screens → outcome/learning. Sabse badi galti: sirf sundar screens dikhana. Interviewer decisions ke REASONS mein interested hai. Redesign case study (kisi existing app ka) fresher ke liye easiest start hai.
UI aur UX mein difference?
UX = poora experience — user apna kaam kitni aasani se kar paya (flow, structure, logic, feelings). UI = visual layer — colors, typography, spacing, components. Classic example: ketchup ki kaanch ki bottle sundar (UI) lekin nikalna mushkil; ulti squeeze bottle = better UX. "Sundar app jo confuse kare = achhi UI, buri UX" — ek line mein clear.
Design principles/heuristics kaunse follow karte ho?
Visibility of system status (loading dikhao, feedback do), consistency (same action same jagah same tarike se), error prevention > error messages, recognition over recall (user ko yaad na rakhna pade), visual hierarchy (size/color/spacing se aankh guide karo), accessibility — contrast ratios, touch targets (~44px), alt text. Nielsen ke heuristics ka naam le sakte ho. Ek app ki on-the-spot critique karne ko bolenge — in principles ke naam ke saath critique karo, vocabulary hi level dikhati hai.
Figma mein kya aana chahiye?
Components + variants (button ke saare states ek component mein), auto-layout (responsive frames — yeh sabse zaroori hai), styles (colors/text tokens — design system ki base), constraints, prototyping (interactions, overlays), dev mode/inspect basics. Speed test ho sakta hai — ek screen ka recreate. Auto-layout confidently use karte ho toh interview mein zaroor dikhao — beginners isi mein pakde jaate hain.
🛠️ Technical Support — Complete Guide
L1→L2→L3, SLA, ticketing — entry easy, growth communication se.
⬆ Jobs MapL1, L2, L3 support mein kya difference hai?
L1: pehla contact — known issues, password resets, basic troubleshooting, KB articles se solve, nahi hua toh proper info ke saath escalate. L2: deeper technical — logs analysis, configuration, DB queries, workarounds. L3: engineering/product team — code-level fixes, patches. Growth path yahi hai: L1 par communication + product knowledge banao → L2 par technical depth (SQL, logs, APIs) → wahan se DevOps/QA/BA branches khulti hain. "Support dead-end nahi, product ko sabse gehra jaanne ka raasta hai" — yeh positive frame interview mein bolo.
SLA aur priority kaise kaam karte hain?
SLA = response aur resolution ka committed time, priority ke hisaab se:
| Priority | Example | Typical Response / Resolution |
|---|
| P1 — Critical | Production down, sab users affected | 15-30 min / 4 ghante — all hands |
| P2 — High | Major feature down, workaround nahi | 1 ghanta / 1 business day |
| P3 — Medium | Issue hai, workaround available | 4-8 ghante / 3-5 din |
| P4 — Low | Cosmetic, question, request | 1 din / planned |
Pro point: "SLA breach hone se pehle escalate karna meri zimmedari hai — breach ke baad sorry bolna nahi." Proactive escalation hi support mein senior banati hai.
Troubleshooting ka framework kya use karte ho?
(1) Gather — exact error, screenshot, kab se, kya change hua, kitne users, (2) Replicate — khud reproduce karo, (3) Isolate — user-specific? Browser-specific? Data-specific? Environment? (aadha problem yahin solve), (4) Known issue check — KB/past tickets search, (5) Fix ya workaround do, (6) Document — ticket mein poora, naya issue tha toh KB article banao. Step 6 wala habit bolo — "main solve karke KB likhta hoon taaki agli baar L1 par hi solve ho" — team-player + growth mindset dono dikh gaye.
Gussa customer/user call par hai — kaise handle karoge?
(1) Sunne do — interrupt mat karo, notes lo, (2) acknowledge — "main samajh sakta hoon, aapka kaam ruka hai" (empathy ≠ galti maanna), (3) facts par aao — specific info lo, (4) realistic commitment — jhootha "abhi ho jayega" mat bolo, timeline + update promise karo, (5) follow-up KHUD karo — bina reminder ke update dena hi trust banata hai. Support mein technical skill entry dilati hai, yeh skill promotion.
📋 Business Analyst — Complete Guide
Requirements, user stories, UAT — business aur tech ka bridge.
⬆ Jobs MapRequirements kaise gather karte ho?
Techniques: stakeholder interviews (open questions — "aaj yeh kaam kaise karte ho? Kahan phansta hai?"), workshops (conflicting stakeholders ko ek room mein), observation/job shadowing (log jo bolte hain aur karte hain — alag hota hai), existing documents/reports analysis, prototypes dikha kar feedback. Golden rule: user SOLUTION bolta hai ("yahan button chahiye"), BA PROBLEM nikalta hai ("aap actually kya achieve karna chahte ho?"). Yeh 5-why-style probing hi BA ki asli skill hai.
User story kaise likhte ho? Acceptance criteria ka example?
Format: "As a [role], I want [kya], so that [kyun]." Example: "As a customer, I want to save my address, so that checkout fast ho." Acceptance criteria (Given-When-Then): "Given user logged in hai, When woh address save karta hai, Then agli baar checkout par woh address pre-filled dikhe" + edge cases (max 5 addresses, invalid pincode par error). AC hi dev aur QA ka contract hai — jitne clear AC, utne kam bugs. INVEST criteria ka naam bhi le sakte ho (Independent, Negotiable, Valuable, Estimable, Small, Testable).
BRD, FRD aur user story mein kya difference hai?
BRD (Business Requirement Document): business KYA chahta hai aur kyun — high level, business language, stakeholders sign karte hain. FRD (Functional): system KAISE behave karega — features, rules, validations detail mein. User stories: agile ka format — chhote, incremental, sprint-sized. Waterfall projects mein BRD/FRD chain, agile mein epics → stories. "Documentation ka level project ki methodology se decide hota hai" — yeh flexible answer do.
Requirement baar-baar change ho rahe hain — kya karoge?
(1) Change ko dushman mat samjho — agile mein expected hai, lekin PROCESS se aaye: change request → impact analysis (effort, timeline, dependencies) → stakeholder approval → backlog reprioritize, (2) baar-baar ho raha hai toh root cause — requirements shuru mein hi vague thi? Sahi stakeholder involve nahi tha? (3) scope creep vs genuine change ka farak — "yeh naya requirement hai, isi story mein nahi ghusega, nayi story banegi." Politely "no" bolna aur written trail rakhna — BA ki survival skills.
UAT kaise plan karte ho?
User Acceptance Testing — business users verify karte hain ki system UNKE real scenarios mein kaam karta hai (QA testing ke BAAD, go-live se pehle). Plan: UAT scenarios business processes se likho (test cases jaise technical nahi — "month-end invoice run karo"), real-jaisa data, users identify + training, defect logging process, entry/exit criteria (kitne % pass par sign-off), sign-off document. "UAT mein naye requirements nikalte hain — unhe defects se alag karke phase 2 mein daalna" — yeh practical wisdom bolo.
🔐 Cybersecurity — Complete Guide
Attacks, SOC, VAPT, certifications — demand supply se zyada.
⬆ Jobs MapCIA triad kya hai?
Security ke 3 pillars: Confidentiality — data sirf authorized ko dikhe (encryption, access control), Integrity — data change na ho bina permission (hashing, checksums, signatures), Availability — system chalta rahe (redundancy, DDoS protection, backups). Har security decision in teeno ke against tola jaata hai. Saath mein AAA bolo — Authentication (tum kaun ho), Authorization (kya kar sakte ho), Accounting (kya kiya — logs). Interview ka pehla sawal aksar yahi hota hai.
Common attacks aur unse basic bachav batao.
Yeh chart entry-level security ka core hai:
| Attack | Kya hota hai | Basic Defense |
|---|
| Phishing | Fake email/site se credentials churana | User training, email filters, MFA |
| SQL Injection | Input field se DB queries chalana ('OR 1=1) | Parameterized queries, input validation |
| XSS | Site par malicious script inject karna | Output encoding, CSP headers |
| Brute force | Passwords guess karte rehna | Lockout policy, MFA, strong password policy |
| MITM | Beech mein baith kar traffic padhna | HTTPS/TLS everywhere, public wifi caution |
| Ransomware | Data encrypt karke firauti | Offline backups, patching, least privilege |
Ek line yaad rakho: MFA + patching + backups + least privilege — yeh 4 cheezein 90% attacks rok deti hain. Simple bolo, solid lagoge.
SOC analyst ka din kaisa hota hai?
SIEM (Splunk/QRadar/Sentinel type tool) par alerts aate hain → triage: false positive hai ya genuine? → genuine par investigation: kaunsa user/system, kya activity (login from naya country? Malware signature? Unusual data transfer?) → severity ke hisaab se escalate/contain (system isolate, account disable) → document + report. Shift-based kaam. "False positives ko tune karna bhi analyst ka kaam hai warna alert fatigue mein asli attack miss ho jaata hai" — yeh insight L1 SOC interview mein bahut strong hai.
Vulnerability assessment aur penetration testing mein difference?
VA: automated scanning (Nessus/OpenVAS type) — known vulnerabilities ki LIST banana, broad coverage, regular (monthly/quarterly). PT: manually EXPLOIT karke dikhana ki attacker kahan tak ghus sakta hai — depth, skilled human, scoped + authorized (written permission ke bina PT = crime, yeh bolna mat bhoolo). VA batata hai "khidki kamzor hai", PT dikhata hai "main khidki se ghus kar tijori tak pahuncha." Dono complementary hain.
Cybersecurity mein entry kaise karein — certifications aur practice?
Base: networking (TCP/IP, ports, DNS, firewall concepts) + Linux — yeh bina kuch nahi hota. Certs order: CompTIA Security+ (best entry — concepts), phir interest se: CEH (offensive, HR-recognized India mein), SOC ke liye Splunk/Microsoft SC-200 type, aage OSCP (serious offensive). Practice: TryHackMe/HackTheBox (ghar baithe legal labs), apna home lab (VirtualBox mein Kali + vulnerable VMs). "Certificate + lab practice + ek documented project (jaise apne home network ka security audit)" — yeh combo fresher ko bheed se alag karta hai.
HR Round Model Answers
// 05 — IT-SPECIFIC HR QUESTIONS
Tell me about yourself.
Formula: education → skills/stack → best project ek line → kya dhoondh rahe ho. "Maine CS mein B.Tech kiya, Java aur SQL strong hai, maine ek inventory management app banaya Spring Boot + MySQL mein jo 3 dukaanein actually use karti hain. Main aisi team dhoondh raha hoon jahan production code par kaam karke seekh sakoon." Personal project jo real use hota ho — sabse bada differentiator hai.
Service bond / 2-year agreement sign karoge?
Service companies mein common hai. Agar career start karna hai toh haan bolna practical hai — "Haan, main commitment ke saath aa raha hoon." Andar se plan kuch bhi ho, interview mein bond par negotiation mat karo — instant red flag.
Gap year / backlog kyun tha?
Seedha, short aur forward-looking: "Backlog second year mein tha, maine usi saal clear kiya aur uske baad ke saare semesters first attempt mein nikale." Ya gap ke liye: "us time maine [skill/course/family reason] par kaam kiya." Lambi safai mat do — 3 lines, phir aage badho.
Why this company?
Company-specific 2 cheezein bolo — unka product, tech stack, ya recent news: "Aapki company [X domain] mein kaam karti hai aur mujhe [Y tech] mein kaam karna hai jo aapke stack mein hai." Generic "great work culture" sab bolte hain — research karke jao, 5 minute ki mehnat hai.