Quick heads up: This is based on my experience at SRMIST KTR. The process, structure, and specifics might
be different at other colleges. Take this as one person's perspective, not a universal guide.
Let me tell you about Samsung PRISM - not the polished version you see on posters, but what it's actually
like. Most students I talk to have the same questions: How do you get in? What do you actually do? Is it worth
it?
So here's everything, unfiltered.
The Selection Process
PRISM opens applications through a Google Form, usually shared in college groups. You fill it, submit it, and
then... you wait.
Round 1 happens at your university. It's an objective test, but here's the catch - you can't
just tick answers. Every question needs rough work, detailed reasoning. This round cuts 60% of applicants.
Round 2 is where Samsung gets directly involved. Three coding problems. Timed. Online. You
solve what you can, submit, and then there's this long silence - sometimes 45 days, sometimes more. No scores.
No feedback. Just waiting.
When you do get selected, it's usually through a WhatsApp group. Not an email. Not a call. A group add.
That's PRISM for you - real, unpolished, straightforward.
What Actually Happens After Selection
You get put into a team of four students. You also get two faculty mentors from your university and industry
mentors from Samsung. This isn't optional - this is your team for the entire program.
Each team gets a real research problem from Samsung. A problem Samsung actually cares about solving. And you
sign NDAs - proper legal documents - before you even see the problem statement.
Here's what most people don't realize: This isn't an internship. It's research engineering.
The Reality of Working in PRISM
When you start, you think "okay, two months, we'll finish this." You won't.
Not because there's too much work, but because Samsung's expectations are different. They don't want
something that works. They want something deployable. Something that can go into production. Something that
solves the problem properly.
You have weekly reviews with your faculty mentors and monthly reviews with Samsung engineers. In these
reviews, you defend every choice. Every assumption. Every line of your approach. "Why did you do it this way?"
"What happens if this fails?" "How does this scale?"
At the end, you don't just submit code. You submit a research paper. Yes, actual publication. That's part of
the program. Your work needs to be documented.
What You Get Out of It
Let's talk perks first:
- Participation Certificate + goodies on completion
- Certificate of Excellence + ₹15,000 stipend (if your mentors approve your work)
- Eligibility for Samsung SRIB Magpie (next level program)
- Counts as your industry project requirement
- Can replace one professional elective
But honestly? The real gain isn't the stipend or the certificate. It's that you learn how to build things
that actually matter.
Should You Apply?
Look, PRISM isn't for everyone, and that's okay. Here's how to know if it's for you.
Apply if:
- You like working on one thing deeply rather than many things superficially
- You want to understand how real product engineering works
- You're okay with ambiguity and figuring things out as you go
- You care more about learning than collecting certificates
- You want actual industry mentorship, not just project guidance
Skip it if:
- You want quick wins and fast turnarounds
- You prefer clear instructions over open-ended problems
- You're only doing it for the stipend or resume line
Final Word
Getting selected for PRISM is one thing. What you do with it is another.
It's not going to be the easiest project you do in college. But if you're someone who wants to build things
that actually work in the real world, understand how industry thinks about problems, and learn what it means
to commit to something meaningful - PRISM might be exactly what you need.
The form will come. You'll have to decide if you want to fill it. At least now, you know exactly what you’re
signing up for.
