From Campus to Career
Placement preparation stops at the offer. The job starts after it.
Everything your students are being prepared for ends the day they are selected. This session covers what happens next — the first ninety days, managers, feedback, mistakes, deadlines and the habits that quietly decide the first two years — described by people who made the transition recently enough to remember it.
In college the path is visible. At work, nobody hands you the syllabus.
Students know what to study, when the exams are, what the syllabus contains and how marks are awarded. Then the questions change entirely: what does my manager expect, how do I know if I am doing well, how much should I ask, what happens when I make a mistake, how quickly am I supposed to learn?
These things become obvious after two years and are nearly invisible before. That gap is the whole session — and it is the part placement preparation almost never covers.
What actually changes
73 topics across 14 areas. Fourteen things that surprise almost everybody.
Nobody Expects You to Know EverythingThe first job is another learning environment.7
Experienced people search for answers, read documentation, ask colleagues and change their approach. The expectation is not knowledge; it is learning.
- Learning company systems
- Understanding the product
- Learning the processes
- Reading documentation
- Shadowing teammates
- Making mistakes
- Asking questions
How to Ask a QuestionThere is a difference between two versions of the same request.5
“This isn't working, what should I do?” against “I'm seeing this error. I checked the logs, tried these two approaches, and think the issue may be here — what am I missing?”
- Understand the problem first
- Try reasonable approaches
- Check the documentation
- Note what you already tried
- Say clearly where you are stuck
Asking is not weakness. Asking the same question repeatedly without learning from the answer is the actual problem.
Communication Decides More Than You ExpectYou can be capable and still struggle if nobody knows what you are doing.6
- Explaining progress
- Writing professional emails
- Participating in meetings
- Speaking with customers
- Explaining a technical problem
- Saying when something will be late
Give UpdatesDo not disappear with a task.4
“I finished the first part, I'm on the API integration now, I hit an authentication issue and I'm investigating — I'll update you tomorrow afternoon.” That single habit prevents most early trouble.
- What happened
- What is happening now
- What the problem is
- What comes next
Deadlines Work DifferentlyA late assignment costs marks. A late delivery costs customers.6
If something will slip, say so early: “this is taking longer because of X. I can finish A today, B may take until tomorrow — or should I change priorities?”
- Customers
- Other teams
- Sales
- Operations
- Product launches
- Revenue
Estimate Carefully“I'll finish it in two hours” is a promise, not a guess.5
- Understand the task
- Identify dependencies
- Ask questions
- Account for testing
- Allow for unknowns
Your Manager Cannot Read Your MindOne question prevents hours of wasted work.6
“Before I start, can I confirm what the expected outcome is?”
- Priority
- Deadline
- Expected output
- Quality bar
- Format
- Who owns what
Feedback Is About the WorkYour code will be reviewed. Your design may be rejected.4
- What specifically needs improvement?
- What should I do differently?
- Can you show me an example?
- How do I avoid this next time?
“This needs to be redone” is not “you are bad at your job”.
Do Not Hide MistakesSmall problems grow in the dark.5
- Understand what happened
- Tell the relevant person
- Explain the impact
- Help fix it
- Say what will change
Managers overwhelmingly prefer hearing it from you first.
Ownership Is Not Doing It AloneIt means moving something forward.7
- Asking for clarification
- Following up
- Escalating a blocker
- Coordinating with another team
- Finding information
- Communicating progress
- Asking for help
Small Tasks MatterHow you handle them decides what you get next.4
Fixing small bugs, testing features, updating documentation and preparing reports feel insignificant — and they teach you how the system, the team and the customer actually work.
- How systems work
- How teams work
- How customers use the product
- How the organisation operates
Learn the Business, Not Only the TechnologyThe work exists because somebody needs something.6
- Who the customer is
- What problem the product solves
- How the company earns money
- What your team contributes
- Why a feature matters
- What happens when it fails
Do Not Compare Too EarlyOne friend joins a bigger company. Another earns more.5
The first two years are not a race with your classmates. Better questions to ask yourself.
- Am I learning?
- Am I building useful skills?
- Am I taking responsibility?
- Am I getting better?
- Am I moving towards work I want to do?
Three Sentences Worth LearningThey cover most of the first year.3
“I don't know — I'll find out and update you by four.” “I've tried these things and I'm stuck, can you help?” “I can take this on, but the report due tomorrow moves — which should I prioritise?”
- Honesty with ownership
- Asking after genuinely trying
- Saying no by making the trade-off visible
Questions to ask the professionals
- What surprised you most about your first job?
- What was harder than you expected?
- What did college prepare you well for?
- What did it not prepare you for?
- What mistake did you make early?
- Which skill mattered more than you expected?
- What did you misunderstand about managers?
- What would you tell yourself in your final semester?
Habits worth starting in month one
- Take notes — you will be told things once
- Document decisions, requirements and outcomes
- Keep a record of what you worked on and what came of it
- Understand why a meeting exists and what you own afterwards
- Apply what you learn before starting another course
- Start on money early: budgeting, savings, an emergency fund, taxes
- Protect sleep, food and the people outside work — a career is long
Your first job does not decide your career
- People move between roles, industries, technologies, companies and countries
- Starting in testing, support or operations does not fix anything permanently
- Ask periodically: am I learning, is there responsibility, is the environment healthy, can I grow?
- Decide thoughtfully rather than out of frustration or comparison
How the session runs
Young professionals describe what actually happened in their first ninety days, then each names something they were not prepared for and a mistake they made early. The room hears what mattered more than expected — usually communication, documentation, relationships and reliability rather than technical depth. Open questions follow, and each speaker closes by answering what they would tell themselves six months before starting.
What your students leave with
- A realistic picture of what the first months actually feel like
- The understanding that nobody expects them to know everything
- How to ask a question that gets a useful answer
- Why communication decides more than technical skill early on
- How to receive feedback without treating it as a verdict
- What ownership means, and what it does not
- Why career comparison in the first two years is a trap
- Habits worth starting in month one rather than year three
Scheduled sessions
Nothing scheduled yet
Sessions are arranged with a college once a date is agreed. Ask us and we will find the right person for it.
A student rather than a college? See what is coming up, or ask your placement team to host this.
Getting the job is a milestone. Becoming good at it happens afterwards.
Tell us who your students are and what stage they are at. Sessions are free for participants.