Learn the things a professional Software Engineer actually needs — in the right order.
এই guide তোমাকে framework list মুখস্থ করাবে না. It explains what each skill is, why you need it, how deep you need to learn it, and when to move to the next step. Goal: requirement বুঝা থেকে production system design, build, test, secure, deploy, debug and improve করা.
এই guide কীভাবে follow করবে
Strongly learn
Explain + build + debug + test করতে হবে. AI ছাড়া basic reasoning পারতে হবে.
Real work level
Real project-এ use করতে পারবে. Internal theory expert হওয়া লাগবে না.
Understand + use docs
Concept clear থাকবে; docs দেখে safe implementation করতে পারলেই enough.
Know what & why
এটা কী/কেন/কখন লাগে জানলেই এখন হবে. Deep study পরে.
Beginner practice loop
প্রতিটা topic একইভাবে finish করবে. First understand the idea, then build something tiny, break it on purpose, debug it, test it, and explain the trade-off in your own words.
Learn the concept
→ Build a small version
→ Add one realistic edge case
→ Debug one failure
→ Write/record a short explanation
→ Add it to your notes or project README
Professional Software Engineer আসলে কী করে?
Software Engineer শুধু code writer না. IEEE SWEBOK-এর current software-engineering body of knowledge requirements, design, construction, testing, operations, maintenance, quality, security, configuration management এবং professional practice-কে discipline-এর অংশ হিসেবে রাখে.
কোনটার পরে কোনটা শিখবে — and why
2026-এ companies repeatedভাবে কী চাইছে?
Recent Bangladesh full-stack postings cross-check করলে day-to-day core হিসেবে repeatedly আসে JavaScript/TypeScript, React/Next.js, Node.js, REST APIs, SQL/relational database, Git, problem-solving and clear English. More senior roles add PostgreSQL optimization, testing, Docker, CI/CD, AWS/cloud, system design, caching/Redis, queues, security, observability and technical ownership.
Core jobs
JS/TS · React · Node · REST · SQL · Git · problem solving.
Stronger full-stack fit
PostgreSQL · tests · Docker · CI/CD · Next/Nest · cloud.
Senior/AI-era fit
System design · security · observability · architecture · AI-assisted workflow.
Requirements & SDLC — coding-এর আগে কী বানাচ্ছ বুঝো
Example: “Booking page বানাও” is not enough. Ask: Who can book? Can two users choose the same slot? Payment fail করলে? Cancel করলে? Owner কে notification যাবে?
Must learn MUST PRACTICAL
ENOUGH FOR NOW Agile/Scrum theory deep না. Sprint, backlog, ticket, stand-up, review—basic work meaning জানলেই হবে.
Web & Computer Basics — framework-এর নিচে কী হচ্ছে
HTTP & browser MUST DEEP BASICS
Browser/server কীভাবে request-response exchange করে.
Know: methods, status codes, headers, cookies, caching.
Network-এর ওপর encrypted connection.
Know: certificate কী role play করে; deep cryptography না.
Domain name-কে server IP/location-এর সাথে connect করে.
Know: A/CNAME basics and why DNS issue can break a site.
Browser কোন origin থেকে request allow করবে তার browser-side policy.
Know: CORS auth/security replacement না.
Computer / Linux basics WORKING
- Process, CPU, memory, file/permission, environment variable.
- Useful commands:
ls,cd,cat,grep,tail,ps,kill,curl,ssh. - Browser DevTools: Network, Console, Performance basics.
JavaScript → TypeScript
JavaScript MUST DEEP
React এবং Node দুটোর language foundation. Framework শেখার আগে language behavior clear থাকা দরকার.
TypeScript MUST DEEP
TypeScript তোমার code-এর contracts clear করে. Large app এবং AI-generated code review দুটোর জন্য useful.
- Types/interfaces, union, narrowing, type guards, unknown vs any.
- Generics and useful utilities: Pick, Omit, Partial, Record.
- API/domain/form/component typing with
strict: true.
DSA minimum WORKING
Big-O basics, array, hash map/object, Set/Map, stack/queue, binary search, tree/graph BFS/DFS basics. Competitive programming এখন দরকার নেই.
any-spam build করতে পারো.Git & Debugging
Git MUST PRACTICAL
Git শুধু push করার tool না; team change history, review and safe rollback-এর foundation.
- Branch, merge, conflict, rebase basics, revert, stash, cherry-pick basics.
- Pull Request, code review, small commits, protected branches concept.
- Lockfile, environment config and dependency update discipline.
Debugging MUST DEEP
Reproduce
→ Gather evidence
→ Narrow the problem
→ Form a hypothesis
→ Test the hypothesis
→ Fix root cause
→ Add regression test
→ Verify
Evidence means: stack trace, browser Network tab, server logs, database query/data, request IDs—not repeated guessing.
Frontend Engineering — React + Next.js
React MUST DEEP
- Components, props/state, composition, controlled forms.
- useState/useEffect/useRef/useMemo/useCallback/useContext.
- Render/re-render, effect cleanup, race conditions.
- Server state/caching/mutations — TanStack Query concept.
Next.js STRONG
- App Router, layouts, dynamic routes, loading/error/not-found.
- Server vs Client Components — কোন code কোথায় run করে.
- Data fetching, caching/revalidation, route handlers, cookies/auth flow.
HTML/CSS + Accessibility + Performance MUST PRACTICAL
React-er age basic UI foundation strong korte hobe: semantic HTML, forms, labels, buttons/links, tables, CSS box model, responsive Flex/Grid, media queries, focus states, keyboard navigation, lazy loading, code splitting, image optimization and Core Web Vitals basics.
Real UI states you must build
- Loading, empty, error, success, permission denied and validation states.
- Search, filter, sort, pagination and detail/edit flows.
- Mobile-first responsive layout without horizontal overflow.
- Accessible forms: label, error text, focus order and keyboard submit.
Backend & API Engineering — Node.js, Express/NestJS, Auth
Node.js MUST DEEP
Event loop/async I/O, HTTP lifecycle, environment/process, error handling and graceful shutdown basics.
Backend structure MUST DEEP
Route
→ Controller (HTTP input/output)
→ Service (business rule)
→ Repository (data access)
→ Database / External API
This is not a law. Main idea হলো responsibilities mix না করা.
Express + NestJS
Express fundamentals strong রাখবে. NestJS-এ modules, DI/providers, DTO, pipes, guards, interceptors, exception filters working/strong level.
REST API MUST DEEP
- Resource design, methods/status codes, validation, errors.
- Pagination, filter, sort, search, versioning basics.
- OpenAPI/Swagger, webhooks, retries and idempotency concept.
Authentication & Authorization MUST DEEP
Session vs JWT, access/refresh token, cookies, password hashing, OAuth/OIDC basics, RBAC/permissions. Authorization must be server-side.
Database & Data — SQL + PostgreSQL first
PostgreSQL / SQL MUST DEEP
ORM MUST PRACTICAL
Prisma/Mongoose speed দেয়. কিন্তু ORM-এর নিচে data/query কী হচ্ছে বুঝতে হবে.
MongoDB WORKING
Document modeling, indexes, aggregation basics and when NoSQL fits. PostgreSQL-এর আগে Mongo deep study করার দরকার নেই.
Database exercises
- Draw ERD for users, teams, customers, deals/tasks and audit logs.
- Write migrations with rollback plan and seed data.
- Prevent duplicate booking/payment with constraints and transactions.
- Compare slow query before/after index using
EXPLAIN ANALYZE. - Practice backup restore locally, not only backup creation.
Software Design — code যেন change করা safe হয়
UI, business rule, database logic এক জায়গায় mix না.
Related responsibilities একই module-এ থাকে.
এক module change করলে সব module break না.
Modules clearly communicate কী input নেয়, কী output দেয়.
WORKING SOLID/design patterns-এর meaning বুঝবে, কিন্তু acronym/pattern force করবে না. Simple solution first.
Code review must check
Correctness · readability · scope · tests · security · performance · backwards compatibility.
Testing & Software Quality
Testing MUST DEEP
একটা ছোট business function/rule independently test.
API + DB/auth-এর মতো multiple parts together test.
User behavior from React Testing Library.
Real critical flow, e.g. login → create → update → logout.
Tools: Vitest/Jest, React Testing Library, Supertest, Playwright. Tool name-এর চেয়ে what to test বেশি important.
Quality is more than tests
Correctness, maintainability, security, performance, accessibility, reliability and operability.
Security — feature build করার সময় থেকেই
NIST SSDF secure practices-কে SDLC-এর মধ্যে integrate করতে বলে; OWASP Top 10:2025 web developers-এর major application risks-এর current awareness baseline.
Must know MUST PRACTICAL
- Broken access control / IDOR: user যেন অন্য user-এর resource access না করে.
- Authentication failures: password/reset/session/token safely handle.
- Injection: validate input; parameterized queries/ORM safely use.
- Security misconfiguration: CORS, headers, debug mode, public buckets, default secrets.
- Supply-chain risk: lockfile, dependency review, minimal packages.
- Secrets: source/client/log-এ secret না.
- Logging/alerts: security-relevant events visible, sensitive data hidden.
- Simple threat modeling: what are we protecting → who can abuse → how → control.
Security exercises
- Try to access another tenant/user record by changing an ID in the URL or API request.
- Write tests for forbidden access, expired token and missing permission.
- Run dependency audit and remove unused packages.
- Check that secrets are not in client bundle, Git history, logs or screenshots.
- Validate every external input: body, query, params, file upload and webhook payload.
Performance & Reliability
Performance MUST PRACTICAL
Guess করে optimize না. First measure.
- Frontend: network waterfall, bundle, images, unnecessary renders, Core Web Vitals basics.
- Backend: response timing, N+1 queries, slow external API, blocking work.
- Database: indexes, query plan, pagination, connection pool concept.
Reliability MUST PRACTICAL
External call forever wait করবে না.
Temporary failure-এ controlled retry; সব operation blindly retry না.
Same request আবার এলেও duplicate payment/action না হয়.
Backup আছে বললেই enough না; restore করতে পারা লাগে.
Docker, CI/CD & Linux — code থেকে production
Docker MUST PRACTICAL
Image, container, Dockerfile, ports, env, volumes, networks, Docker Compose. Goal: same application reliably different environments-এ run.
CI/CD MUST PRACTICAL
Pull Request
→ Lint + Typecheck
→ Tests
→ Build
→ Staging
→ Smoke/E2E
→ Production
→ Monitor
→ Rollback if needed
Linux WORKING
Server logs/process/permissions/env/network inspect করার মতো knowledge. Linux admin expert না.
Beginner deployment path
Run locally with env vars
→ Add Docker Compose for app + PostgreSQL + Redis
→ CI: lint, typecheck, test, build
→ Deploy one clear path first: VPS, ECS, Render, Railway or similar
→ Add logs, health check and backup
→ Practice rollback after a bad release
Early goal হলো one path reliable করা. একসাথে সব cloud/service শিখতে গেলে depth কমে যাবে.
AWS & Observability
AWS minimum MUST PRACTICAL
Who/what can access AWS resources. Learn least privilege.
Where application compute runs. One path strong করলেই enough initially.
Managed PostgreSQL database, backups/security basics.
Files/object storage; signed access concept.
CDN/cache static content near users.
Logs, metrics, alarms.
Observability — system-এর ভেতরে কী হচ্ছে বুঝার ক্ষমতা
What happened? Error/context/request ID.
How much? Request rate, latency, errors, resource use.
One request কোন service/DB/API path দিয়ে গেল.
Important failure হলে engineer-কে জানায়.
AWS Well-Architected architecture review-এ six pillars use করে: operational excellence, security, reliability, performance efficiency, cost optimization, sustainability.
System Design — পুরো system কীভাবে চলবে?
Example: PlayIndoor-style booking. 100 user থাকলে simple app works. কিন্তু 10,000 user হলে: same slot double-book হবে না কীভাবে? Images কোথায় থাকবে? Search fast কীভাবে? Email send করতে request wait করবে? Server fail করলে?
Concepts you MUST understand
Functional: “user can book.” Non-functional: fast, secure, available, scalable.
Traffic manager. Multiple server instance থাকলে request distribute করে.
Images/static files user-এর কাছাকাছি server থেকে দেয়, so faster delivery.
Frequently needed data-এর fast temporary copy. DB load কমায়. Key question: cache কখন invalid হবে?
Email, PDF, image processing-এর মতো slow work main request থেকে আলাদা queue-তে যায়.
Large files DB row-এ না রেখে S3-type storage-এ রাখা.
One bigger server না; more app instances add করা.
Related changes একসাথে correct থাকা. Booking/payment-এ critical.
Same payment/webhook request twice এলে action যেন duplicate না হয়.
Timeout, retry, backup, graceful degradation. “Dependency fail করলে system কী করবে?”
Basic only for now
BASIC ONLY Replication, sharding, multi-region, eventual consistency—concept কী এবং কেন লাগে জানবে. Hyperscale implementation deep এখন না.
Software Architecture — parts কীভাবে organize হবে?
System Design vs Architecture — simple difference
System Design
“Whole system under traffic/failure কীভাবে চলবে?”
Example: cache, queue, DB, load balancer.
Software Architecture
“Code/services কীভাবে ভাগ করলে safely change করা যাবে?”
Example: Auth module, Booking module, Payment module.
Architectural styles — how deep?
One deployable application, but clear modules. Small/medium SaaS/business app-এর জন্য strong default.
HTTP/controller → service/business → data layer. Responsibility clear রাখা.
Core business rules যেন framework/database-এর সাথে unnecessarily tightly coupled না হয়. Idea বুঝবে, dogma না.
Separate services independently deploy. Benefit আছে, but network/ops/data complexity অনেক. Default না.
One event triggers other work, e.g. OrderCreated → email/inventory. Eventual consistency/idempotency basics.
Cloud functions/events. Useful for some workloads; not a universal architecture.
Documents a professional engineer should create
- System diagram: app/API/DB/cache/queue/external systems.
- ERD: database entities and relationships.
- ADR: important decision — context, decision, trade-off.
- Runbook: deploy, migrate, logs, rollback, recovery.
AI-Assisted Engineering — AI use করবে, control হারাবে না
DORA 2025 AI-কে an amplifier বলে: strong engineering practice থাকলে benefit বাড়ে, weak process থাকলে problem-ও amplify হতে পারে. Stack Overflow 2025-এ 46% developers AI accuracy distrust করে vs 33% trust.
Professional AI workflow MUST PRACTICAL
Understand task
→ Inspect current code
→ Define acceptance criteria
→ Ask AI for a focused change
→ Review diff
→ Lint + Typecheck + Tests
→ Security / data / performance review
→ Manual verification
→ Commit
→ Monitor
You must own
- Requirements and architecture decisions.
- Authorization/data access and migration safety.
- AI code/test review and rejecting wrong output.
- Root-cause debugging when AI fails.
- Company/source-code/secrets/privacy policy.
AI Application Engineering — কতটুকু দরকার?
WORKING AFTER CORE Full-Stack engineer হিসেবে ML researcher হতে হবে না. Real app-এর মধ্যে reliable AI workflow build করা useful.
Model call, context/token/cost basics.
Free text নয়; schema-valid JSON/result use করা.
Model action suggest করে; app validates permission then executes.
Your trusted documents/data retrieve করে answer ground করা.
AI feature “seems good” না; known test cases দিয়ে quality check.
High-impact action model automatically execute না.
AI safety basics
Prompt injection, sensitive data leakage, excessive tool permission, unvalidated output, unbounded cost/rate. NIST also extends SSDF with AI-specific secure-development guidance.
BASIC ONLY NOW Agents, MCP, multi-agent frameworks. Concept জানো; core software engineering weak রেখে এগুলো chase করো না.
Communication, Documentation, Reviews & Ownership
Current job postings repeatedly ask for problem-solving, written/spoken English, collaboration, code reviews and technical ownership. এগুলো “soft” বলে ignore করলে international role কঠিন হবে.
Must practice MUST PRACTICAL
Estimation
Perfect estimate impossible. Break work into smaller tasks, identify unknowns/risks, state assumptions and communicate confidence.
One Flagship Project — সবকিছু এক project-এ prove
Build up in 3 project levels
Level 1: Fundamentals
Static responsive site + form validation + GitHub README. Proves HTML/CSS/JS basics.
Level 2: Full-stack CRUD
Auth, REST API, PostgreSQL, search/filter/pagination, tests and deploy.
Level 3: Flagship SaaS
Multi-tenant CRM with RBAC, jobs, cache, CI/CD, observability, docs and optional AI.
Next.js + TypeScript
↓
Node / NestJS API
↓
PostgreSQL
↓
Redis (cache / queue)
↓
Worker (email / report / AI job)
↓
S3 / External APIs
↓
Docker + CI/CD + AWS
↓
Logs / Metrics / Error Tracking
Across everything:
RBAC + Security + Tests + Documentation
Must prove
Portfolio proof
- Live demo link, GitHub repo and short product walkthrough video.
- README with setup, env vars, architecture, API docs, test commands and deployment notes.
- Case study: problem, users, constraints, trade-offs, screenshots and lessons learned.
- Known limitations and next improvements. Honest scope looks more professional than fake completeness.
Flagship project rubric
| Area | Good evidence | Weak signal |
|---|---|---|
| Requirements | Clear users, roles, flows, edge cases and acceptance criteria. | Only feature names, no business rules. |
| Frontend UX | Responsive, accessible, complete loading/empty/error/form states. | Looks okay only on desktop; broken mobile/forms. |
| Backend | Validated APIs, clean service boundaries, useful errors and API docs. | Controller has everything; random status codes. |
| Database | ERD, constraints, migrations, transactions, indexes and restore practice. | Tables exist but data integrity depends on luck. |
| Security | Server-side RBAC, tenant isolation tests, secret discipline, dependency review. | Auth only hides buttons in UI. |
| Testing | Unit, integration and at least a few E2E tests for critical paths. | No tests or only happy-path snapshots. |
| Production | Docker/CI/deploy/logs/backup/rollback documented and tested. | Runs only on your machine. |
| AI feature | Schema output, validation, evaluation cases and human approval for risky actions. | Raw prompt response directly trusted. |
| Communication | README, architecture diagram, ADR, runbook and concise case study. | No explanation of decisions or trade-offs. |
কোনগুলো এখন শুধু basic, deep না
| Topic | Level now | Enough for now |
|---|---|---|
| Kubernetes | BASIC | Pod/deployment/service কেন লাগে. Deep cluster ops later. |
| Terraform / IaC | BASIC → LATER | Infrastructure as Code purpose; practical after AWS foundation. |
| Kafka / RabbitMQ | BASIC | Message broker/queue purpose, retry/delivery basics. |
| GraphQL | BASIC | Schema/query/mutation and when it may fit better than REST. |
| Microservices | CONCEPT | Trade-offs; do not make it default. |
| Python/FastAPI | LATER | Useful second language for AI/data; TypeScript remains your core. |
| Go / Rust / Java / .NET | NOT NOW | Learn if repeated target jobs/project requires it. |
| Advanced ML / PyTorch | NOT NOW | Not required for Full-Stack + AI integration path. |
| MCP / multi-agent frameworks | BASIC | Know the idea; deep only when work needs it. |
32-week focused plan
Professional Full-Stack Engineer readiness checklist
Interview and application readiness
- Resume should show outcomes, stack, ownership and links. শুধু technology list না.
- GitHub pinned project should have clear README, screenshots, setup, env example and test/deploy commands.
- Practice explaining one feature end-to-end: requirement, API, DB, UI, tests, security and deployment.
- Practice take-home discipline: clarify scope, make small commits, write notes, handle edge cases and submit clean instructions.
- Prepare stories for debugging, trade-off, conflict, missed estimate and production issue.
Common beginner mistakes
Tutorial copy-paste
Course finish করলে skill prove হয় না. Same idea দিয়ে new feature independently build করতে হবে.
CSS and accessibility ignore করা
Full-stack engineer হলেও broken responsive UI, missing labels and bad forms professional signal কমায়.
Database weak রাখা
Real business apps data correctness-এর ওপর দাঁড়ায়. Constraints, transactions and migrations skip করা যাবে না.
Client-side auth trust করা
Button hide করা authorization না. Permission check server-side হতে হবে.
No tests, no verification
“Works on my machine” enough না. Important paths test, lint, typecheck and manually verify করতে হবে.
Deploy না করা
Localhost project job proof না. Deploy, logs, env, backup and rollback practice দরকার.
Too many tools chase করা
Kubernetes, microservices, new language, AI agents সব একসাথে শিখলে core weak থাকে. Need-based learning করো.
AI blindly trust করা
AI output explain/test/debug করতে না পারলে production-level code হিসেবে accept করবে না.
Research sources used
Reviewed 28 Aug 2026. Professional standards define the foundation; current job postings are used only to cross-check market demand.
Trusted learning resources
| Topic | Best starting resource | Use it for |
|---|---|---|
| HTML/CSS/JS | MDN Web Docs | Web platform fundamentals, forms, accessibility, HTTP, browser APIs. |
| Accessibility | W3C WAI Fundamentals | Semantic HTML, keyboard/focus, labels and inclusive UI basics. |
| React | React Learn | Components, state, effects, rendering and modern React mental model. |
| Next.js | Next.js Docs | App Router, server/client components, routing, caching and deployment basics. |
| TypeScript | TypeScript Docs | Types, narrowing, generics, strict mode and app-level contracts. |
| Node.js | Node.js Learn | Runtime, modules, async behavior, HTTP/server basics. |
| NestJS | NestJS Docs | Modules, providers, DTOs, guards, pipes, testing and backend structure. |
| PostgreSQL | PostgreSQL Docs | SQL, constraints, indexes, transactions, query plans, backup/restore. |
| Testing | Vitest Guide + Playwright Docs | Unit/integration tests and realistic browser E2E tests. |
| Security | OWASP Top 10 + OWASP Cheat Sheets | Common web risks and practical secure implementation checks. |
| Docker | Docker Get Started | Images, containers, Dockerfile, Compose and local production-like setup. |
| AWS | AWS Well-Architected | Production thinking: security, reliability, operations, cost and performance. |
| AI Apps | OpenAI Platform Docs + OWASP GenAI Security | LLM APIs, structured output, tool use, evaluation and AI security risks. |
https://www.computer.org/education/bodies-of-knowledge/software-engineering/topics
https://csrc.nist.gov/pubs/sp/800/218/final
https://owasp.org/Top10/
AWS Well-Architected
https://dora.dev/research/2025/dora-report/
https://survey.stackoverflow.co/2025/ai
Current Bangladesh job-market cross-checks
Job snapshot
Job snapshot
Job snapshot
Job snapshot