Nestack Technologies Pvt Ltd is accepting applications for Core Ops Intern in Hyderabad, Telangana. The employer advertises a monthly stipend of INR 12,000 and work supporting AI agents used in business workflows. Jobsii checked the official role, current careers listing and fully loaded application form on 17 October 2026. The form identifies the selected role as Core Ops Intern.
This opportunity is for final- or pre-final-year B.Tech students in specified technical disciplines who already have evidence of building with LLM APIs. It is not advertised as a no-skills internship or a general opening for every graduate. The total internship duration, joining date, application deadline and vacancy count are not disclosed.
The degree requirement is B.Tech in Computer Science, IT, AI/ML or Data Science, in the final or pre-final year. Applicants should demonstrate LLM API work, such as a hackathon agent or a RAG project on GitHub. Linux basics and curiosity under pressure are also listed. No minimum CGPA, graduating batch year or college category is specified.
LangChain or LlamaIndex experimentation and a CTF or hackathon record appear as nice-to-have experience. Do not turn those preferences into mandatory certifications. The role listing is labelled fresher, but it still expects practical project evidence. A candidate should be able to explain what they built rather than simply list tools or repeat terminology from a tutorial.
Nestack describes Agent Care as a 24/7 team that monitors, triages and supports AI agents running business workflows. Examples of problems include incorrect tool calls, hallucinated answers and injection attempts. The internship belongs to the L1 support bench. Applicants should understand that this is operational monitoring and troubleshooting, not exclusively model training or building new AI products.
The described learning path begins with one month of shift shadowing at the monitoring desk, followed by rotation into a domain team. That initial month is a training phase, not a stated end date for the whole internship. The employer mentions mentorship from engineers supporting live agent fleets but does not specify a guaranteed domain allocation or individual project.
The official benefit is a monthly stipend of INR 12,000 during the internship. Payment dates, deductions, attendance conditions and additional allowances are not detailed. Confirm the written payment terms before accepting. The listing mentions possible full-time conversion for outstanding performers; it does not guarantee a permanent offer, publish conversion criteria or state a future salary.
Hyderabad is the stated location. The vacancy does not explicitly confirm remote, hybrid or in-office arrangements, so this article does not market it as work from home. The team's 24/7 coverage also does not mean an individual intern works continuously. Exact shift allocation, daily hours, weekly days and any night-shift requirements need confirmation from the employer.
Use the employer's application link below, which opens the role-specific registration page. The live form shows three stages: application details, screening questions, and review and submit. No application was filled or submitted by Jobsii. Candidates should follow the current portal instructions and read any notices themselves before entering personal information or accepting terms.
The first stage asks for name, email, mobile number, current location, skills and educational details. It includes a required GitHub profile link and asks whether the applicant is available for an in-person interview if selected. That question is not a confirmed interview invitation or proof of a particular work arrangement. Answer it truthfully based on your actual availability.
The portal offers resume autofill using a PDF or Word document and includes optional portfolio and social-profile links. Education fields include institution, major, degree and percentage score. Screening questions were not inspected beyond the first stage, so their contents are not asserted here. Review every step carefully and keep any acknowledgement after submitting your own application.
The following suggestions are independent editorial guidance, not additional employer eligibility conditions or a confirmed assessment syllabus. Choose one LLM API project you genuinely understand. Explain its purpose, your contribution, inputs, outputs and limitations. Distinguish your implementation from library functionality and identify which parts were built by teammates, if it was a group project.
For a RAG example, describe the source material and how information reaches the final answer at a high level. Explain what you checked when an answer was unsupported or irrelevant. Do not claim that a system is reliable merely because it produced convincing text. Use synthetic or appropriately public information, not confidential customer records or private documents from another organisation.
Create a fictional incident note describing a symptom, time observed, affected task and evidence available. Separate confirmed facts from possible causes and explain what you would ask a supervisor to clarify. A useful handover lets another person understand the issue without reconstructing a long conversation. This exercise demonstrates communication; it is not Nestack's actual incident procedure.
When practising with your own test application, keep troubleshooting within systems you control or are authorised to use. Do not test attacks against a company, expose private prompts or alter a live workflow to create a portfolio example. Discuss how you would recognise unexpected behaviour, preserve relevant evidence safely and escalate when the impact is unclear.
Review the Linux skills you have actually used and prepare to explain a practical task or debugging example. Organise your project so another person can understand its setup and dependencies. Keep API keys out of repositories and screenshots. Do not add operational experience you lack simply because the role mentions production agents and a monitoring desk.
A short project readme can explain what works, what remains unfinished and how you checked a representative result. Describe errors you encountered and the changes you made. Academic and hackathon projects can provide relevant evidence when presented honestly. A polished demonstration should not conceal unresolved failures or imply that a prototype has handled real customer traffic.
Discuss examinations, class commitments and the actual shift schedule before agreeing to the placement. Ask how shadowing, mentoring and the later domain rotation are organised, and how questions or incidents are escalated. Clarify whether attendance in Hyderabad is required. Do not assume that a team operating around the clock offers an entirely flexible internship schedule.
Before accepting, confirm total duration, start date, hours, work mode and stipend payment terms in writing. Evaluate the internship on those conditions rather than a possible permanent conversion. Recheck the official role before applying because no deadline is published. Jobsii provides opportunity information and does not collect applications, make hiring decisions or guarantee selection.
Review the role details, deadline, and work mode before applying. Jobsii tracks the apply action so candidates can keep application history inside their dashboard.
