Candidates for Mediatek software roles report interviews centered on C++ and systems fundamentals, project or thesis discussions, and coding or design problems, with the format varying by report.
$115K
Avg. Base Comp
$175K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Mediatek's software interviews, as candidates describe them, reward depth in systems fundamentals more than speed on puzzle-style coding. A Software Engineer I candidate who received an offer described an almost entirely technical conversation: pointers versus references, stack versus heap, when to choose unique_ptr over shared_ptr, virtual methods, abstract classes, and the pitfalls of multiple inheritance. The same candidate compared vector with list and map with unordered_map, worked through iterator invalidation, and was asked to implement a deque from scratch before moving on to threads, processes and deadlocks. Behavioral questions were minimal.
Another Software Engineer candidate opened by presenting a master's thesis and coursework, with follow-up questions drawn straight from what was covered. Technical questions then moved to computer architecture, CPU pipelines, embedded systems concepts, OS topics, and linker and compiler basics, along with an LRU cache problem that felt straightforward. That candidate came away feeling that coding carried less weight than domain understanding.
A third report, from a candidate listed as Senior Software Engineer, described three rounds. Two technical rounds covered data structures, algorithms and system design, and the final round mixed behavioral questions about past work and team dynamics with design at scale. That candidate did not receive an offer and found the tone varied between interviewers.
There are only a few software-focused reports and their formats differ, so read the job description closely and be ready to explain your own projects and the reasoning behind your answers.
Synthesized from 9 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Mediatek process.
The interview kicked off with me presenting a PowerPoint about my master's thesis and relevant coursework. The interviewers asked follow-up questions directly based on what I'd covered, which felt more conversational than interrogative—they seemed genuinely interested in my research background. After the presentation segment, we moved into technical territory: questions on computer architecture, CPU pipeline fundamentals, and embedded systems concepts. I was also asked to write code—I got a LeetCode-style problem (LRU cache), which was fairly straightforward since I'd seen it before. The technical rounds also included broader software engineering knowledge checks—OS concepts, linker and compiler basics, and how different components fit together. It seemed like coding wasn't weighted as heavily as deep technical understanding of my domain, so having solid answers on architecture, kernel objects, and system-level design mattered more than writing perfect code. The tone throughout was collaborative; at the end, the interviewer pitched their department and opened the floor for questions.
Prep tip from this candidate
Before your interview, prepare a strong technical presentation on your thesis or major projects and be ready for deep-dive questions on CPU pipeline, embedded systems, and OS concepts. Practice both easy coding problems (like simple loops) and medium problems like LRU cache, but prioritize understanding system-level architecture and linker/compiler fundamentals over raw coding speed.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Mediatek
How would you negotiate and resolve disagreements when a client rejects your proposed solution?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Prime to N | |
| Find the Missing Number | |
| Random SQL Sample | |
| Maximum Profit | |
| The Brackets Problem | |
| Upsell Transactions | |
| Over-Budget Projects | |
| Hurdles In Data Projects | |
| Recurring Character | |
| Scrambled Tickets | |
| Detecting ECG Tachycardia Runs | |
| Retailer Data Warehouse | |
| Employee Project Budgets | |
| Size of Joins | |
| Integer to Roman | |
| Sum to N | |
| Cyclic Detection | |
| Twenty Variants | |
| Find the First Non-Repeating Character in a String | |
| Equivalent Index | |
| Bagging vs Boosting | |
| Completed Shipments | |
| Get Top N Frequent Words | |
| Delivery Estimate Model | |
| One Element Removed | |
| Paired Products | |
| Groups of Anagrams |
Synthesized from candidate reports. Individual experiences may vary.
One Software Engineer candidate opened by presenting a PowerPoint on a master's thesis and relevant coursework. The interviewers asked follow-up questions based directly on what was presented, and the tone was conversational. Have a short walkthrough of your best project ready and be prepared to explain the decisions behind it.
An offer-receiving Software Engineer I candidate was asked about pointers and references, stack and heap, smart pointers, virtual methods, abstract classes, STL container differences and iterator invalidation, then threads, processes and deadlocks. Another candidate was asked about CPU pipelines, embedded systems, OS concepts, and linker and compiler basics.
Coding appeared alongside the conceptual questions rather than dominating them. One candidate was given an LRU cache problem and found it straightforward. Another was asked to implement a deque from scratch, which tested container internals more than algorithm tricks. A third described data structure and algorithm problems with follow-ups on complexity and edge cases.
The Senior Software Engineer-listed candidate described three rounds in total. The last one included a behavioral discussion about past work and team dynamics, plus design questions about building systems at scale. Interviewers were mostly senior engineers, and the candidate felt the tone differed from one interviewer to the next.
