CATAAM is accepting applications for a Security Research Intern in Pune with a hybrid schedule and an advertised stipend of INR 30,000–50,000 per month. The role combines vulnerability and detection research, scripting for internal tools, and technical writing. Applicants need to be based in or near Pune and able to attend the hybrid arrangement.
Jobsii checked the employer's careers index, linked vacancy and public application form on 30 October 2026. The role remained listed and its form was available. The posting does not disclose a closing date, internship duration, start date, number of openings or weekly hours. The top of the stipend range is not a promised offer for every applicant.
The employer asks for a current CS, security or related degree, or equivalent self-study; practical scripting in Python, Go or JavaScript; and security fundamentals. Applicants should have public GitHub work, CTF history or projects to share. Cloud-security or compliance-framework experience is desirable rather than a stated essential qualification.
The vacancy gives no numerical marks cutoff, graduation-batch restriction or mandatory number of employment years. Its practical evidence requirement still matters. The public form also includes a declaration that the applicant is authorised to work in India.
CATAAM's careers page describes a platform combining compliance automation, breach simulation and attack-surface management. It lists this position within its internships section and identifies a growing hybrid team in Pune. The site's footer names TheMarkups Canada Inc.; applicants should confirm the contracting entity in their eventual offer.
Use the official vacancy form linked below. It asks for contact and location information, LinkedIn, GitHub and portfolio links, a resume and an optional note. The resume formats shown are PDF, DOC or DOCX, with a 5 MB maximum. Jobsii inspected the form without uploading a document or sending an application.
Interview rounds, assessment tasks and response dates are not published. The following preparation sections are Jobsii's editorial guidance, not a CATAAM assignment, selection rubric or description of unpublished interview questions.
Choose a few strong items rather than sending an unexplained collection of repositories. For each item, make the purpose, your contribution, the result and the limitations easy to find. A reviewer should be able to understand the evidence before deciding whether to run anything.
One useful item is a short research note from a training environment or system you are authorised to assess. State the scope and the question you examined. Explain what you observed, what evidence supports that observation and what remains uncertain. If you relied on a public tutorial, identify it and distinguish your own work from the supplied exercise.
Finish the note with a proportionate remediation suggestion and explain how you checked it. A result that you could not reproduce is worth discussing honestly. Clear boundaries between an observation, a suspected cause and a verified conclusion demonstrate judgement without overstating the severity of a finding.
A second item can demonstrate how you turn messy information into a usable result. For example, create a small synthetic asset inventory containing duplicate identifiers, missing ownership fields and inconsistent labels. Write a local script that normalises the records, identifies the issues and produces a readable summary.
Use this synthetic inventory as a preparation exercise to demonstrate practical programming and careful treatment of incomplete information. Explain why you chose the input format and how a reviewer can reproduce the output.
Document the expected input, dependencies, command to run and output format. Explain how the script handles an empty file, an invalid record and conflicting duplicates. Keep example input and expected output together so another person can follow your reasoning. If a field is unknown, preserve that uncertainty rather than silently inventing a value.
When discussing the example, explain one design choice and one trade-off. A short, understandable script with clear failure messages can provide more useful evidence than a larger tool whose behaviour you cannot explain. Use the language you understand best among the relevant scripting options.
Technical writing is explicitly part of the role, so make at least one sample readable without specialist knowledge of your project. Open with the question, describe the evidence and explain what action the reader could reasonably take. Keep unsupported claims out of the conclusion.
For instance, a report about your synthetic inventory could distinguish an administrative data-quality problem from evidence of a security weakness. Explain why a missing owner needs investigation without presenting it as proof of a compromise. This gives a reviewer something concrete to assess: your ability to describe uncertainty and avoid exaggerated conclusions.
Keep sensitive data and credentials out of public samples. Where an existing project cannot be shared, prepare a sanitised explanation of your contribution and state what you can demonstrate. Do not imply that confidential work is publicly available when the link only leads to a private repository.
Organise your evidence around the advertised work: research, scripting and communication. For a repository, identify what you built; for a CTF entry, explain what you learned; for a write-up, show how you reached the conclusion. Make sure the links open as intended and that the resume stays within the form's size limit.
The optional note can briefly connect your strongest example with this role and explain your Pune availability. There is no published requirement for a long cover letter or a particular certification, so avoid treating either as an employer instruction.
Ask for the internship duration, working hours, office attendance pattern, reporting location, start date and stipend amount in writing. The posting does not explain how an individual stipend is chosen within its range, or specify accommodation and travel support. Do not build a relocation budget around benefits that have not been offered.
Clarify supervision and what work can later be discussed in a portfolio. These questions help assess the opportunity without assuming a permanent-job conversion, certificate or extension that the vacancy does not promise.
Official Security Research Intern vacancy and application form
Review the role details, deadline, and work mode before applying. Jobsii tracks the apply action so candidates can keep application history inside their dashboard.
