Academic snapshot
Marks: ~60% or 6.0-6.5 CGPA; 10th/12th ~60%
Degree: B.E./B.Tech/MCA/M.Tech
Backlogs: None active
Year: Final year / recent grad
Persistent Systems Placement Papers 2026
Persistent Systems is a Pune-headquartered digital engineering firm that partners with software product companies and independent software vendors. It builds cloud-native applications, data platforms, and enterprise software for global clients. Persistent is a regular campus recruiter for software engineering roles across its India delivery centres.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Persistent Systems in 2026?
Persistent does not keep one forever eligibility PDF on the public careers site. Each drive prints its own numbers. What follows is the planning baseline students report for 2024-2026, not a signed HR policy.
Who this hub is for
- For: B.E./B.Tech/MCA students targeting Software Engineer via campus OA or the Martian internship-to-PPO path. Joining cities that show up: Pune, Nagpur, Bengaluru, Hyderabad.
- Not the same track: Experienced product-engineering loops, or faculty-development programs on the early-careers page. This hub is the student filter: aptitude + coding + CS fundamentals.
- ECE / non-CS: Some mailers include related branches if coding is real. Do not assume every Persistent drive is open to every circuit branch.
Degree, marks, backlogs
- Graduation: About 60% or 6.0-6.5 CGPA on many 2024-2025 reports (AmbitionBox/Shiksha/cell aggregates).
- 10th and 12th: Around 60% each. Keep scans. Services-style “throughout” checks still happen.
- Backlogs: Zero active at apply time is the usual rule. Clear before joining.
- Gap: Up to about one year tolerated on many drives; longer needs a clean story.
- Batch: Most recent one or two graduating years, as printed.
- Languages: Java, C++, or Python. Martian locks the final coding to Java or Python.
Direct FTE vs Martian
| Path | What you sit | What you get if you clear |
|---|---|---|
| Direct campus | OA → tech → HR | FTE / GET-style offer |
| Martian | OA → weeks of training + weekly MCQs → final 2 coding → tech → SVAR → HR | Internship then PPO |
| Train and hire / Career Compass | Self-learn modules before a drive | Readiness, not an automatic offer |
Martian is the distinctive Persistent story. It is not a free internship. Weekly tests and a 70+ score note on one LinkedIn account are real filters. If your college only has Martian this year, plan for a two-month stamina problem, not a one-day OA.
On-campus vs careers.persistent.com
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, Martian vs direct, college % list | Coding + CS bar |
| Careers / early-careers page | Application form | Same assessment flavour if invited |
| Referral | Visibility | You still code |
Off-campus does not mean easier coding. It often means more applicants who treated Persistent like a pure aptitude company and blanked on the second coding question.
CGPA: printed floor vs selected cluster
Is 6.5 enough? It matches many reported floors. If your mailer says 60% throughout, a 6.4 with a weak 12th can still fail the cell pre-filter. A 6.6 who finishes both coding questions and can explain OOPs beats a 8.5 who only practised quant.
| Hiring route | Typical filter (reports) | What actually filters you |
|---|---|---|
| On-campus | 60% / 6.0-6.5 when listed | Cell list + OA + interviews |
| Martian | Same plus training assessments | Weekly tests + final coding |
| Off-campus | Profile + OA | Resume + coding completeness |
Selection chances by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| Below 6.0 | Low on-campus | Only if the JD is softer |
| 6.0-6.4 | Medium | Coding must carry you |
| 6.5-7.5 | High | Common shortlisted band |
| Above 7.5 | Very high if coding holds | CGPA never ships a broken submit |
Skills they actually filter
Primary: Coding, OOPs, DBMS, aptitude
Languages: Java, C++, Python
Exam filter: Persistent Online Assessment
Persistent is a product-engineering flavoured services hire. Clearing 6.5 only gets you a test link. Treat coding completeness as the cut, CS fundamentals as the interview, and relocation honesty as the HR gate.
Persistent Systems previous year papers & PDFs
Download 2026 Persistent Systems placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What these papers train for the AMCAT-style filter
Persistent does not publish a permanent official paper set. “Previous year papers” on this site are pattern trainers: aptitude, OOPs/DBMS MCQs, and easy-medium coding. They are not leaked AMCAT/Cocubes items.
| Round (typical) | What to practice |
|---|---|
| Aptitude / verbal / logic | Speed with a skip rule |
| CS fundamentals MCQs | OOPs, DBMS, OS, CN |
| Coding | 1-2 easy-medium DSA |
| Martian final | Same, locked to Java or Python |
| Interviews | Projects + sorting/SQL |
Think of papers as simulators for a coding-weighted OA. Persistent reuses families (arrays, strings, binary search, frequency maps) more than exact clones. If you can finish a 2024-style pair of problems, a 2026 OA will feel familiar even when the string prompt is new.
Themes that keep repeating (2024-2026)
- Martian 2024 (GFG): OA with aptitude/logical/CS + 2 coding. Then 6-week training (DBMS, Linux, DSA, Java or Python). Final assessment: MCQ + 2 medium coding (array + string cited); 1 or 1.5 questions still got some interview calls. Then L1/L2 tech, SVAR, HR. Selection mail next day; offer letter ~a month later.
- LinkedIn Martian → SWE intern (2024): OA (apt + tech + easy-medium coding) → ~2-month Martian → another OA (70+ cited) → four on-campus steps (tech, advanced DSA, spoken English, HR) → 6-month SWE intern/training.
- Direct 2025-2026 drives: Secondary guides still describe AMCAT/Cocubes-style aptitude plus a coding section that carries more weight than at mass-service firms. Some drives club everything; others separate coding.
- 2026 prep expectation: Keep two finishable mediums in one language, plus OOPs/SQL flashcards, plus a 60-second spoken intro if SVAR is possible.
How to use one paper set in a single sitting
- Timed: 20 min aptitude, 20 min CS MCQs, 40 min two coding (or your invite’s split).
- Untimed review: rewrite the cleaner array/string solution.
- Map misses to coding and aptitude cousins.
- If Martian: solve both coding problems in the same language you will pick as your track.
- Log one STAR story and one “Why Persistent / Pune” line.
Related problems to practice
| Theme you saw in a set | What to drill next | Why Persistent asks it |
|---|---|---|
| Binary search | Overflow-safe mid, empty array | OA + tech IDE |
| Move zeros / two pointers | In-place discipline | Easy-medium coding |
| Rotate array | Reverse-three-times | Same |
| First unique character | Frequency array | String mediums |
| OOP MCQs | Interface vs abstract | CS section + L1 |
| SQL joins | GROUP BY / HAVING | Tech interview |
Persistent Systems placement process, round by round
Persistent hires freshers through campus cells, careers.persistent.com, and the Martian early-careers path. After eligibility, the shape is product-leaning services: coding matters, then fundamentals, then relocation.
Application methods
Campus recruitment
Primary path. PPT → OA → (Martian training or direct interviews) → HR. Locations: Pune, Nagpur, Bengaluru, Hyderabad.
Online applications
persistent.com careers. Follow the assessment mail for platform (AMCAT / Cocubes appear in secondary guides).
Referrals
Help visibility. You still need a complete coding submit.
Direct path
- Resume / eligibility - 60% throughout style rules, no active backlogs.
- Online assessment - Aptitude, verbal, logic, CS MCQs, 1-2 coding. Coding is the differentiator vs a TCS-style mill.
- Technical R1 - Resume, OOPs, DBMS, one sorting/DSA in an IDE.
- Technical R2 (some drives) - Harder DSA or deeper CS.
- HR - Hobbies, Why Persistent, relocation.
Martian path (the long game)
- OA - Same flavour: apt + CS + 2 coding.
- Training (5-6 weeks or ~2 months) - Weekly MCQs. Tracks: Java or Python. Topics students name: DBMS, Linux, DSA.
- Final assessment - MCQ + 2 medium coding in the chosen language. One GFG note: 1 or 1.5 solved still got interview calls; a LinkedIn note cited 70+ as a score target.
- Technical interview(s) - L1 fundamentals, L2 a bit advanced. One account: resume + sorting in IDE, then a harder DSA round.
- SVAR / spoken English - Amcat, computer-based.
- HR - Company knowledge, relocate, hobbies.
- PPO / offer - Mail next day in one GFG account; offer letter about a month later. Some continue into a 6-month SWE intern/training.
| # | Round | Direct | Martian |
|---|---|---|---|
| 1 | OA | Yes | Yes |
| 2 | Training tests | No | Weekly, eliminatory |
| 3 | Final 2-coding | No | Yes |
| 4 | Technical | 1-2 | 1-2 |
| 5 | SVAR | Rare | Common |
| 6 | HR | Yes | Yes |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| OA | 1 day | Campus lab or remote |
| Direct interviews | Days to 2 weeks | Tech + HR |
| Martian training | 5-8 weeks | Do not ghost weekly tests |
| Final assess + interviews | 1-2 weeks | SVAR same week as tech |
| Offer letter | Days to ~1 month | Mail ≠ PDF |
| End to end | ~3-10 weeks | Martian is the long tail |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude / verbal / logic | Skip after 45 seconds | Daily mock quiz |
| CS MCQs | OOPs, DBMS, OS | 20 flashcards |
| Coding | 1-2 complete easy-medium | Coding questions |
| Martian track | Java or Python | Same language every sitting |
| SVAR | Clear, short answers | Record intro twice |
| HR | Relocate, Why Persistent | One honest city line |
Deeper OA notes: Persistent online assessment.
Coding under a product-engineering filter
Persistent students keep saying coding weighs more than at mass-service firms. Practical target:
- Direct OA: one fully passing plus a serious second attempt.
- Martian final: two mediums (array + string is the 2024 pair people remember).
25-40 minute clock per problem: read twice, name the pattern (search / two pointers / freq map), code happy path, test n=1 and empty, submit. Do not start a third algorithm at minute 38.
Technical cabin: questions that actually get asked
From Martian 2024-style write-ups:
- Introduce yourself and this project. What did you write?
- Overloading vs overriding; interface vs abstract class.
- Primary key, normalisation 1NF-3NF in one example.
- Write or run a sort in the IDE.
- SQL: students with marks > 80.
- Why this language track?
- Are you ready to relocate?
Prepare short answers. A 12-minute microservices tour is how you miss DBMS.
SVAR: what “good enough” sounds like
You are not sitting IELTS. You are proving you can join a stand-up in Pune.
- 45-60 second intro: name, college, one project, one language, stop.
- Listen to the prompt. Answer the question asked.
- Fillers (“basically, like”) count against you if they bury the noun.
Practice on a phone in a noisy hostel once. If you can stay clear there, Amcat at home is easier.
Relocation: decide before HR
Persistent’s centre of gravity is Pune (Nagpur is a real second hub; Bengaluru/Hyderabad also appear). HR will ask. “I’ll see” is a no. Ask city on the letter if you have constraints. Pretending you love every city and backing out later burns the college’s next drive.
Documents pack
10th, 12th, semester marksheets, ID, resume one page. Martian adds training-portal logins you should not lose. Name and percentages must match every form.
Weekend mock that matches a direct drive
Saturday 10:00: 20 min aptitude, 20 min OOPs/DBMS MCQs, 40 min two coding in one language.
Saturday 13:00: review only misses. Rewrite the cleaner array/string solution.
Sunday: 30-minute oral (project + OOP + one SQL) with a friend, then a 60-second intro recording for SVAR.
If your drive is Martian, add one weekly MCQ set on the training portal schedule and do not skip week 3. That is when people ghost and then fail the final 2-coding.
Martian weekly tests: how not to die slowly
- Same language every week. Switching Java to Python in week 5 is how the final assessment feels foreign.
- DBMS and Linux show up in training. Twenty flashcards beat a 400-page PDF.
- Treat a 60% weekly score as a warning, not a participation trophy.
- Keep a running notes file: one SQL you missed, one OOP definition, one DSA pattern. That file is the final-assessment revision.
Coding mini-drills for Persistent-style mediums
- Binary search (empty array, duplicates if the prompt allows).
- Move zeros / two pointers.
- Rotate array by k (k %= n).
- First unique character.
- Frequency map + one string window.
Five sittings until submit-and-test is automatic. Then solve all five again in the Martian track language if that is your path.
Why Persistent (30 seconds)
“I want product-engineering work with ISVs, not only ticket-closed staffing.” The Martian/coding filter matches how I already practise.” If you are on the direct path, drop Martian and say coding + CS fundamentals. Specific > “Persistent is a good company.”
Pune vs Nagpur vs Bengaluru
Pune is HQ gravity. Nagpur is a real delivery hub with a different living-cost story. Bengaluru/Hyderabad show up on some letters. Ask the city before you post a celebration story. Relocating after you told HR “anywhere” and then refusing Nagpur is how colleges lose the next drive.
Cloud certs vs the OA
Persistent’s early-careers page loves AWS/GCP/Microsoft counts. Those help after you join. They do not replace two passing coding questions. If you have spare time in week 8 of Martian, a cloud fundamentals badge is fine. In week 1, code.
Direct vs Martian: pick so your calendar matches
If both are open, ask the cell which letter you will actually get. Martian is a stamina product: weekly tests plus a final 2-coding plus SVAR. Direct is a one-week product: OA then cabins. Students who treat Martian like a relaxed internship and then panic at the final assessment are a repeating pattern. Block the training weeks on your calendar like a course, not like a club.
Technical R2 when it exists
Some drives add a harder DSA round after L1. Expect an IDE, not a chalkboard only. Patterns: sorting you must implement, a graph/tree if the panel is spicy, or a second SQL. If L1 was all theory, L2 is where incomplete coding shows. Keep one medium you can type without looking at notes.
What “product engineering” means in a 20-year-old services firm
Persistent sells engineering to ISVs. In an interview that means: you can own a module, write tests, and talk to a product manager’s ticket. It does not mean you will ship a consumer app with your name on the icon. If you want that, sit a product company. If you want stronger coding than a mass mill plus a Pune/Nagpur seat, Persistent is in the right band.
Offer letter lag
GFG Martian 2024: selection mail next day, offer PDF about a month later. Do not resign another offer on a portal “congratulations.” Keep coding warm in that month; some people still sit other companies until the PDF.
Spoken English if you are not on Martian
Direct HR still hears you. A mumbled “I am passionate about software” is a skip. Same 60-second intro. Same relocation sentence. Practise once even if SVAR is not on the mailer.
10th/12th “throughout” checks
Even when the graduation CGPA is 7.0, cells still ask for 10th and 12th scans. A 58% in 12th against a 60% mailer is a silent reject. Scan everything the night you register. Do not discover a missing marksheet after you cleared the final Martian coding test.
Language track lock-in (write this on a sticky note)
Martian final coding is in the track you chose. If you pick Java, every weekly coding exercise should be Java. Practising Python “because it’s faster to sketch” and then translating on assessment day is how people miss the second medium. Pick on day one. Tell your roommate so they can nag you. If the portal lets you change tracks, still do not; interviewers will ask why your Git samples are in the other language. Keep one small Java or Python repo you can open in the cabin without hunting for a USB.
Where to practise for Persistent Systems
Week-by-week plans live on the preparation guide, not here.
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.
How students actually prep for Persistent Systems
If a Persistent Systems 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 Persistent Systems sits around ₹5-8 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): Persistent does not publish one static public sheet. Campus and candidate reports commonly cite about 60% or 6.0-6.5 CGPA in 10th, 12th, and graduation, no active backlogs, and up to about one year gap. Degrees: B.E./B.Tech/MCA/M.Tech, typically CS/IT and related for software tracks. Always verify careers.persistent.com or your placement email.
What you are training for: Two common campus shapes. Direct: online assessment (aptitude, CS fundamentals, 1-2 coding) → technical interviews → HR. Martian: OA → 5-6 week (sometimes 2 month) training with weekly tests → final MCQ + 2 coding in Java or Python → tech interview(s) → SVAR/Amcat speaking → HR → PPO. End-to-end from first OA to offer letter can be weeks to a couple of months.
Short version of the prep split: Weight coding higher than at a mass-service aptitude mill: about 35% easy-medium DSA, 25% aptitude/verbal/logic, 20% OOPs/DBMS/OS MCQs, 10% Java or Python track depth if Martian, 10% speaking + HR (relocation to Pune/Nagpur). Full plan: /persistent/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Persistent Systems 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 Persistent Systems 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 Persistent Systems 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 Persistent Systems?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Persistent Systems-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.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Persistent Systems story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Persistent Systems PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Persistent Systems papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Persistent Systems papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Persistent Systems-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Persistent Systems compensation & benefits
Figures are candidate-reported India bands as of August 2026.
| Band | Typical CTC (reports) | Notes |
|---|---|---|
| Software Engineer fresher | ₹5-8 LPA | Primary band for this hub |
| Martian / associate-adjacent | Often ₹4.5-6 LPA in chatter | Confirm PPO letter |
| Intern stipends | Drive-specific | Separate from FTE |
Confirm base vs variable and joining city on the written offer. Treat ₹5-8 LPA as a reported band, not a product-company number.
Benefits students actually care about
- Health insurance
- Learning / hyperscaler cert marketing (AWS/GCP/Microsoft numbers on the early-careers page)
- Pune / Nagpur living costs vs Bengaluru
- Internship-to-PPO structure on Martian
How to talk CTC in HR
Know ₹5-8 LPA. Ask split and city. Do not negotiate like a FAANG blog. If two services offers arrive, compare site + joining date + Martian vs direct before headline ego.
Offer-stage discipline
- Read whether the letter is intern, PPO, or FTE
- Confirm location (Pune vs Nagpur vs Bengaluru)
- Do not resign another offer until the PDF lands
- Background check will match 10th/12th/degree
Keep every email. “Selected” on a training portal is not an offer letter.
What’s changed in Persistent Systems hiring lately
- Martian remains the signature campus path on many colleges: training weeks, language track, SVAR, then PPO.
- Coding weight stays higher than mass-service aptitude mills.
- Java vs Python track is a real lock-in for the final assessment. Pick in week one.
- Offer letters lag selection mails by weeks. Budget for that.
- Pune/Nagpur still dominate location talk.
- Treat ₹5-8 LPA as the reported SE band for 2026 planning.
Net for 2026: finish coding questions, take Martian weekly tests if that is your path, and decide relocation before HR.
FAQs students ask about Persistent Systems placements
Process & papers
What is the Persistent Systems placement process?
Direct: OA → 1-2 technicals → HR. Martian: OA → weeks of training → final MCQ + 2 coding → tech → SVAR → HR → PPO. End-to-end can be a few weeks to a couple of months.
How many rounds are there in Persistent Systems interview?
Direct loops often 4 stages (OA, tech R1, tech R2, HR). Martian adds training assessments and SVAR. Count the invite.
Can I download Persistent Systems placement papers PDF?
Yes. Free Persistent papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
What is the Persistent online assessment exam pattern?
Aptitude / verbal / logic plus CS fundamentals MCQs plus 1-2 coding (2 in several Martian accounts). Platforms: AMCAT/Cocubes in secondary guides. Languages: Java, C++, Python.
Eligibility & offer
What is Persistent Systems eligibility criteria for freshers 2026?
Reports cluster around 60% or 6.0-6.5 CGPA, 10th/12th ~60%, no active backlogs. Binding number is on your mailer or careers.persistent.com.
What is Persistent Systems salary for freshers in India?
Candidate-reported CTC often lands around ₹5-8 LPA (as of August 2026). Martian/associate notes can sit lower. The written letter is the only number that matters.
What is the Persistent Martian program?
Internship/training after OA: 5-8 weeks of weekly tests, Java or Python track, final 2-coding assessment, then interviews and SVAR for a PPO. Eliminatory, not ceremonial.
Prep & Persistent-specific
How to prepare for Persistent Systems placement?
About 35% coding, 25% aptitude, 20% OOPs/DBMS, 10% language track, 10% speaking/HR. Details: preparation guide.
What programming languages are allowed in Persistent Systems?
Java, C++, Python on most OAs. Martian final coding is usually only the track you chose.
Is there a communication or SVAR round?
Yes on Martian (Amcat SVAR). Direct drives may skip the named test but still expect clear English in HR.
Any pro tip for Persistent Systems placement preparation?
Finish coding questions. If Martian, pick Java or Python early and treat weekly tests as real exams. Decide Pune/Nagpur before HR.
Where can I read real interview experiences?
Start with Persistent interview experience and the GFG Martian 2024 write-up.
Does Persistent hire only CS/IT?
Software tracks usually list CS/IT and related. ECE appears on some mailers. Read the JD.
Persistent vs Coforge vs Thoughtworks for freshers?
Persistent: coding-weighted services with a Martian path. Coforge: aptitude plus a communication-first round on some campuses. Thoughtworks: pair programming, higher DSA bar. Prep aptitude+coding for the first two; add pair practice for Thoughtworks.
Is Martian a guaranteed PPO?
No. Weekly tests and the final 2-coding assessment are eliminatory. Clearing OA only gets you into training. A PPO still needs the final assessment, interviews, and SVAR.
What recent candidates reported
Full write-ups stay on interview experience.
What to steal this week
Steal: two coding completes; one language track; weekly Martian tests if that is your path; relocation answer.
Ignore: treating Persistent like a pure aptitude mill; switching Java to Python in week five; celebrating a selection mail as an offer letter.
If you only do three things: time two mediums in one language, record a 60-second intro, and read whether your drive is Martian or direct.
Martian Program, 2024 (GFG)
OA (apt/logical/CS + 2 coding) → 6-week training → final MCQ + 2 coding (array + string) → tech L1/L2 → SVAR → HR (hobbies, company knowledge, relocate). Selection mail next day; offer letter about a month later.
Source: GFG Persistent Martian 2024.
Martian then SWE intern (LinkedIn, 2024)
OA → ~2-month Martian → second OA (70+ cited) → four on-campus rounds (tech, DSA, spoken English, HR) → 6-month SWE intern/training. Takeaway: Martian can be a two-stage filter, not one internship and done.
What selected vs rejected patterns look like
Helped: complete coding; same language all the way; honest relocation; documents ready.
Hurt: blank second coding; skipped weekly tests; mumbled SVAR; surprise at Pune.
Persistent vs Coforge vs Thoughtworks
All three sit near “I want better than a pure mill.” Persistent’s twist is Martian + coding weight. Coforge’s twist is communication-first on some campuses. Thoughtworks is a different sport (pair + values). Prep accordingly.
More narratives: Persistent Systems interview experience.
Related companies to compare
Hexaware · Coforge · Thoughtworks · Mphasis · LTTS