QA Intern

QA Intern

Duration: 3 to 6 months, with a full-time offer for the right person

About Samaaro

Samaaro is an AI-powered event marketing platform. Companies use us to run their events end to end: registration, event websites, attendee apps, on-ground check-in and badge printing, and reporting on what the event actually delivered.
That means when something breaks on our platform, it often breaks in front of three thousand people standing in a queue at a real venue. QA is not a formality here. It is the last check before a client's event goes live.
We are a small team and the QA function is still being built, so you will see how it is put together rather than inheriting a machine that already runs.

What you will actually do

Most of your time, especially in the first few months, goes into manual testing:

Run test cases across our core product and our client-specific deployments, before every release
Write clear bug reports in Jira that a developer can act on without asking you a single follow-up question
Re-test fixes and confirm nothing else broke along the way
Test on different browsers, screen sizes and devices
Help build and maintain our test case library as new features ship
Sit in on release discussions so you understand what changed and why
Support the QA team during client events, when things move fast
As you settle in, you will also start working on automation alongside the team:

Learn how our automated tests are structured and what they cover
Write and maintain simple automated scripts for flows that get tested over and over
Understand how automated tests fit into our release process

Being straight with you: a large part of this job is running the same checks again and again. Some weeks that is most of your day. It is careful, repetitive, detail-heavy work, and it is exactly what keeps our clients' events from falling over. If that sounds dull to you, this is not the right role, and we would rather you know that now.

Manual first, automation next
We take both seriously, and the order matters.

Manual testing is where you learn the product, learn what "correct" looks like, and develop the instinct to notice when something is subtly wrong. Automation cannot teach you that, and automated tests written by someone who has not done the manual work tend to check the wrong things. So you start with manual, and manual stays the bigger part of your day for most of the internship.

Automation is where the role goes next, and it is a real part of what you will do here, not a someday promise. Once you know the product well, you will start writing scripts for the flows we run every single release. You do not need any automation experience to apply and you will not need to write code on day one. You do need to find the idea genuinely interesting rather than something you hope to avoid.

What we are looking for

Non-negotiable:

You notice things other people walk past. Wrong date format, misaligned button, inconsistent spelling, a number that does not add up
You can write clearly. Most of this job is explaining a problem so someone else can understand it
You are patient with repetitive work and have your own way of staying accurate on the last twenty checks, not just the first twenty
You ask questions instead of guessing, and you ask them early
You are comfortable saying "I am not sure if this is a bug, but it looks off"
You are open to learning some code, enough to write and read basic test scripts

Good to have, not required:

Any exposure to manual testing, in a job, internship, college project, or helping a friend's product
Basic understanding of how web apps work
Familiarity with Jira, or any bug tracking tool
Any programming basics, in any language
Basic SQL or Postman
A degree in computer science or a related field
We are not expecting you to know testing terminology, hold a certification, have prior QA experience, or have written automated tests before. We will teach you the craft. We cannot teach you to care about small broken things.