Academic snapshot
Marks: 7.5+ CGPA preferred (drive-dependent)
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Arcesium builds post-trade, fund accounting, and data platforms for asset managers and hedge funds. Spun out of D. E. Shaw technology in 2015, the company runs a major engineering hub in Hyderabad focused on financial systems software.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA, PPT, college CGPA list; two technicals can land the same afternoon | Coding + MCQ bar |
| Careers / Instahyre | OA can arrive in ~2 days after apply | Same medium+hard coding |
| Referral | Faster recruiter eyes | You still sit the test |
| Intern → FTE | Conversion may skip a stage | You still defend projects |
Off-campus does not mean easier LLD. It often means more applicants who only prepared LeetCode and freeze when asked to design Snake & Ladders.
Is 7.5 CGPA enough? It matches the commonly reported preferred floor. Selection still hinges on OA accuracy. A 7.6 who clears both coding prompts and does not bleed MCQs (if negative marking is on) beats an 8.9 who guesses OS and fails DP.
Branches: CS/IT first; ECE when DSA is first-class. Confirm the notice.
Gaps and backlogs: Standing arrears are a hard stop on many campus notices. A short gap is easier to explain with a project than with silence.
What helps the resume screen: One project you can defend (schema, hardest bug, a metric), any internship with ownership language. See certifications after DSA and LLD, not as a substitute. CFA Level 1 without a hash map story is noise.
Academic snapshot
Marks: 7.5+ CGPA preferred (drive-dependent)
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Skills they actually filter
Primary: DSA, LLD, SQL/DBMS
Languages: Java, Python, C++
Light finance: NAV / position / post-trade vocabulary
Exam filter: Arcesium Online Assessment
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation CGPA | 7.5+ preferred on many tech shortlists | Arcesium has not locked one public India cutoff |
| Degree | B.E. / B.Tech / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE | Non-CS clears when DSA + SQL are daily |
| Year | Final year + recent grads | 0-2 YOE SDE-1 loops also appear off-campus |
| Backlogs | No active backlogs | Clear them before offer paperwork |
| Coding languages | Java, Python, C++ | Stick to one for OA + interviews |
Arcesium shortlists on academics when the JD prints a floor, then filters hard on the Online Assessment. Clearing CGPA only gets you into the funnel. One public on-campus FTE write-up described ~180 students sitting OA and 15 moving to interviews - treat that ratio as a planning number, not a promise for your college.
Download 2026 Arcesium placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Arcesium does not publish a permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy: aptitude, CS MCQs, 2 coding (medium + hard) |
| Technical 1-2 | Live DSA + resume; puzzles on some campus loops |
| LLD / DB design | Class design, extensibility, SQL joins / schema |
| HR | Why Arcesium, Hyderabad/Bengaluru/Gurugram, CTC split |
Think of papers as simulators for OA stamina, not a question bank to memorise. Arcesium reuses themes (interval merge, DP coin-change, topological sort, Snake & Ladders LLD) more than exact clones. If you can finish a 2024-style timed set cleanly, a 2026 OA will feel familiar even when the DP prompt is new.
| Theme you saw in a set | What to drill next | Why Arcesium asks it |
|---|---|---|
| Merge intervals | Sort + sweep, overlapping bookings | Calendars, trade windows |
| Coin change / unbounded knapsack | DP table vs greedy trap | Counting allocations |
| Topological sort | Kahn vs DFS, cycle = invalid | Job / dependency graphs |
| LCA / tree views | Recursion returning two values | Nested account trees |
| SQL multi-join | Inner vs left, recursive CTE lite | Positions + reference data |
| LLD game | Classes, state, extensibility | They want design, not only LeetCode |
2025 PDFs often drill “maximum prefix with broken keys.” Own the greedy + constraint template - then drill a related problem. That transfers; memorising the story text does not.
Arcesium India hires freshers through campus placement cells, arcesium.com/careers, Instahyre / job boards, and referrals. After resume screen, the shape is high-bar product engineering: mixed OA, DSA interviews, then LLD or schema design.
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline. Super-dream slot at many campuses.
Online applications
Apply on arcesium.com or boards like Instahyre for SDE / early-career; follow the invite for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear LLD.
Placement cell or recruiter checks degree, CGPA floor when printed (7.5+ preferred on many tech lists), backlogs, and year of passing. Projects help when volumes are high. This is a gate, not the hard filter - the OA is.
Candidate reports describe a HackerRank-style test. Instahyre-triggered OAs in 2026 write-ups match the same mix.
| Section (typical) | What shows up | Time feel | Pass habit |
|---|---|---|---|
| Aptitude / reasoning | Quant, logic, DI | Easy to over-spend | Skip if no path in 45 seconds |
| CS fundamentals | OOP, OS, DBMS, DSA theory | Precise; negative marking on some drives | Do not guess wild |
| Coding | 2 problems (medium + hard) | Correctness over golf | Edge cases before submit |
Languages: Java, Python, C++.
Pass bar in practice: One complete + one partial coding plus a clean MCQ score has cleared people when negative marking is on. Two fully passing solutions is the safer target.
Student tip: Read the MCQ instructions first. If negative marking is on, blank is better than a 25% guess.
| Minute | Move |
|---|---|
| 0-5 | Skim coding prompts; mark easy MCQs |
| 5-25 | Aptitude + CS - skip sticky items |
| 25-55 | Coding 1 (medium): restate → brute → optimize → code |
| 55-85 | Coding 2 (hard): same loop; leave 5 minutes for samples |
| 85-end | Flagged MCQs only if time remains and marking is not punitive |
Deeper OA notes: Arcesium Online Assessment.
Medium cousin - merge intervals: sort by start, walk once, merge when next.start <= cur.end. Edge cases: empty list, one interval, touching vs overlapping (ask). Complexity: O(n log n).
Hard cousin - constrained string / broken keys: you have a budget of errors and per-key use limits. Model it as “how far can I go in the prefix?” Greedy with a counter usually beats a vague DP if you can prove the choice. Hidden tests punish off-by-one on the last character.
You will not see these exact stems. You will see “sort then sweep” and “prefix under a budget.” That is why papers are trainers.
Often 2 DSA problems (array + DP is a common pair) plus OOP/DBMS and a project walkthrough. Some campus loops add a puzzle at the end.
You should:
Example narration (coin change ways): “Unlimited coins of 1, 3, 5. dp[x] += dp[x-coin]. Order of loops matters so we count combinations not permutations unless they ask otherwise.” I’ll test n=0 and unreachable n.”
Campus: another DSA set plus CS. Off-campus 2026: LLD Snake & Ladders - classes, state, how you would add a new rule without rewriting the board.
Start with nouns → responsibilities → what varies. Interfaces for Dice and WinningRule beat a 40-line main.
Worked mini-outline - Snake & Ladders:
SDE-1 write-ups include a cab management schema hour (tables, keys, a booking query) then HR on fixed vs variable, notice, joining. Campus FTE may fold SQL into technicals and keep HR shorter.
Know the ₹20-35 LPA fresher band so CTC talk is grounded. Ask one real question about post-trade or fund-accounting surface - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA | Drive-dependent (~90 min common) | MCQs + 2 coding |
| 2 | Technical 1 | 45-60 min | DSA + resume + maybe puzzle |
| 3 | Technical 2 / LLD | 45-60 min | More DSA or class design |
| 4 | DB design (some loops) | ~60 min | Schema + SQL |
| 5 | HR | 20-30 min | Fit, location, CTC split |
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | Instahyre OA can arrive in ~2 days |
| OA → interview shortlist | Same week common | Steep cut (example: 180 → 15) |
| Interview loop | Same day to ~2 weeks | Campus can stack two technicals |
| Offer / paperwork | Days after HR | Written offer wins over verbal |
| End to end | ~2-6 weeks often | Off-campus 0-2 YOE can stretch |
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude / logic | Skip rules | Timed mock quiz |
| CS MCQs | OOP, OS, DBMS | 20 flash cards; no wild guesses if negative marking |
| Coding | Medium + hard | Two timed problems back-to-back |
| LLD | Snake & Ladders / cab | Draw classes twice from memory |
| SQL | Joins, aggregation | 10 queries on a tiny positions schema |
| HR | Why Arcesium, city | Two STAR stories + relocation answer |
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 Arcesium 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 Arcesium sits around ₹20-35 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): Arcesium eligibility is drive-specific. Common India fresher reports: B.E./B.Tech/M.Tech/MCA in CS, IT, ECE, or related; typically 7.5+ CGPA preferred; no active backlogs; final-year students. Strong DSA, SQL/DBMS, and LLD matter after the academic gate. Always verify arcesium.com/careers or your campus JD.
What you are training for: Typical fresher loop: Online Assessment (MCQs on aptitude + CS fundamentals + 2 coding problems, medium + hard, often HackerRank) → 2-3 technical interviews (DSA, projects, sometimes puzzles) → LLD or database-design round on many SDE loops → HR. Campus batches can stack two technicals the same day. End-to-end often 2-6 weeks.
Short version of the prep split: Split time roughly: 40% DSA (arrays, DP, graphs, trees), 20% timed OA including aptitude and CS MCQs, 20% LLD/OOP, 10% SQL/DBMS, 10% projects/HR. Languages: Java, Python, C++. Do not skip LLD - Snake & Ladders and similar games show up.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Arcesium 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 Arcesium 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 Arcesium 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 Arcesium?” 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 Arcesium-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 Arcesium story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Arcesium papers on three different days, then interview prep on the leftovers.
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location (Hyderabad, Bengaluru, Gurugram), hiring year, and written components (base / bonus).
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| SDE / new-grad | ₹20-35 LPA | Primary band for this hub |
| SDE-1 (0-2 YOE, off-campus) | Often inside the same band | HR will discuss fixed vs variable |
| Experienced platform | Higher | Not the fresher campus default |
Confirm base, joining bonus, and variable on the written offer. Do not treat blog midpoints as guarantees.
Know the ₹20-35 LPA fresher context. One selected SDE-1 write-up said HR walked fixed, variable, and perks explicitly. Ask how the package splits and confirm joining vs final exams. One calm question beats aggressive negotiation with no anchor.
If you stall, say the constraint you would ask next.
Keep every email thread. Verbal numbers are not offer letters.
Use a tiny schema: accounts(id), positions(id, account_id, symbol, qty), trades(id, account_id, symbol, qty, ts).
WHERE qty > 0 is not the same as HAVING SUM(qty) > 0.Five queries, fifteen minutes, three times a week until they are boring.
Open a blank page. No IDE. Title: Snake & Ladders.
Board, Cell, Snake, Ladder, Dice, Player, Game.roll(), move(player), applyWarp(cell), isWin().Do the same with cab booking the other day: Rider, Driver, Trip, PricingStrategy, Location. One query: “trips in progress in a bounding box.” That is the DB-design hour in a different costume.
If you only ever AC LeetCode, this page is the interview you will fail. Arcesium’s 2026 off-campus notes are not subtle about that.
Some campus technicals end with a logic puzzle. You will not predict the exact one. The habit that transfers: restate the constraint, pick an example with n=3, then generalise. Silence for two minutes is worse than a wrong first model you correct. Practice with river-crossing or weighing-puzzles once a week, not every night.
A 2025 campus note had an hour between Tech 1 and Tech 2. Use that hour:
Campus compression is a feature. Prepare as if both rounds are today.
Campus technicals still ask immutability, singleton, overloading vs overriding after a graph problem. Thirty minutes, once a week:
If you only grind LeetCode, this 5-minute oral is how a 15-person shortlist becomes 10.
After a trade is agreed, someone has to confirm, settle, allocate, and report. Asset managers also need NAV and positions that match reality. Arcesium sells software for those workflows. You do not need to implement SWIFT messages in the interview. You do need to stop saying “they are a hedge fund like DESCO.” They are a platform company that came out of DESCO technology. That sentence alone prevents a common HR facepalm.
When they say “design a cab management system,” they often want tables, not Kafka.
users (id, role: rider/driver, phone)cabs (id, driver_id, plate, status)trips (id, rider_id, cab_id, start_ts, end_ts, status, fare)locations (cab_id, lat, lng, ts) - or last-known sampleThen one query: overlapping trips for a cab (start < other.end AND end > other.start). Talk about a status machine so a cab is not “on trip” twice. Index cab_id + start_ts. That 15-minute sketch is the round. Drawing 12 microservices is not.
If MCQs are +1 / −0.25 (or similar), expected value of a 4-option guess is negative. Eliminate two, then guess; otherwise skip. Coding still has no such penalty - finish the medium problem even if the hard one is half-done. The 180→15 campus cut was not decided by a heroic third algorithm. It was decided by people who either bled MCQs or submitted nothing.
Public 2026 notes: apply → OA in ~2 days → interviews soon after. That is faster than campus PPT week. Keep a “ready bag”: language chosen, Snake & Ladders drawing in muscle memory, two STAR stories, Hyderabad/Bengaluru/Gurugram answer. You cannot start LLD the evening the OA invite arrives if you have never drawn a class in your life.
If Instahyre is your only channel, still keep campus-style MCQ skip rules. The OA mix does not get easier because a job board sent it.
Same-day campus stacks are the other extreme: two technicals with an hour between them. Keep water, resume, and an LLD sketch already practised. Do not open a new hard DP in the corridor.
HR will still ask fixed vs variable even after three technicals. Know the ₹20-35 LPA band so you can ask a split question without quoting a meme. Then wait for the written letter. Background verification will match CGPA and dates; do not “round up” a 7.46 on the form. Hyderabad vs Bengaluru vs Gurugram belongs in that same honest list. Say the city you will actually join; a last-round location flip is a common self-reject.
Typical SDE path: resume screen → Online Assessment (aptitude + CS MCQs + 2 coding) → 2-3 technicals (DSA, projects, sometimes puzzles) → LLD or database-design round → HR. Campus can stack two technicals the same day. Off-campus often 2-6 weeks to written offer.
Most fresher loops report 4-5 stages (OA + two technicals + LLD/DB + HR). One campus cycle sent ~180 to OA and 15 to interviews. Count the mailer.
Yes. Free Arcesium placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. Start with the 2026 PDF or the paper archive.
Candidate-reported OA mixes aptitude/CS MCQs and 2 coding problems (medium + hard), often on HackerRank. Some campus years mention negative marking on MCQs. Verify your invite.
Commonly reported: 7.5+ CGPA preferred; B.E./B.Tech/M.Tech/MCA; final-year students; no active backlogs. Arcesium does not publish one universal cutoff - your notice overrides this page.
Candidate-reported CTC often lands around ₹20-35 LPA (as of August 2026) for SDE new-grads in Hyderabad, Bengaluru, or Gurugram. The written offer letter is the only number that matters.
Hyderabad is the largest hub; Bengaluru and Gurugram also appear. HR checks relocation. Be honest early.
Split time roughly 40% DSA, 20% timed OA (aptitude + CS), 20% LLD, 10% SQL, 10% behavioral. Clear timed mocks first. Details: preparation guide.
Java, Python, and C++ are the usual OA/interview set. Confirm on the invite. Do not switch the week of the drive.
No. It spun out of D. E. Shaw technology and remains a separate company building post-trade and data platforms. Prep DSA + LLD, not a pure quant contest plan.
Deep finance is not the fresher OA filter. Light vocabulary plus strong SQL and code is enough for most SDE screens. Do not skip DSA to cram finance blogs.
Treat the OA as the real filter - one campus cycle sat ~180 and sent 15 to interviews. Bank MCQ accuracy (watch negative marking), then defend two coding problems. Rehearse one LLD (Snake & Ladders) from memory.
Start with Arcesium interview experience on this site, then cross-check recent LinkedIn/GFG write-ups. Patterns shift by year - use them as maps, not scripts.
Different sport. Service aptitude mills are longer on volume; Arcesium’s mix is shorter but adds medium/hard coding, CS MCQs, and a steep LLD interview after OA.
Some campus write-ups say yes on MCQs. Confirm on your invite. If yes, do not guess wild - one complete coding problem plus careful MCQs has cleared people.
Public 2026 notes include Snake & Ladders (classes, extensibility) and cab management as a database-design hour. Practice those shapes; do not memorise someone else’s class names.
DESCO is still the higher-variance quant/engineering brand. Arcesium is the post-trade platform spinout - SDE with LLD and SQL. BlackRock India is Aladdin plus a mixed OA with aptitude. Prep DSA for all three; customise LLD for Arcesium and SQL+Aladdin talk for BlackRock.
Steal: OA as the real filter; MCQ skip rules; LLD on paper before the loop; honest DESCO-spinout story.
Ignore: memorising a 2019 GFG paper as if 2026 will clone it; CFA crash courses the week of OA; treating Arcesium as “easy DESCO.”
If you only do three things after reading this hub: time one mixed mock, draw Snake & Ladders once, and write five SQL queries from memory. That beats highlighting this page again.
An on-campus FTE process: HackerRank OA with 2 coding + 15 aptitude + 10 CS MCQs, negative marking on MCQs. About 180 sat the test; 15 reached interviews. Technicals covered topological sort, LCA, tree views, complex SQL, coin-change DP, OOP (immutable, singleton), then more SQL. Takeaway: one complete + one partial coding with decent MCQs can clear OA; interviews still expect real SQL and trees.
What that means for juniors: if your college opens Arcesium, do not celebrate - prepare the common layer (DP, SQL, MCQ discipline) harder.
A candidate applied via Instahyre, received OA in 2 days (MCQs + 2 coding medium/hard), cleared DSA (2 problems), then LLD Snake & Ladders. Stopped after LLD; takeaway they published: communication and design thinking, not only AC solutions.
Public LinkedIn notes: OA → multiple ~1 hour technicals including resume ownership and database design (cab system) → HR on salary structure and notice. Selected SDE-1. Takeaway: off-campus is the same bar plus more HR on logistics.
Helped: fully passing OA code; careful MCQs; spoken edge cases; a schema you can draw; honest city preference.
Hurt: wild MCQ guesses; silent coding; “I like DESCO” with no product story; skipping LLD practice.
Candidate cleared OA and a clean DSA round, then froze on Snake & Ladders: dumped a 80-line main with magic numbers, could not say how to add a second dice, and argued with the interviewer about “this is not DSA.” That is a self-reject. The fix is not more graphs that week. The fix is two paper designs.
OA first. Three ~1 hour technicals including a cab schema (tables, keys, a query for overlapping bookings). HR walked fixed vs variable and notice. They had already decided Hyderabad vs Bengaluru. Takeaway: off-campus is the campus bar plus adult logistics. Prepare both.
Campus same-day stack: if Tech 1 was trees, assume Tech 2 may switch to LLD or SQL. Keep those sketches warm before OA day. Water, food, resume re-read. No new LeetCode hard in the hour gap.
Off-campus Instahyre speed: OA in ~2 days means your LLD drawing must already exist. You will not learn class design the evening the HackerRank link arrives.
HR after three technicals: they will still walk fixed vs variable. Know the ₹20-35 LPA band. Then wait for the letter. Do not round CGPA on forms.
More fresher narratives: Arcesium interview experience.