Computer Engineering Interview Experiences

Flubbed the interrupt latency question.. Codesignal OA then two technical rounds. First was C and C++ questions on pointers and manual memory management. Second was operating systems, scheduling algorithms and interrupt handling. Good company if you want embedded over web.

Passed recruiter screen, first technical was graph BFS and solved it no issues but second technical had a really long problem statement like two pages and by the time I understood what they wanted I only had 20 minutes to code and didn't finish

GPU memory hierarchy, C++ templates and a design question about a parallel task queue. Technical interview was with a couple engineers after passing the OA (two medium coding questions on arrays and graphs). Waiting to hear back

Online coding test then technical interview, coding had dynamic programming and recursion and interview was walking through solutions and edge cases and a project from my resume done in 2 weeks

They dug into a resume project then gave me a 2D array problem where the interviewer kept pushing for better time complexity. couldn't get there

2 Rounds -- 30 Minutes Each R1) Standard behavioral questions / Resume Review -- Tell me about a time where X, tell me about X project on your resume etc. R2) Technical -- OOP Style questions, designing functions to fit some goal, required familiarity with inheritance, interfaces, protected methods, and writing functions. Psuedocode was accepted, did not write any business logic, just sketched out the functions

I had 2 rounds on interview, botn was medium Leetcode. The first question was the variation of Fizz Buzz, where we need to check multiple conditions before printing anything. The second question was design a template like google doc, where each line has a character limit, and if the word exceeds the limit it should be placed in the next line

Live coding for an hour 3 questions easy then 2 mediums both mediums on tree traversal then turned into a casual chat about hobbies and interests nice interviewer but stressful process due to them not saying anything during the coding part lol

all behavioral stuff like going above and beyond and time management and what I know about Qualcomm

42 question OA with MCQs on networking OOPs OS DBMS plus 2 coding. Spent too long on MCQs and barely had time for coding

They wanted OpenShift or IBM Cloud experience and I've mostly used GCP, I think that hurt me. Recruiter screen was a 20 min phone call, then the technical interview dug into cloud architecture.

Got stuck on the third C++ coding question and never made it to the tech interview. Phone screen first, then a coding test with three questions, passed two

Two separate teams interviewed me back to back, one on threat modeling and zero trust and one on behavioral questions about incident response. OA before that had networking security MCQs and a short scripting exercise. Applied 3 weeks ago, still waiting

Just a rejection email, no feedback. Questions were on jenkins pipelines, Ansible and cloud deployment patterns. Also a root cause analysis scenario for a production outage. Teams interview with the engineering team after a phone screen

Process took 3 weeks overall, pre screen and 2 follow up interviews. Leetcode hard question killed me in the end I think it was linked list related

Deeper than expected for a co-op. They walk you through their actual stack during the interview. GCP and containerization questions, also service mesh architecture. Had a coding component in the screen before the round with two engineers.

Standard behavioural and leadership principals and leetcode tagged. Tell me about yourself

Went through my senior project walkthrough, HR was quick just why Dayforce and career goals

Zoom maybe 20 min, one of the shorter interviwes I did this cycle. Project and experience walkthrough, some questions about automotive software interest. Resume discussion more than anything technical

Should have prepped more on the infrastructure side. Phone screen then two coding interviews, second one had virtualization questions and I clearly didn't know enough about hypervisors and VM scheduling. Not rude about it though

Coding assessment first, it was reverse a string and some OOP stuff. 30 min zoom after that, questions about my projects and some behavioral questions. laid back the interviewer seemed interested in my side projects

Two interviewers who were both in the leadership development program, questions about IPv4 vs IPv6 and then a bunch of stuff about how I'd handle disagreements with a supervisor. It was pretty conversational, like 50 minutes but it went by fast