Academic snapshot
Marks: 7.5+ CGPA / 75% (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Reliance Industries is India’s largest private sector company with interests in petrochemicals, refining, oil, telecommunications, and retail. Founded in 1966 and headquartered in Mumbai, it recruits engineers for Jio Digital, RIL IT, and core graduate engineer trainee roles. Reliance offers diverse technology careers across telecom, retail, and energy businesses.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus IT / Jio Digital | Batch OA, PPT, college CGPA list | Aptitude speed + coding bar |
| Campus GET / core | Written aptitude + branch paper | Location/shift questions in HR |
| Careers portal / referral | Resume screen volume | Still expect the BU’s filter |
| Intern (e.g. NIT-style) | Written + one technical in TPO office | Panels may already know shared projects |
If your CGPA sits near 7.5, spend energy on the 12-minute clock (IT) or core orals (GET), not on hunting a mythical 7.0 cutoff.
Which notice did you actually get? “Reliance” on a WhatsApp TPO blast can mean Jio Digital, RIL corporate IT, a refinery GET drive, or a retail/digital cousin. Screenshot the PDF: role title, branches, CGPA, test duration. If it says 12 minutes aptitude, your week is a timer. If it says chemical written + document verification, your week is core + marksheets. Same brand, different exam.
Is 7.5 CGPA enough? It matches the commonly reported floor. Selection still hinges on OA/written accuracy and interview narration. A 7.6 with clean timed aptitude beats an 8.8 that panics at 15 questions in 12 minutes.
Branches: CS/IT/ECE/EE dominate IT lists. Chemical, mechanical, electrical, and other core branches dominate GET. If your college lists only “circuit + CS,” do not assume chemical is auto-included (or the reverse).
Gaps and backlogs: Active backlogs are the usual blocker. GET HR often probes Reliance vs PSU and why not research - have a real answer.
What helps the resume screen: One project you can defend (Jio-like product or plant-design), internship ownership language, and honest keywords. Certificates are optional. See certifications after fundamentals.
Academic snapshot
Marks: 7.5+ CGPA / 75% (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Branch & skills
IT / Jio: CS / IT / ECE / EE
GET: Core branch as listed
Languages (IT): C, C++, Java, Python
Differentiator: Jio platforms or plant/project depth
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.5+ CGPA / ~75% across 10th, 12th, graduation | Some notices mirror college norms |
| Degree | B.Tech / B.E. / M.Tech / MCA | Full-time degrees usually |
| Branch | CS, IT, ECE, EE (IT) or core (GET) | Read the BU list |
| Year | Final year + recent grads (~1-2 years) | Intern conversions also appear |
| Backlogs | No active backlogs | Clear before paperwork |
| Gaps | Typically max 1-2 years | Explain with a skills story |
Minimum CGPA required (candidate-reported): 7.5+ CGPA / 75% is the commonly cited campus floor. Treat it as a shortlisting filter when printed. Clearing CGPA only gets you into the funnel - the 12-minute aptitude slice or the core written decides a lot of shortlists.
Reliance does not publish one universal cutoff across Jio Digital, RIL IT, and GET. Your mailer always wins.
Download 2026 Reliance placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Reliance does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Aptitude slice | Speed on ~12 min / 15-20 Q (when that format appears) |
| Full OA | 60-90 min mix: aptitude + technical MCQ + 1-2 coding |
| Technical (IT) | Arrays/strings, OOP, Java/SQL, Jio platform talk |
| Technical (GET) | Branch orals + plant/project defence |
| HR | Why this BU?, location/shifts, long-term plans |
Aptitude PDF vs full OA: packs on this site are built so you can time a quant + LR + verbal block. That matches the 12-minute story. It does not replace Java/SQL orals or a chemical written. Use the PDF for speed; use nested coding and interview pages for the rest.
| Theme you saw in a set | What to drill next | Why Reliance asks it |
|---|---|---|
| Percentages / ratios | Profit-loss, CI/SI under 60s | Aptitude speed |
| Syllogisms / puzzles | Seating, blood relations | 12-min LR slice |
| RC / grammar | One timed verbal set | Sectional cutoff insurance |
| Rotate array / unique char | Two pointers, frequency | IT OA coding |
| Stack min / valid parens | Stack templates | Fundamentals orals |
| Kadane | Running sum | Easy-medium coding |
| Prime / sort vs library | Loop bounds, complexity talk | GET+IT crossover |
Reliance group hiring for freshers runs through campus cells (RIL, Jio Digital, other BUs) and the careers portal. After resume screen, IT looks like aptitude + coding + two technicals + HR. GET looks like written + core oral + HR.
Campus recruitment
Through college placement cells - PPT, then OA/written and interviews on a batch timeline.
Online applications
Apply on ril.com (and related group careers) for early-career / GET / IT roles; follow the invite.
Referrals
Employee referrals improve visibility. You still need the aptitude/coding or core bar.
Degree, CGPA floor when printed (7.5+ / 75% commonly reported), backlogs, year of passing. Projects help. This is a gate - the OA is the volume filter.
Candidate reports commonly describe a 60-90 minute proctored test. Some drives isolate aptitude into ~12-15 minutes / 15-20 questions. Treat the table as a working map.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude | ~15-20 | ~12-15 min on some drives | Quant, LR, verbal |
| Technical MCQ | ~10-15 | ~20-25 min | Programming, DS, DBMS |
| Coding | 1-2 | ~15-20+ min | Arrays, strings, basic algorithms |
| Total | ~30-40 | 60-90 min | Sectional cutoffs may apply |
Languages: C, C++, Java, Python. Negative marking: usually none in student notes - still do not guess-spam if your invite says otherwise.
Pass bar: Speed + accuracy on aptitude; at least one fully passing coding solution when coding is present. Some write-ups cite ~30-40% clearing OA - colour, not a promise.
Student tip: If aptitude is 12 minutes, skip a sticky puzzle at second 40. Bank 10-12 clean answers. Then code the obvious array/string first.
Worked 12-minute triage (15 questions): Q1-Q4 percentages/ratios - do immediately. Q5 long seating puzzle - star and skip. Q6-Q8 syllogisms - 20 seconds each; if the Venn is messy, skip. Q9-Q11 verbal - RC last if the passage is long; grammar first. Q12-Q15 leftover quant. You are not trying to be a CAT topper. You are trying to not zero a sectional cutoff because you married one puzzle.
| Minute | Move |
|---|---|
| 0-1 | Skim all 15-20; mark sitters |
| 1-8 | Quant + easy LR; skip long puzzles |
| 8-11 | Verbal / leftover sitters |
| 11-12 | Guess only if no negative marking and time remains |
Deeper OA notes: Reliance Online Assessment. Full aptitude bank: aptitude questions.
IT: basic array/string coding, OOP, DBMS/SQL, project warm-up. GET: core subjects, plant or lab project.
You should narrate constraints → approach → code or derivation → edge cases. Silent staring is a common reject signal.
IT: deeper Java/SQL, Jio platforms in plain language (scale, APIs, what breaks), project trade-offs. GET: design choices on a plant project, safety/ops awareness at fresher depth.
Worked mini-outline - Jio-like subscriber lookup (fresher):
Second mini-outline - recharge / plan change: user pays → payment confirm → entitlement row updates → cache key for that MSISDN dies → next app open reads new plan. If payment confirms and entitlement write fails, you need a retry or a support-visible “pending” state - not a silent old plan. That is fresher depth and maps to both Jio Digital and generic IT orals.
SQL oral you should not skip: one join (customers ↔ recharges), one GROUP BY (recharges per day), one index intuition (“we look up by mobile number a lot”). Interviewers still open a lot of Reliance IT panels with this after the coding warmup.
Why this business unit (not “largest private company” only), location flexibility, shifts for some GET roles, joining vs exams. Know the ₹12-20 LPA IT/Analyst band so CTC talk is grounded.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA / written | 60-90 min (or longer GET paper) | Speed + accuracy |
| 2 | Technical 1 | 45-60 min | Fundamentals + code/core |
| 3 | Technical 2 | 45-60 min | Domain + projects |
| 4 | HR | ~30 min | Location, motivation |
GET/intern loops may drop to written + one technical + HR. An NIT Jalandhar intern write-up: 45 took the written, 11 interned.
Document verification showed up on the IIT Jammu GET path between written and panel. Keep 10th/12th/grad marksheets, ID, and backlog-clear proofs in one folder. A clean OA does not save you if paperwork stalls the offer.
Anti-cheating colour: the NIT intern technical ran on Microsoft Teams inside the TPO office. If your college does the same, assume the panel can see shared project groups and last-week Git spikes. Explain your slice of a group project in 60 seconds before they ask.
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT then OA/written |
| OA → shortlist | Few days to a week | Intern notes: within a week |
| Interview loop | ~1-2 weeks | Sometimes same-day technical + HR |
| Offer / paperwork | Days after final round | Written offer wins |
| End to end | ~2-3 weeks campus often | Off-campus can stretch |
| Component | Focus | Prep move this week |
|---|---|---|
| 12-min aptitude | Skip discipline | Daily timed 15-20 Q |
| Technical MCQ | DS, DBMS, OOP | Short flash + mock quiz |
| Coding | Arrays/strings | Two easy-mediums |
| Jio / IT interview | Java, SQL, platforms | 3-minute flow aloud |
| GET interview | Branch + project | One plant story + PSU comparison |
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Reliance invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Reliance sits around ₹12-20 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Reliance eligibility for freshers 2026 is candidate-reported. Common baseline: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, EE, or related fields (core branches for GET/plant roles); final-year students and recent graduates; typically 7.5+ CGPA / 75% across 10th, 12th, and graduation; no active backlogs. Requirements vary by Jio Digital vs RIL IT vs GET. Always verify the drive notice.
What you are training for: Candidate-reported loops commonly run: Online Assessment (60-90 min, aptitude + technical + coding) → Technical 1 (45-60 min) → Technical 2 (45-60 min) → HR (~30 min). Some GET/intern drives use a written test then a single technical + HR. Campus batches often finish in about 2-3 weeks.
Short version of the prep split: Split time roughly: 40% aptitude speed (including 12-minute drills), 30% coding/CS (arrays, strings, OOP, SQL), 15% domain (Jio platforms or core engineering), 15% behavioral/HR. For GET/core, swap most coding time into branch subjects. Languages: C, C++, Java, Python.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Reliance previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Reliance drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Reliance usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Reliance?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Reliance-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Reliance story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Reliance papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Reliance papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Reliance-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Reliance paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Reliance. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on BU (Jio Digital vs RIL IT vs GET), location, and written components.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer / Analyst (fresher) | ₹12-20 LPA | Primary IT band for this hub |
| GET / core | Varies by site and year | Do not assume IT CTC |
| Intern stipend | Drive-specific | Written letter wins |
| Mid-level | Higher | Outside fresher default |
Confirm base, bonus, and benefits on the written offer. Do not treat blog midpoints as guarantees.
Policies vary by BU and year. Candidates commonly care about:
Know the ₹12-20 LPA IT/Analyst context, ask how the package splits, and clarify joining vs exams and posting location. One calm question beats arguing a Jio Digital screenshot on a GET letter.
GET vs IT letters: do not paste a Bengaluru Jio Digital CTC into a site GET negotiation. Ask posting city/site, shift expectations, and probation language. Intern stipends are a different letter again - the NIT write-up was an internship conversion funnel (11 of 45), not a ₹12-20 LPA guarantee.
PF / insurance / relocation: candidates care, policies vary by BU. Ask HR once, write the answer down, compare to the PDF offer. Group companies are not one benefits spreadsheet.
Typical IT path: OA (60-90 min) → Technical 1 → Technical 2 → HR. GET/intern drives may be written + one technical + HR. Campus batches often finish in about 2-3 weeks. Confirm the BU on your invite.
Many IT loops report four stages. GET/intern often three. Count the mailer.
Yes. Free Reliance placement papers and aptitude PDFs for 2024-2026 are on this site - pattern trainers with solutions. Start with the 2026 PDF or the paper archive.
OA typically 60-90 minutes. Some drives: ~12 minutes / 15-20 aptitude questions, then technical MCQs and 1-2 coding problems. Sectional cutoffs may apply. Verify your invite.
Quant (percentages, ratios, time & work, profit & loss), LR (syllogisms, puzzles, coding-decoding), verbal (RC, grammar, vocabulary). Speed beats exotic tricks. Drill aptitude questions.
Commonly reported floor: 7.5+ CGPA / 75%, relevant branch for the BU, final-year or recent grads, no active backlogs. Your drive notice overrides this page.
Candidate-reported Software Engineer / Analyst CTC often lands around ₹12-20 LPA (as of August 2026). GET/site packages differ. The written offer is the only number that matters.
Mumbai is HQ; GET/plant roles can mean sites and shifts. HR usually checks location flexibility. Be honest early.
IT: 40% aptitude speed, 30% coding/CS, 15% Jio/domain, 15% HR. GET: branch + project first. Details: preparation guide.
No. Jio Digital / RIL IT is coding + Java/SQL + platforms. GET is core written + plant projects + location/shifts. Prep to the notice.
C, C++, Java, and Python for IT coding. Core GET may have little coding. Confirm on the invite.
Jio Digital sits inside the Reliance group story; Airtel is a separate telecom product bar. Reliance also runs core GET tracks those telecom-only hubs may not. Prep aptitude once; customise BU stories.
For campus IT, aptitude timer + easy coding + one project beat certificate stacks. See certifications.
Practise the 12-minute aptitude clock until skip-and-return is automatic. Do not over-prep hard DP for GET. For Jio Digital, pair speed aptitude with a plain Jio-platform explanation.
Start with Reliance interview experience on this site, then cross-check GeeksforGeeks / Unstop for GET vs IT. Patterns shift - use them as maps, not scripts.
Profile patterns that got selected: B.Tech CSE/IT/ECE, roughly 7.5-8.0+ CGPA, one internship or a strong project, timed aptitude practice.
Online / written: Sections matched the college mailer. Speed and accuracy mattered more than fancy tricks. Shortlist often within a week.
Technical: Basic array/string coding, OOP follow-ups, Jio platforms and Java/SQL in plain language. Project: stack, hardest bug, what you would rebuild. Later rounds: scale-systems basics at fresher depth.
HR: Why this BU? Location flexibility? Keep answers short: situation → what you did → result.
Takeaway: clear aptitude plus a coherent Jio story beats a high CGPA with weak explanation.
What hurt others: untimed prep for a 12-minute section; treating HR location questions as optional; Kafka diagrams with no bottleneck.
An NIT Jalandhar Electrical Engineering summer-intern candidate described Reliance’s campus drive with a written test, then a Microsoft Teams technical held in the TPO office for anti-cheating, followed by HR. “Out of the 45 students who took the written test, a total of 11 students secured the internship,” with panels already familiar with shared project groups (GeeksforGeeks).
IIT Jammu’s Gaytri Sachdeva recounted her Reliance GET path on Unstop: resume shortlisting, aptitude + core chemical written test, document verification, then a three-member offline panel on plant-design projects and HR including Reliance vs PSU and why not research. Her answer: “Most of my research work has been hands-on and application-focused… That’s why I want to be at Reliance - to see real chemical engineering in action.”
If you are GET: that sentence structure - application over paper - is the bar, not a memorised slogan.
How to prep a GET oral in one page: write your plant/lab project as: objective → your calculations or design choice → what would break in a real unit → what you would measure. Then write two HR answers: (1) Reliance vs PSU - scale, private-sector execution, still respect PSU stability if that is your honest view; (2) why not a PhD - application focus, not “I dislike research.” Document verification showed up in that path - keep marksheets ready, not just a DSA folder.
IT vs GET on the same campus week: if both notices drop, do not merge prep. Morning: 12-minute aptitude + one array/string. Evening: branch numericals + plant story. Mixing Kafka into a chemical panel wastes both.
More narratives: Reliance interview experience.