Every RIT co-op begins with an interview. Walk into it having already done it.

The four questions every RIT co-op interview opens with. Get these clean before you go deep.

• Tell me about yourself — RIT edition

  Open a co-op interview with a sharp intro that connects your RIT track to what this employer actually needs.

  5 turns · recruiter

• Why this company — the co-op version

  The question that filters students who researched from students who didn't. Sound like you meant to interview here.

  5 turns · hiringManager

• Walk me through your hardest project

  Where your ownership, judgment, and technical range get read at the same time. Answer this well and the rest of the interview is easier.

  5 turns · hiringManager

• Compensation + timing conversation

  Hold your number without deflection when the recruiter asks about pay and start dates. The awkward moment they use as a filter.

  5 turns · recruiter

The questions almost every interview includes — hard bug, disagreement, project that failed, learning fast. What most tools skip.

• Tell me about a difficult bug

  Behavioral classic. Interviewer wants to see how you actually debug, not the tidied-up postmortem version. Practice narrating the mess.

  5 turns · behavioralPanel

• Describe a disagreement with a teammate

  Filters for whether you can hold a position AND change your mind. Interviewers watch for defensiveness, blame, and whether you actually learned from it.

  5 turns · behavioralPanel

• Tell me about a project that failed

  The failure question. Interviewers want ownership language: what YOU missed, what YOU'd do differently — not what the team, the tools, or the client got wrong.

  5 turns · hiringManager

• Explain a time you learned a new technology quickly

  Filters for how you actually onboard onto unfamiliar tech. Interviewers care about your first-week playbook — what you read, who you asked, what you shipped.

  5 turns · hiringManager

Git, code, live-thinking, DSA, OO design, code review, SQL, system design, debugging. What employers actually screen for at the tech interview step.

• Git-readiness screen (code-linked)

  Paste your GitHub. We grade your actual commit history against the co-op interview bar: PR sizes, commit-message craft, main-branch stability, collab signals. Evidence-anchored — cites real commits and PRs.

  0 turns · engineerScreener

• Code & stack evaluation

  Technical screen tuned to the role — talking through your stack, your choices, and your code under real pushback. Find where your explanation loses the interviewer.

  6 turns · engineerScreener

• Live coding warm-up (think out loud)

  Practice narrating your problem-solving in real time. Not a coding test — a rehearsal for the moment when your fingers stop and the interviewer needs to hear your thinking.

  6 turns · engineerScreener

• System design — the junior version

  How you'd structure something moderately complex without whiteboard theater. Employers ask this earlier than students expect.

  6 turns · engineerScreener

• Debugging out loud

  Interviewer describes a bug. You narrate how you'd find it. Filter for how you actually think when something goes wrong.

  6 turns · engineerScreener

• DSA — narrating an algorithm live

  The interviewer gives you a classic data-structures problem. You don't code — you narrate the approach, complexity, and trade-offs the way you would on a whiteboard.

  6 turns · engineerScreener

• Object-oriented design — design a system

  The classic 'design a library' / 'design a parking lot' interview. Interviewer probes your classes, interfaces, and extensibility choices.

  6 turns · engineerScreener

• Code review — critique what you see

  You're shown a small piece of code. Interviewer asks what's wrong, what's ambiguous, what you'd change. Filter for whether you can be a reviewer, not just an author.

  6 turns · engineerScreener

• SQL interview — writing queries out loud

  Common for data-adjacent co-ops. Interviewer gives you a schema, asks a business question, you narrate the SELECT / JOIN / GROUP BY without writing code.

  5 turns · engineerScreener

Career Fair booth, MSD defense, project defense, take-home defense — the interview shapes RIT students face that most tools skip.

• Career Fair Speed Round (UWCF booth)

  3-5 minutes at a University-Wide Career Fair booth. Line behind you. Recruiter has seconds to remember you or not.

  4 turns · careerFairRecruiter

• MSD / Senior Project defense

  Employers ask about this in every KGCOE and GCCIS interview. Defending a 12-month team project where you owned one specific piece.

  6 turns · projectDefenseReviewer

• Personal project defense

  Solo project on your resume — no team to hide behind. Interviewer probes your architecture, your decisions, and what you'd change now.

  6 turns · projectDefenseReviewer

• Take-home defense (post-submission interview)

  You submitted a take-home. Now the interviewer walks you through your own code and asks about specific lines and decisions. The trap is defending choices you didn't consciously make.

  7 turns · projectDefenseReviewer

Employers now assume you use AI. What matters is how you talk about what you own vs what the AI helped with.

• AI disclosure — what did you build vs what did the AI build

  The question every employer now asks. Practice defending your work when the interviewer assumes AI helped and wants to know exactly where.

  6 turns · hiringManager

• Why this stack — defending choices under pressure

  The interviewer picks a decision you made and asks why. Not hostile, but persistent. Practice defending choices without falling into 'that's what the tutorial said.'

  6 turns · engineerScreener

Drills sharpened for your major — CS, SWE, Cybersecurity, Game Dev, Data Science, Computer Engineering, HCI.

• Full-stack build narrative (CS / SWE)

  For CS and Software Engineering students. Walk through a complete build front-to-back: architecture, data model, deployment, testing, real users.

  7 turns · engineerScreener

• Cybersecurity — clearance readiness + CTF narrative

  For Computing Security students. Defense-industry pipeline. Practice the CTF story, red/blue team thinking, and clearance-readiness questions.

  7 turns · hiringManager

• Game Dev — portfolio walkthrough

  For Game Design & Development students. Talk through a portfolio piece with a studio hiring manager who's played dozens of demos this week.

  6 turns · hiringManager

• Data Science — model choice defense

  For Data Science students. Walk through a project's model selection: why this algorithm, what alternatives you tried, how you validated, what you'd do differently.

  6 turns · engineerScreener

• Computer Engineering — hardware/software interface

  For KGCOE Computer Engineering. Talk through where software meets hardware — embedded C, timing constraints, FPGA, memory management under real limits.

  7 turns · engineerScreener

• HCI — user research defense + design critique response

  For Human-Computer Interaction students. Practice presenting research findings and defending design choices when the interviewer disagrees.

  6 turns · hiringManager

• The 'between co-ops' transition narrative

  You just finished a co-op. Now you're interviewing for the next one. Practice bridging the story without sounding like you're job-hopping.

  5 turns · hiringManager