Academic snapshot
Marks: 7.5+ CGPA / 75% (candidate-reported)
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
MathWorks Placement Papers 2026
MathWorks builds MATLAB and Simulink, the industry-standard tools used by engineers and scientists for modeling, simulation, and algorithm development. Founded in 1984, its India engineering hubs in Bengaluru, Pune, and Hyderabad hire for software development, quality engineering, and technical support roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to MathWorks in 2026?
Who this hub is for
- For: Students targeting Engineering Development Group (EDG) and related early-career software / application-support roles at MathWorks India - the people who build, test, and support MATLAB and Simulink, primarily Bengaluru and Pune.
- Not the same track: Pure sales, campus ambassador gigs, or experienced-hire product-development loops with a staff-level design bar. Those interviews go deeper on compilers, numerics, or domain than this fresher map.
- Intern → FTE: Intern OAs can look similar (HackerRank + sometimes HireVue). Conversion still needs you to defend projects and code. Use this page as the base, then read intern write-ups for HireVue prompts.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT (watch it - later rounds quiz it), CS vs Core track choice | Coding bar, EDG conversation |
| Careers portal | Resume + transcript volume; sometimes a code challenge + video screen | Still expect HackerRank + technical depth |
| Intern → full-time | Some stages may compress | You still defend MATLAB/coding and “why EDG” |
Off-campus does not mean easier coding. It often means more applicants on the same ~90-minute filter. If your CGPA sits near 7.5, spend energy on mocks, not on hunting a mythical 7.0 blog post.
Degree, projects, and “is 7.5 enough?”
Is 7.5 CGPA enough? It matches the commonly reported floor. Selection still hinges on OA correctness and whether you can talk like an engineer who enjoys other people’s models, not only your own LeetCode streak. A 7.6 with clean timed coding beats an 8.9 that freezes on pointers.
Branches: Campus drives often split CS and Core Engineering. CS/IT/ECE dominate shortlists. Mechanical, EEE, and related streams show up on the core track when control, signals, or numerics are real - not when the resume only lists “MATLAB beginner certificate.”
Gaps and backlogs: Active backlogs are the usual blocker at offer time. A short education gap is easier to explain with a skills story (projects, internship, open-source, course) than silence. Lying about CGPA is an instant integrity fail in HR.
What helps the resume screen: One project you can defend end-to-end (numerical method, simulation, compiler toy, vision pipeline, or a solid software tool), any internship with ownership language, and honest keywords you can explain. MATLAB on the resume only helps if you can open a live session in your head. See certifications after fundamentals are solid.
Branch & skills
Tracks: CS or Core Engineering (drive-dependent)
Languages: MATLAB, C++, Python, Java
Focus: DSA, numerical methods, OOP / C memory
Differentiator: MATLAB/Simulink + teaching-tools mindset
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.5+ CGPA / ~75% | Some notices say “strong academic record” without a number; verify every drive |
| Degree | B.E. / B.Tech / M.Tech / MCA | Related engineering/CS degrees on many posts |
| Branch | CS track or Core (ECE/EEE/Mech etc.) | Choose the track you can defend in interview |
| Year | Final year + recent grads | Internship → conversion paths also appear |
| Backlogs | No active backlogs preferred | Clear them before offer paperwork |
| Coding languages | MATLAB, C++, Python, Java | Stick to one for live coding; keep MATLAB vocabulary |
MathWorks CGPA criteria
Minimum CGPA required (candidate-reported): 7.5+ CGPA / 75% is the commonly cited campus floor for EDG fresher roles. Treat it as a shortlisting filter when printed - MathWorks still decides on OA correctness and interview narration.
MathWorks shortlists on academics when the JD prints a floor, then filters hard on the Online Test. Clearing CGPA only gets you into the funnel - coding plus a coherent EDG story decide whether you see an offer.
MathWorks does not publish one universal India cutoff for every drive. Numbers below are candidate-reported from campus notices and interview write-ups (as of August 2026). Your placement cell mailer always wins.
MathWorks previous year papers & PDFs
Download 2026 MathWorks placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What MathWorks previous year papers actually train
MathWorks does not publish one 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 Test | Timed accuracy on ~90 min HackerRank: aptitude speed + 2 medium coding + pseudocode |
| GD | Listening, PPT facts, education/tech policy style prompts |
| Technical | Live coding narration, C/OOP, MATLAB or core domain |
| HR / managerial | Why EDG (not “I like MATLAB the brand”), higher studies, failure stories |
Themes that keep repeating (2024-2026)
- 2024 cycles: Campus OAs still mixed aptitude + 2 coding + C-family pseudocode. Interval / array / search themes show up in practice sets. Students who only drilled unsorted LeetCode without timeboxes lost easy quant marks. PPT follow-ups appeared in HR/managerial.
- 2025 loops: Write-ups still describe HackerRank as the first gate. Intern-style papers sometimes offer a MATLAB MCQ track vs coding track - India FTE campus papers more often keep the mixed format. Technical rounds stay long (~60-90 min) with live coding and C memory / OOP. CS vs Core track choice remains a real fork.
- 2026 prep expectation: Keep aptitude speed, medium DSA, and one MATLAB or core story warm. Expect technical to stay “engineer who can teach a tool,” not FAANG staff-level distributed systems. Treat PDF packs as pattern catalogs: Master the unbounded-knapsack template, do not memorize that story.
How to use one paper set in a single sitting
- Timed: run a full ~90-minute mock (aptitude + two coding + a short pseudocode block) in the language you will use on test day.
- Untimed review: rewrite the cleaner solution; list three edge cases you missed (empty array, overflow, impossible amount).
- Map each coding miss to a theme (DP / binary search / two pointers / graphs) and pull two cousins from coding questions.
- Spend 15 minutes explaining what MATLAB does for an engineer who is not you - a control student debugging a plant model, or a CS student vectorizing a loop.
- Log one STAR story the session reminded you of (helping a teammate, owning a broken simulation, choosing an algorithm under a deadline).
Related problems to practice
| Theme you saw in a set | What to drill next | Why MathWorks asks it |
|---|---|---|
| Min coins / unbounded knapsack | Classic DP 1D/2D | Numerical “fewest steps” thinking |
| Binary search on answer | Bounds, overflow-safe mid | Root-finding / threshold intuition |
| Two pointers / move zeros | In-place array discipline | Clean code without extra buffers |
| Rotate / reverse tricks | In-place O(1) space | You can manipulate arrays without STL panic |
| Pseudocode output | Pointers, loops, short-circuit | C-family literacy for tool internals |
| MATLAB indexing / vectorize | Broadcasting, end, logical index |
Product vocabulary, even if OA was C++ |
2024 PDFs often drill “minimum coins for amount N.” Own the DP template - dp[0]=0, update each coin, sentinel for impossible - then drill a related problem with limited coin counts. That transfers to interviews; memorising the story text does not.
MathWorks hiring rounds in 2026
MathWorks India hires freshers through campus placement cells, mathworks.com careers, referrals, and intern conversion. After resume screen, the shape is product-company plus a teaching/support twist: timed OA, then a variable-order mix of GD, HR, managerial, and a long technical.
Application methods
Campus recruitment
Through college placement cells - PPT (take notes), then OA and knockout interviews on a batch timeline.
Online applications
Apply on mathworks.com careers for EDG / early-career roles; follow the invite for HackerRank and any video screen.
Referrals
Employee referrals improve visibility. You still need passing OA code and a clear EDG story.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (7.5+ / 75% commonly reported), backlogs, and year of passing. Projects that look like numerics, simulation, compilers, vision, or real software help when volumes are high. This is a gate, not the hard filter - the Online Test is.
2. MathWorks online test - HackerRank (~90 min)
Candidate reports commonly describe a ~90-minute (sometimes ~1.5h intern-account) assessment mixing aptitude, coding, and pseudocode. Exact section splits vary; treat the table as a working map, not a sealed blueprint.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude / quant | ~10-20 | ~20-30 min | Ratios, P&L, interest, time-work |
| Coding | 2 medium | ~40-50 min | Arrays, search, DP, strings |
| Pseudocode / language MCQ | ~8-15 (when present) | ~15-25 min | C/C++/Java output, OOP basics |
Languages: MATLAB, C++, Python, Java - confirm yours. Platform: HackerRank appears in almost every India write-up.
Pass bar in practice: Two fully passing coding solutions beat a brilliant half-answer plus perfect aptitude. Pseudocode punishes people who never compiled a pointer.
Student tip: Spend 3-4 minutes skimming both coding prompts. Bank the solvable one first. Invent two edge cases before submit. Do not burn the clock proving a fancy algorithm if a clear O(n log n) already passes.
Example timing for a 90-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim full paper; mark easy aptitude + easier coding |
| 5-25 | Aptitude / MCQ block - skip sticky puzzles, return later |
| 25-55 | Coding problem 1: restate → brute → optimize → code → samples |
| 55-80 | Coding problem 2 or harden edge cases |
| 80-90 | Pseudocode leftovers; do not open a new hard DSA rabbit hole |
Deeper OA notes and drills: MathWorks Online Assessment.
3. Group discussion - ~15-20 min
Not every drive runs GD. When it does, topics look like education policy, tech in society, or something from the PPT. Knockout: people who never listened get cut even with a good OA.
Speak 2-3 times with a fact or a structure (“two trade-offs…”). Do not dominate. Do not stay mute.
4. HR + managerial conversation - ~20-40 min each
Often separate. HR checks logistics, higher studies, integrity, family constraints, Bengaluru/Pune move. Managerial is a conversation: internships, a failure, why EDG instead of a pure SWE product role, how you help a frustrated MATLAB user.
Why EDG sample shape: “I like going deep on algorithms, but I also like explaining tools.” EDG’s mix of customer application support and rotations matches that better than a single-stack trainee role.” Generic “prestigious brand” answers die here.
5. Technical interview - ~60-90 min
Video or onsite shared editor. Expect 1-2 live coding problems plus C/OOP/memory and a project deep-dive. CS track: data structures, complexity, sometimes compilers/linkers. Core track: control, signals, embedded, plus enough coding to prove you belong.
You should:
- Clarify constraints (null inputs, overflow, MATLAB 1-based indexing if relevant)
- Narrate brute force → bottleneck → target complexity
- Code without syntax stalls
- Walk edge cases and complexity at the end
Interviewers care about debugging out loud. Silent staring after a failed test case is a common reject signal even when the idea was right.
Example narration shape (binary search on answer): “Brute force is linear scan of the threshold. The feasibility check is monotonic, so I’ll binary-search the answer. Mid overflow - I’ll use lo+(hi-lo)/2.” Empty input - I’ll state the return before coding.” That 40-second plan already signals interview readiness.
Worked mini-outline - “help a user whose simulation is slow”:
- Ask: How large is the model? Where is time spent (solver, I/O, MATLAB loops)?
- First aid: Profile, vectorize obvious loops, check sample time / solver choice.
- Trade-off: Accuracy vs speed; do not jump to MEX/codegen before measuring.
- EDG angle: You teach the user to diagnose, you do not just throw a faster script over the wall.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (aptitude + coding + pseudo) | ~90 min | Timed accuracy |
| 2 | GD (if scheduled) | ~15-20 min | Listening + PPT awareness |
| 3 | HR | ~20-30 min | Logistics, integrity, location |
| 4 | Managerial | ~20-40 min | EDG fit, communication |
| 5 | Technical | ~60-90 min | Code + C/OOP/domain |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA completion → shortlist | Few days common | Some batches move faster |
| Interview loop | ~1-2 weeks | Order can shuffle; knockout |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~2-4 weeks campus batches often | Off-campus can be 3-6+ weeks |
Intern loops sometimes add HireVue video questions before or after OA. Treat those as extra, not the default campus FTE script.
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude | Speed + accuracy | Timed mock quiz |
| Coding Q1-Q2 | Arrays, DP, search, two pointers | Two timed mediums back-to-back |
| Pseudocode | C/C++/Java output | 15 pointer/loop MCQs |
| Domain | MATLAB or core story | Explain one flow in 3 minutes aloud |
| HR / EDG | Why rotations + support | Two STAR stories + location answer |
Preparation resources for MathWorks
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.
MathWorks preparation strategy that works
If a MathWorks 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 MathWorks sits around ₹14-25 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): MathWorks eligibility for freshers 2026 is candidate-reported, not one official published cutoff. Common EDG / campus baseline: B.E./B.Tech/M.Tech/MCA (or related engineering/CS) with a strong academic record; typically 7.5+ CGPA / 75%; no active backlogs preferred; final-year students and recent graduates. MATLAB helps but is often listed as a plus, not a hard gate. Always verify the drive notice or mathworks.com ca.
What you are training for: India EDG fresher loops commonly run: MathWorks Online Test (HackerRank, often ~90 min: aptitude + 2 medium coding + pseudocode) → then a mix of Group Discussion, HR, managerial conversation, and a deep technical round. Order can vary and rounds are often knockout. Campus batches frequently finish in about 2-4 weeks; off-campus can stretch.
Short version of the prep split: Treat MathWorks as scientific-computing product hiring, not a generic IT services drive. Split time roughly: 40% DSA/coding (C++/Java/Python), 25% MATLAB + numerical methods / core engineering for your track, 20% CS fundamentals (OOP, C memory, complexity), 15% EDG story + HR/GD. Clear timed OA mocks before deep interview prep.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the MathWorks 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 MathWorks 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 MathWorks 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 MathWorks?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. 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 MathWorks-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 MathWorks story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 MathWorks 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 MathWorks 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 MathWorks papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in MathWorks-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed MathWorks 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 MathWorks. 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.
MathWorks compensation & benefits
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level (EDG associate vs other early-career titles), location (Bengaluru / Pune), hiring year, and written components (base / bonus / any equity).
Edg and related bands students ask about
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| EDG / fresher software | ₹14-25 LPA | Primary band for this hub |
| Some EDG offer write-ups | Toward upper end of that range | Role and year dependent - offer letter wins |
| Intern stipends | Separate from FTE CTC | Do not mix intern monthly pay into LPA blogs |
| Experienced product hire | Wide spread | Outside fresher prep scope |
Confirm base, joining bonus, and benefits language on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Policies vary by team and year. Candidates commonly care about:
- Health insurance and wellness support
- Learning / MATLAB product depth (you live in the tools)
- Hybrid or office norms for Bengaluru / Pune
- Relocation support when moving cities - ask HR, do not assume
How to talk CTC in HR without sounding lost
Know the ₹14-25 LPA fresher context, ask how the package splits (fixed vs variable), and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor.
What’s changed in MathWorks hiring lately
- HackerRank remains the common first filter for India campus and many intern loops.
- EDG is still the fresher story - rotations + application support + product teams - not a generic services trainee label.
- CS vs Core track choice still shows up; pick honestly.
- PPT quizzes in later rounds have not gone away. Take notes.
- MATLAB-as-alternative-section appears more in intern / some international papers; India FTE campus papers still often mix aptitude + coding + pseudocode. Trust your invite.
- Treat ₹14-25 LPA as a reported fresher band, not a promise for every college.
- Process order stays flexible - do not memorize “OA then tech then HR” as a law.
Common questions about MathWorks hiring
Process & papers
What is the MathWorks placement process for freshers?
Typical India EDG path: MathWorks Online Test (~90 min, aptitude + coding + often pseudocode) → then GD, HR, managerial, and technical in an order that can shuffle. Campus batches often finish in about 2-4 weeks; off-campus timelines vary. Confirm round names on your invite.
How many interview rounds does MathWorks usually have?
Most fresher EDG loops report 4-5 stages after resume screen (OA + a mix of GD/HR/managerial/technical). Intern loops may add HireVue. Count the mailer, not a random blog.
Can I download MathWorks placement papers PDF for free?
Yes. Free MathWorks placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. No registration for the main downloads. Start with the 2026 PDF or the paper archive.
What does the MathWorks Online Test look like?
Candidate-reported India OA is often ~90 minutes on HackerRank with aptitude and 2 medium coding problems, plus C/C++/Java-style pseudocode on many campus papers. Languages: MATLAB, C++, Python, Java. Verify yours.
Eligibility & offer
What eligibility / CGPA do fresher EDG drives usually expect?
Commonly reported floor: 7.5+ CGPA / 75%, relevant engineering/CS degree, final-year or recent grads, no active backlogs preferred. MathWorks does not publish one universal cutoff - your drive notice overrides this page.
What is MathWorks fresher salary in India?
Candidate-reported EDG / fresher CTC often lands around ₹14-25 LPA (as of August 2026), mainly for Bengaluru and Pune. Some write-ups cite higher bands for certain offers. The written offer letter is the only number that matters.
Do I have to relocate to Bengaluru or Pune?
Those are the main India hubs candidates report. HR usually checks relocation willingness and joining logistics. Be honest about constraints early.
Prep & MathWorks-specific
How should I prepare for MathWorks EDG?
Split time roughly 40% DSA, 25% MATLAB/core, 20% C/OOP, 15% EDG/HR/GD. Clear timed OA mocks first. Keep one coding language. Details: preparation guide.
Which programming languages are allowed?
MATLAB, C++, Python, and Java are the usual set. Some coding-only sections historically restrict the list. Confirm on the invite. Do not switch languages the week of the drive.
What is EDG and how is it different from a normal SDE role?
Engineering Development Group is a rotational early-career program: customer application support on MATLAB/Simulink, projects with product teams, then specialization. You still code. You also need to enjoy explaining tools to engineers.
Do I need MATLAB to get selected?
It is a plus, not always a hard gate. You can survive OA in C++/Java/Python. You should still explain MATLAB/Simulink in plain language and not fake a toolbox list.
CS track vs Core Engineering - which should I pick?
Pick the track whose interviews you can defend. CS: DSA, OOP, systems. Core: control, signals, embedded, numerics, plus enough coding for OA. Switching stories mid-loop looks messy.
How is MathWorks different from Google or Siemens for freshers?
All three can ask real coding. MathWorks adds scientific computing + teaching-tools culture (MATLAB/Simulink). Google is general product/SWE at a different bar. Siemens (and similar industrial software) may lean more embedded/automation. Prep DSA for all; customise the EDG story for MathWorks.
Any pro tip that actually changes outcomes?
Watch the PPT, bank both OA coding problems, keep an error log, and rehearse one “slow simulation / confused user” explanation before technical. Correctness under time beats a half-finished clever solution - and never walk in thinking “MATLAB company = easy MCQs.”
Where can I read real interview experiences?
Start with MathWorks interview experience on this site, then cross-check recent GeeksforGeeks EDG write-ups. Patterns shift by year - use them as maps, not scripts.
MathWorks - recent candidate experiences
Campus edg loops
Profile patterns that got selected: B.Tech CSE/ECE/core mix, roughly 7.6-8.5 CGPA, one internship or a strong numerical/software project, steady DSA rather than last-week panic, and a sentence about why EDG that was not “I love MATLAB” with zero examples.
Online test: Timed coding on HackerRank. Clean, fully passing solutions beat partial cleverness. Students who triaged prompts early kept both coding and aptitude alive. Pseudocode punished rusty C.
Later rounds: GD on education/tech topics; HR on higher studies and location; managerial as a conversation; technical with live coding (search/DP/arrays), C/OOP, and project grilling. PPT facts showed up. Order was not the same for every student - knockout either way.
Takeaway candidates repeated: clear DSA plus a coherent “I like helping engineers use tools” story beats a high CGPA with weak explanation. Talking through the approach before coding mattered as much as the final snippet.
What hurt other candidates in the same cycles: coding before clarifying constraints; treating GD as optional chatter; claiming MATLAB fluency then failing basic indexing; freezing on pointers; saying they want EDG because they want to avoid coding; ignoring the PPT.
Public write-up colour
A widely cited GeeksforGeeks MathWorks EDG on-campus FTE account describes CS vs Core track after PPT, then knockout rounds in any order: GD, HR, managerial conversation, and technical. Selected students included FTE + intern mixes.
A GeeksforGeeks EDG intern write-up matches the OA shape this hub uses: aptitude + 2 coding + pseudocode, then GD → HR (EDG role depth) → managerial → ~1.5h technical with live coding and C/OOP.
Freshers should not copy US intern HireVue + MATLAB-section papers blindly - but the signals transfer: passing tests, C literacy, and EDG communication.
More fresher narratives: MathWorks interview experience.