MediaTek Interview Questions
& Process

So before the actual interview, there was like a C language test, and an English exam, and also a behavioral assessment that was multiple choice. Then for the interview itself, I had to do a PPT to introduce myself and my projects. They also asked me some questions about operating systems and CPU pipeline and also gave me an introduction to the department.

The interview process involved an initial MCQ test covering C, embedded C, OS, computer architecture, and computer security. This was followed by a second round. The second round began with general questions about introductions, projects, C programming concepts like null and void pointers, string length calculation, and number reversal. It then delved into C storage classes and their usage. Subsequently, an interviewer focused on Embedded C, revisiting storage classes and covering bitwise operators, embedded C projects, interrupts, and RTOS.

So, to get ready for MediaTek's interviews, you'll go through a few rounds. They really look at your technical skills, how you solve problems, and if you know your computer science basics. You should really brush up on C++ stuff like pointers vs references, stack vs heap memory, smart pointers (unique_ptr, shared_ptr, weak_ptr), and rvalue/lvalue with std::move/forward. Also, OOP concepts are big – like accessing private members, multiple inheritance, virtual methods/destructors, and abstract classes vs interfaces. Don't forget the STL: vector vs list, map vs unordered_map, iterator invalidation (especially for vector), and what makes a custom type usable as a map key. Concurrency is also important: know processes vs threads, how to sync threads, and how to avoid deadlocks. It's a good idea to look at past questions from MediaTek interviews. Practicing coding problems on LeetCode, HackerRank, or Codeforces will sharpen your analytical skills. Make sure you've got a good handle on OS concepts like sync, deadlocks, and memory management. Be ready for behavioral questions too – think about your strengths, weaknesses, and how you've handled tough spots. Using good resources like Toptal for C++ questions is smart. And seriously, do some mock interviews to get used to the timing and practice answering questions.

I applied for the Fullstack Engineer Intern role through my school's career system. The interview process was really bad. The interviewer was 30 minutes late, which was weird for a big company. The interview was awkward. The main interviewer spoke poorly and didn't seem interested. The questions weren't very technical. They asked me to talk about my past projects, show my GitHub, and rate my own Python skills. When I answered questions, they'd just be silent and not give feedback. Their next questions sometimes didn't even relate to what we were talking about. It was also misleading because the role was supposed to be Full Stack but they only wanted frontend work, which wasn't what the job description said. The interviewer said I was a top candidate and I'd hear back in two weeks, but I never did. It was super unprofessional. Worst interview ever.