বাংলা

Goal guide · start from where you are

Global companies & advanced engineering

Prepare for a role, not a logo: Google, Meta, Microsoft, Amazon, Tesla, SpaceX and NASA-related routes have different work and eligibility.

Find my starting pointGive me one action this week

First, a reality check

Know the route before the checklist

Ambition is useful; a company name is not a syllabus. NASA is a government agency and most NASA employment requires U.S. citizenship. Check each vacancy's location, work authorization, degree and experience conditions before investing in a company-specific route. No roadmap guarantees an interview or offer.

Software & product engineering

Backend, frontend, mobile, data, security and UX/UI roles. Build role depth plus coding, testing and collaborative problem-solving; interview emphasis varies.

Embedded, robotics & physical systems

For relevant Tesla, SpaceX or other engineering roles, inspect requirements for C/C++, hardware interfaces, control, real-time behavior and safety. A web portfolio alone may not demonstrate these.

Research & scientific computing

Match a specific scientific question, lab or research role. Mathematics, experiments, papers and sometimes advanced degrees matter more than a generic interview-question streak.

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 role and audit the gap

You need a feasible target before a preparation calendar.

What to do

  • Read three actual openings at a suitable level. Record repeated skills, responsibilities, location constraints and which requirements are essential versus preferred.
  • Pick one career roadmap below. Practice a language, data structures, debugging, Git and the CS fundamentals your target uses; keep notes on concepts you cannot yet explain.

Enough for now when…

A one-page role brief and a small independently explained program. You know whether your target is currently eligible or needs an alternative route.

Not yet: Do not collect seven company-specific courses or start senior system-design memorization before basic coding is dependable.

Reference for this stage: Google

Stage 2 / 4

Build proof of engineering depth

Solving exercises and owning useful work are complementary skills.

What to do

  • Build one role-aligned artifact: a tested service, accessible mobile flow, evaluated model or measured embedded prototype. Explain a failure, trade-off and limitation.
  • Get a review, respond in writing and improve the artifact. For research roles, reproduce a baseline before proposing a new method.

Enough for now when…

A runnable project, clear README, meaningful tests or evaluation, and one review-driven improvement you can defend.

Not yet: A copied clone and inflated impact numbers are not evidence. Avoid publishing employer or user secrets.

Reference for this stage: Microsoft Careers

Stage 3 / 4

Practice the actual hiring process

Good work still needs clear explanation under the relevant interview conditions.

What to do

  • For coding interviews, solve unfamiliar problems aloud: clarify, plan, implement, test and explain complexity. Review mistakes instead of counting solved questions.
  • Prepare honest stories about collaboration, setbacks and decisions. Use role-specific mock interviews; confirm format, permitted tools and accommodations with the employer.

Enough for now when…

You can complete a realistic mock, explain the gaps and revise your plan; your CV links directly to verifiable work.

Not yet: Do not secretly use AI in an assessment or assume every role has the same algorithm and system-design rounds.

Reference for this stage: Amazon Jobs

Stage 4 / 4

Apply broadly and use feedback

A narrow employer list makes useful skills feel like a failed lottery ticket.

What to do

  • Apply to suitable internships and roles across employer sizes. Verify the listing on the official site; ask for a referral only with a clear role and evidence, not spam.
  • Keep a private application log, revise one weak skill from feedback and continue shipping work. Consider local or remote experience as valid routes, not consolation prizes.

Enough for now when…

A targeted application pack, an alternative route and a concrete next practice task after each review cycle.

Not yet: Do not promise yourself a fixed hiring date or treat rejection as a measure of personal worth.

Reference for this stage: Meta

Keep your judgment switched on

Common traps & sensible AI use

  • Company prestige does not replace role fit, health, eligibility or learning quality.
  • Competitive programming can strengthen problem solving; it is not the whole preparation for every role.
  • Citizenship, work authorization and export-control conditions must be checked in current official postings; do not infer legal eligibility from this guide.

AI can assist. You remain responsible.

Use AI to challenge your explanation or generate test cases, then verify them. Regularly code and reason unaided so your independent ability is visible. Follow each assessment's tool rules.

Explore AI-resilient skills →

One small action is enough

Make this week count

Pick one role, annotate three vacancies and finish one small task from its foundation roadmap. Your first win is a clearer target—not an offer letter by Friday.

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.

  • Amazon Jobs · Software development interview topics

    Use the topic guidance to plan role-specific practice; confirm the actual format with the recruiter.

    Reference reviewed:
  • Microsoft Careers · Technical interviewing

    Read problem solving, coding and testing expectations; requirements vary by role and level.

    Reference reviewed:
  • Google · Careers and job search

    Find a specific vacancy and check its qualifications, location and application instructions.

    Reference reviewed:
  • Meta · Careers

    Check current vacancies and role-specific preparation; do not infer requirements from the company name.

    Reference reviewed:
  • Tesla · Careers

    Separate software, embedded, robotics and other roles; inspect the actual responsibilities and eligibility.

    Reference reviewed:
  • NASA · Careers FAQ

    NASA is a government agency, not a company. Its FAQ says U.S. citizenship is required in most cases; check each route and vacancy.

    Reference reviewed:
  • SpaceX · Careers

    Read the specific opening, including work authorization and any export-control conditions. Do not assume one rule covers every applicant.

    Reference reviewed: