বাংলা

Goal guide · start from where you are

Build a career in Bangladesh

Explore product teams, export services, fintech, telecom, enterprise IT and public-interest technology—then prepare for the actual work.

Find my starting pointGive me one action this week

First, a reality check

Know the route before the checklist

Local does not mean easy or second-rate. Company category helps you ask better questions; it does not predict pay, culture or engineering quality. Verify vacancies and evaluate mentorship, ownership, working conditions and learning opportunities individually.

Product companies & startups

Practice shipping a narrow feature, using feedback and maintaining it. Ask who reviews junior work and how product decisions are made.

Services, outsourcing & export

Prepare for client requirements, readable delivery, documentation and changing scope. Confirm team language, review process and time-zone expectations.

Banks & fintech

Emphasize correctness, data access boundaries, auditability and integration. Use fictional data; production financial systems are not student playgrounds.

Telecom & enterprise IT

Explore networks, operations, integration, reliability and internal tools. Distinguish engineering roles from support and administration in each posting.

Government & public-interest technology

Check each circular's degree, examination and eligibility rules. For NGOs and service delivery, learn accessibility, field constraints and responsible data handling.

Choose by your current evidence

There is more than one route into the same industry.

Strong CP can create an advantage in algorithm-heavy hiring. If CP is not your strength, use project, debugging, testing or other role-specific evidence while building the necessary problem-solving floor. Neither route is a shortcut or guarantee.

Not a test or a score

Where are you starting today?

Jump to the point that fits. If earlier evidence is missing, return to it. Nothing is saved or scored, and stages have no fixed completion deadline.

Stage 1 / 4

Choose a work category, then a role

An industry label is too broad to tell you what to study tomorrow.

What to do

  • Compare three junior/internship postings from official employer pages. Note tasks, required stack, degree conditions and application channel; check the closing date.
  • Use one career roadmap for the repeated fundamentals. Practice reading technical English and explaining work clearly in Bangla and English.

Enough for now when…

One target role, a short employer comparison and a practical learning gap list.

Not yet: Do not rank employers from rumors or treat every advertised technology as a prerequisite.

Reference for this stage: BASIS

Stage 2 / 4

Deliver a relevant small project

A reviewer needs to see whether you can finish and explain useful work.

What to do

  • Choose a realistic local use case: a bilingual service form, stock ledger, appointment flow or offline mobile list. Use synthetic data and keep scope small.
  • Add validation, tests, setup instructions and one failure-recovery path. Ask a peer to run it from the README and fix unclear instructions.

Enough for now when…

A reviewer can run the project, see your contribution and reproduce one test or bug fix.

Not yet: No real bank credentials, customer data or unpaid production project disguised as a portfolio exercise.

Reference for this stage: Microsoft Careers

Stage 3 / 4

Prepare for interviews and evaluate the team

Hiring is a two-way check, not just a coding exam.

What to do

  • Practice coding/debugging, basic databases or your role's core tasks, plus a short project walkthrough. Tailor your CV to evidence, not skill-bar graphics.
  • Ask about supervision, code review, probation, hours, support duties, pay terms and the written role. Clarify take-home scope before doing a large assignment.

Enough for now when…

A targeted CV, practiced walkthrough and written questions to assess the opportunity.

Not yet: Do not pay a recruiter to secure an interview or accept vague terms solely because the title sounds impressive.

Reference for this stage: BASIS

Stage 4 / 4

Turn the first role into learning

Reliable small contributions create options beyond the first job title.

What to do

  • When joining, agree on a bounded first task, review expectations and who to ask for help. Learn the system before proposing a rewrite.
  • Write concise updates, document decisions and reflect on one improvement each week. Keep confidential work private and describe public contributions honestly.

Enough for now when…

A completed reviewed task and a clear account of what you learned—not just time spent at a company.

Not yet: Do not compare your first month to someone else's fifth year.

Reference for this stage: GitLab

Keep your judgment switched on

Common traps & sensible AI use

  • A referral helps discovery; it does not replace competence or guarantee selection.
  • One person's experience is a clue, not proof about every team in a company.
  • Read written employment terms and seek qualified local advice for legal questions; this is educational guidance.

AI can assist. You remain responsible.

Use AI to review practice work and improve explanations; never upload employer code or client data without authorization. Be able to debug your own submission without AI.

Explore AI-resilient skills →

One small action is enough

Make this week count

Compare three suitable postings and build one tiny feature that appears in their work. A reviewed, working feature beats another week of collecting stack names.

Afterwards, write three lines: what I did, what I learned, what I will change next. Today's direction is a draft—not a lifetime contract.

The skills underneath the goal

Pair this with a career roadmap

These are relevant starting points, not a list of prerequisites. Choose one; other careers may also fit your specific goal.

Adjacent directions

Bridge from final semester to an internship or junior software role →

Build engineering evidence through your final-year project →

Sources & requirement checks

This roadmap is CSE-Pothik editorial guidance. Sources provide specific official references, not endorsement of the entire plan. Reading guidance may be free while applications, tests, tools or publication have costs. Rules change: recheck official pages before acting. External references are primarily in English.