What to Say When a Student Doubts Themselves

"I'm just not cut out for this." Every TA hears some version of it, usually right after a bad grade or a long night stuck on one bug. What you say next matters more than it seems. Students often hear a TA's reply as a verdict from the field itself. This page gives you a short pattern for replying, ready-made lines for the statements you will hear most, a few replies to avoid, and the research on why this works. It is not counseling, and it does not take long: most good replies are three sentences and an offer to look at the work together.

Defaults that work. If you only take four things from this page:

Ask what happened before you reassure. A specific struggle can be fixed; a general verdict cannot.
Separate one grade or one course from the person and the field.
End with one concrete next step you take together, not only encouragement.
Praise the process, not the person: what they tried, not how smart they are.

A pattern for the reply

Ask what happened. "What has been going on that is making you feel this way?" The answer turns "I can't do CS" into "I didn't understand recursion on the last homework," which is something you can help with.
Name the belief, without agreeing with it. "It sounds like this has made you wonder whether you belong in the major." Students relax when they feel heard.
Offer another way to see it. One grade is one piece of information, not a forecast. Being stuck is what learning something hard feels like. Many people who are now good at this felt the same way, often including the TA in front of them.
Give one next step, together. "Show me the problem where you got stuck and let's find the first place it went wrong." Encouragement without a step leaves the student exactly where they were.

What you will hear, and what to say

"I'm just not cut out for CS."

"That's a hard feeling, and it's very common at this point in the major. What has been going on? Let's look at that part together."

"Everyone else already knows this."

"Students start this course with very different backgrounds, so some people are seeing it for the second time. That's a head start, not a difference in ability. Which part is new to you? Let's start there."

"I'll never be as fast as the others."

"Speed comes from practice, and right now you're comparing your first time with someone else's fifth. Being slower while you learn is normal. Let's pick one kind of problem and get it solid."

"I just need to work harder."

This one sounds healthy, and sometimes it is. But more hours with the same approach often fail, and then the student reads the failure as proof. Ask how, not how much: "Tell me what you do when you sit down to study for this. Maybe there's a different way in, not just more time."

"I got a C on the midterm. Maybe CS isn't for me."

"One exam is one data point, and it was written to find the hard spots. It doesn't predict whether you'll do well in the field. Bring it to office hours and let's find the two problems worth fixing first."

"I'm fine with the theory. I just can't code." (or the reverse)

"Those are different skills, and most people are ahead in one of them for a while. The theory you understand is real; now we build the other half. Show me a program you started, and let's see where the ideas stop turning into code."

"Maybe I should drop the course."

Take it seriously, and don't decide for them. "Let's talk about what's making you think that. Before you decide, it might help to talk with your advisor, and to look at what it would take to finish strong. Can I help you make a plan for the next two weeks?" Point them to their advisor and the instructor for the decision itself.

Careful with these

All of these are meant kindly, and all of them can land badly:

Agreeing with the belief. "Maybe it isn't for everyone" confirms the fear, even when you mean it as honesty. Ask what they enjoy first; the question of fit can come later, and from them.
Reassurance with no next step. "Don't worry, it'll get better" feels warm and changes nothing. Add one thing to do together.
"Just keep trying." More effort with the same strategy is the trap above. Point to a different way of working.
Praising talent. "But you're so smart!" makes the next struggle feel like proof they aren't. Praise what they did instead.
Your own story, at length. "I struggled too" helps in one sentence. Five minutes about you does not.

Why this works

Praise the process, not the person. In Mueller and Dweck's classic studies, children praised for intelligence did worse after a setback than children praised for effort. "You tried two approaches before asking" builds a habit; "you're so smart" makes the next struggle feel like a verdict.
High standards plus belief. In Yeager and colleagues' studies of "wise feedback," students were more likely to revise their work when critical feedback came with a short note: high standards, and confidence they could meet them. "I'm pushing on this because I know you can get it" is that note, out loud.
Belonging. In Walton and Cohen's study, first-year students who learned that worries about belonging are common and fade with time did better academically over the following years. Saying "most people feel this, and it passes" is a small version of the same message.
It's common in computing. A study of CS students at one large university found that more than half showed signs of impostor feelings, and later work found it across institutions and higher among women. In intro programming, teaching students about mindset and giving mindset-oriented feedback has improved test performance.

Reaching out first

Many students who are struggling never come to you. A short, personal note after a low score or missed work can bring them in. In one study, a few well-timed emails from professors with tips, an update on where the student stood, and a reminder they were available made students rate the course more positively, and raised grades for some groups. Check with your instructor first about who sends outreach and what it may say.

Write soon, within a few days, while there is still time to recover.
Keep it short and personal: what you noticed, one concrete next step, when and where you're available.
Pair honesty with belief: high standards, and confidence they can meet them. Don't guess at causes.
Make replying easy: a specific office-hours time or a link to book one.
One student per message. Never put grades in a group message.

After a low exam score: "Hi [name], I wanted to check in after Exam 1. Your score suggests some of the material hasn't clicked yet, which is common at this point, and plenty of students who start here finish well. The standard in this course is high because I think you can meet it. Could you come to office hours on [day and time], or book a time here: [link]? Bring the exam, and we'll go through the two questions that cost the most points."

After missed work: "Hi [name], I noticed Homework 3 and 4 haven't come in, and wanted to check in before it gets harder to catch up. If something is getting in the way, you don't need to share details. The course allows [late policy], and I can help you plan the next step. I'm in office hours [day and time], or just reply here."

When it is more than doubt

Sometimes "I'm not cut out for this" sits on top of something heavier: exhaustion, hopelessness, trouble outside class. If a student seems to be in real distress, or mentions hurting themselves, that is no longer a confidence conversation. Follow your campus's process for students in distress, and see Handle It or Hand It to the Instructor? for who to call.

Small habits that help every student

Learn names and use them.
Say out loud that being stuck is normal, before anyone is stuck, and again when they are.
Show your own process: when you hit a bug in front of students, debug it calmly and say what you are thinking.
Notice effort and strategy in your comments: "Good call testing the empty case first."