Opens in a new tab

Free career guidance for CSE students

You got into CSE. Now what?

Students can enter CSE for its popularity, earning potential, or promise of opportunities abroad—then discover a field far broader than the few roles they have heard about.

Without early orientation, semesters can disappear into trends and random tutorials. If that feels familiar, you have not missed your chance.

Understand the options, try real work and choose one useful next step—while building the fundamentals and judgment that make AI useful.

A Chakma woman holds a QA checklist tablet between two teammates at laptops, all three smiling toward you.
A note from your future self

“Start small. Future you will be glad you did.”

Your advantage in the AI era

AI can generate code. Can you lead the decision?

AI is already removing some implementation work, changing junior roles and raising expectations across experience levels. That disruption is real. Now try a harder question: what happens when the software actually matters?

No prediction required. Think through four systems and the pipeline that must produce their future engineers.

Five questions worth thinking about

Do not look for the answer we want. Try to answer each one yourself.

01 · Space

Would you launch it?

AI built the spacecraft software. Every test is green. Is that enough to launch?Think it through

An AI agent designs and implements software for a spacecraft carrying people or equipment worth hundreds of millions of dollars. The tests are green and the AI says it is ready. Who decides whether the architecture fits, the assumptions are valid, the failure modes are understood and the system is actually safe to launch?

“All tests passed” sounds different when the rollback button is 400 km above Earth.

Who owns the final decision?
02 · Health

Would “looks correct” be enough?

The common medical cases work. What happens to the uncommon patient?Think it through

Software influences a medical decision or controls a medical device. The AI-generated implementation works for common cases. Who investigates the uncommon patient, strange input, sensor failure, missing data or condition nobody included in the happy-path demo?

“Works on my machine” is not a medical certification strategy.

Who proves the edge cases are acceptable?
03 · Finance & FinTech

Would you trust it with the ledger?

AI delivered the financial feature quickly and confidently. Where could the money—or the decision—go wrong?Think it through

A banking, insurance or FinTech platform processes millions of transactions, claims or decisions. AI produces a feature quickly and explains it confidently. Who verifies security, consistency, reconciliation, permissions, auditability, compliance, failure recovery and what happens when two systems disagree?

“Probably correct” is less charming when the missing zero belongs to your account.

Who understands the consequences?
04 · Your business

Now imagine it is your money.

Your billion-dollar advantage lives in this system. Is “the code runs” the only requirement?Think it through

You build a company around business logic competitors do not have. AI can generate and modify the system. Would somebody still need to understand the rules, architecture, security, data, trade-offs and long-term consequences well enough to decide what should actually be built?

Plot twist: now you are the stakeholder.

What expertise would you want in the room?
05 · Talent pipeline

Where does the next senior come from?

If beginners never get meaningful engineering work, who becomes experienced enough to supervise tomorrow's systems?Think it through

Companies may redesign junior work, apprenticeships and career ladders. AI may help beginners attempt harder work earlier. But judgment still grows through reviewing decisions, debugging strange failures, reading difficult systems, making mistakes and correcting them. If companies keep consuming experience without helping create it, the pipeline eventually becomes their problem too.

SeniorEngineer.exe does not install itself after eight years.

What would a sustainable path from beginner to expert look like?
What did all five questions have in common?Show me

Notice what we never asked.

Can AI write the code?

Increasingly, yes—and it will probably get better at it. The harder questions were:

  • What should actually be built?
  • Which assumptions are safe?
  • What could fail?
  • How do we know the answer is correct?
  • Which trade-off is acceptable?
  • What evidence is enough to deploy?
  • What happens when reality differs from the specification?
  • Who is accountable for the result?

That is why “coding” and “software engineering” are not perfect synonyms.

A proud AI teammate presents a tall stack of generated code while a student checks requirements, security, tests, failures, data and recovery.

AII generated 8,742 lines and all tests pass.

EngineerNice. Why does the payment service need permission to delete users?

AI…excellent question.

Speed is useful. Understanding what just happened is useful too.

Frame → Verify → Own

What becomes more valuable when implementation gets cheaper?

  1. 1. Frame

    Can you explain the real problem, constraints, users, data, risks and definition of “done” before asking AI to solve it?

    Bad problem definition + faster code = faster wrong direction.
  2. 2. Verify

    Can you challenge a convincing answer with tests, evidence, edge cases, security reasoning and system knowledge?

    Confidence is not a test suite.
  3. 3. Own

    Can you justify the trade-off, explain the system when something breaks and take responsibility for what reaches real users?

    Someone still has to answer the 2:17 AM question: “Why did production do THAT?”

So… should you still learn software engineering?

No role is guaranteed safe, and yesterday's senior skill set is not automatically enough tomorrow. A better question is: what should I become good at as AI keeps getting better at implementation?

Do not train to beat AI at typing code. Train to understand systems well enough to frame the problem, challenge the answer, verify the evidence and own the result.

What to practise now

  • Understand the problem, business and domain before solving it
  • Know programming, algorithms and trade-offs well enough to understand what the code does
  • Reason about systems, architecture and data
  • Challenge assumptions with tests and evidence
  • Read unfamiliar code and investigate unexpected failures
  • Think about security, privacy, misuse and recovery
  • Communicate decisions and trade-offs
  • Use AI aggressively where it helps—within cost, security and governance constraints

The future job title may change. The tools will definitely change. The valuable part is becoming someone who can understand, decide, verify and build with those tools.

Continue the inquiry

Worried about AI? Good question. Investigate it properly.

Some routine implementation and small freelance work is already shrinking. Junior roles, senior expectations, team structures and the cost of continuous AI use are all changing. Examine the evidence and build an AI-resilient practice without pretending anyone knows the final shape of the market.

Evidence behind the deeper guidance: DORA · NIST NCCoE

Your next step starts here

What would help you today?

Pick one route. You can change direction later—no quiz, account, or perfect answer needed.

Already studying? Find a more specific starting point

Where are you right now?

New, undecided, worried about AI, or feeling behind? Choose what sounds like you today.

Feeling behind? You do not have to catch everyone. You just need to stop standing still. Make a realistic restart →

Before you choose anything

Take the pressure off.

  • CSE is a landscape, not one career.
  • Programming is a tool. A framework is not a career plan.
  • You can explore deliberately without deciding your whole life.

Your first direction is a draft, not a verdict.

The CSE career landscape

What does this work actually involve?

Explore different kinds of problems, daily tasks and trade-offs. Open a career that makes you curious—you are exploring, not committing.

Try before you choose

Would I enjoy doing this work?

Try a safe, 60–120 minute challenge. Check the prerequisites, try the work, and notice what interests you before committing to a longer learning path.

Try three expanding paths: analytics, AI and application security

A useful loop

What should I learn—and where can it lead?

Understand → Explore → Compare → Try → Prepare → Adapt

Open the six-step loop
  1. UnderstandFind your starting point.
  2. ExploreLook behind the job title.
  3. CompareCompare the trade-offs.
  4. TryGet a little real evidence.
  5. PrepareBuild your foundations.
  6. AdaptKeep learning as work changes.

A career roadmap explains what to learn. A goal guide helps you apply it. Choose a learning roadmap · Find a preparation guide

A meaningful next step beats a perfect plan

You do not need to have it all figured out.

Give yourself 20 minutes today: open one career, notice what interests you, and pick one thing to try. That is a real start.

Help Me Find My Next StepNo sign-up. No perfect answer required.