Getting an Interview
Getting an Interview
Interviews for Top Jobs at Intel Corporation
- Process Engineer (193)
- Software Engineer (162)
- Intern (98)
- Component Design Engineer (73)
- Financial Analyst (47)
- Senior Process Engineer (41)
- Manufacturing Technician (37)
- Engineering (36)
- Hardware Engineer (34)
- Graduate Technical Intern (24)
- Design Engineer (23)
- Senior Software Engineer (23)
- Engineer (21)
- Senior Financial Analyst (20)
- Product Development Engineer (20)
- Graduate Technical (19)
- Validation Engineer (18)
- Process TD Engineer (18)
- Systems Validation Engineer (17)
- Software Developer (16)
- Software Engineer Intern (13)
- Physical Design Engineer (11)
- Applications Developer (11)
- Analog Engineer (10)
- Systems Engineer (10)
- Graphics Hardware Engineer (10)
- Test Engineer (9)
- Research Scientist (8)
- Software Engineering Intern (7)
- Graphics Software Engineer (7)
- Accepted OfferPositive ExperienceAverage Interview
I applied online. The process took 3 days. I interviewed at Intel Corporation (Folsom, CA).
One on one interviews. Engineers and managers would sit down and ask you questions. Questions ranged from solving a math problem to questions on game theory. Lasted 3 days
- How would you solve a technical issue Answer Question
- Accepted OfferPositive ExperienceDifficult Interview
I applied online. The process took 3 weeks. I interviewed at Intel Corporation (Folsom, CA) in September 2015.
I got a call by mailing HR. There was a 1.5 hour phone screening after which I was called on-site to Folsom. There were 4 rounds and a lunch with the team. Got the results just 2 days after the interview.
- Phone interview - 2 projects on resume, Mealy and Moore, FSM for a given sequence, basic cache related questions, setup hold, how to fix them, SRAM DRAM, SRAM full operation, Unix commands grep, chmod, chop, chomp, ps. Onsite - Round 1 - Behavioral round. He was an engineer at Intel for 22 years. But he mostly asked about my resume and behavioral questions. He wanted me to ask him a lot of questions. Round 2 - Lunch with 8 members of the team. Just casual discussion about Folsom and my school and work at Intel. Round 3 - Complete Physical Design. Starting from the flow, she asked me every aspect of it. What are inputs to floorplan? Will it help if these inputs are available at Synthesis stage itself? what is clock tree synthesis? why is it done after placing? timing questions. How is power structure decided at floorplan? voltage delay dependence, inverted temperature dependence, sizing of gates, CMOS fabrication process and diagram, layout for CMOS. Round 4 - Timing in more detail and more difficult questions, inverter vs buffer, SRAM layout, why higher metal for Vdd Gnd? Why resistance is lower for higher metal layers? spef saif formats, verification basics, reliability verification, functional verification. Round 5 - Perl questions. Gave a file and asked me to extract few details using regex. Then had to use hashes to perform some operations on the extracted data. basic C++ questions and simple programs. Answer Question
- Accepted OfferPositive ExperienceEasy Interview
I applied through an employee referral. The process took 4+ weeks. I interviewed at Intel Corporation (Folsom, CA) in July 2015.
Phone screening.I got the offer thru employee reference and one of the team member called and asked some basic questions and gave me coding exercises.He spoke about the team and its work.
- Polymorphism 1 Answer
Helpful (1)No OfferPositive ExperienceAverage Interview
I applied through a staffing agency. The process took 2 weeks. I interviewed at Intel Corporation (Folsom, CA) in June 2015.
face 2 face interview through kelly IT. two interview panel. They ask me to write code and then discuss my Experience. And in 2nd room again ask me to write code and below questions.
- Q: Write program code in any language about grading system. Q: swap the value without using temp variable Q: what is difference between linear and binary search. Q: Explain Linklist. 1 Answer
- No OfferPositive ExperienceAverage Interview
I applied through an employee referral. The process took 2 days. I interviewed at Intel Corporation (Sacramento, CA) in June 2015.
Internal, many candidates that match the criteria. First round panel with 3 managers then a 1 on 1 with senior controller that probe every skill you need to succeed. You need to prepare very well and know the product road map, understand the customer and be able to provide good examples that showcase your skills.
- Example showing leadership Answer Question
- No OfferNeutral ExperienceDifficult Interview
I applied through an employee referral. The process took a week. I interviewed at Intel Corporation (Folsom, CA) in June 2015.
Interview was scheduled for 3 hours. I met with 6 different people, 30 minutes each. These went from management to technical people, so interview technical difficulty increased with each new interviewer. Overall, this approach was less stressful than the panel type interview, but it was the first time I had experienced this type.
- How would you write a script to test a particular item on a linux server, then reboot the server and recheck the same test after the reboot? Answer Question
- No OfferNeutral ExperienceEasy Interview
I applied through an employee referral. The process took 2+ weeks. I interviewed at Intel Corporation (Folsom, CA) in June 2015.
A 20 min phone interview followed by a in-person turn around by six or seven different 1:1 and group. After I didn't get an offer they handed over my resume to another department of them where my experience with them was quite awful. But this one was a normal job interview and no offer case that I it would be great if I was hired. The hiring Engineer was a great person (his name was JL) and I enjoyed his personality.
- No OfferNeutral ExperienceAverage Interview
I applied online. The process took 2 weeks. I interviewed at Intel Corporation (Sacramento, CA) in June 2015.
I submitted a resume online. I had one phone screen interview with the hiring manager, that ended up being his only interview of me, so I wish I could have been more prepared than I was and told him more. Then interviewed by 4 team members individually each with a different focus of their questions. technical skills business skills, knowledge of the product, and personality type questions.
- what was my experience with the product? What would I do to market the product? What technology did I have in my home. What was in my home computer. Describe my experiences working with external customers. Answer Question
Helpful (14)Accepted OfferPositive ExperienceAverage Interview
I applied through an employee referral. The process took 3+ months. I interviewed at Intel Corporation (Folsom, CA) in April 2015.
I applied trough my friend. After 3 months, I got a call for phone call interview (1hr). I answered all the questions. Next day, I got confirmation for Onsite Interview. I had 10 days to prepare. After 2 days, I got the confirmation.
- Phone call Interview: Physical Design Flow. What problems did you face ? How to remove Setup violation ? How to remove Hold violation ? Unix commands: ls, cp, grep what is the command to check processes running ? How to run process in background ? softlink command how to check disk usage ? Perl questions: chop vs chomp array, hash, default scalar sign. what is th difference between array and hash when we do indexing ? Logic: he gave me one boolean exp to solve. latch vs flop sram vs dram ? which one is volatile? D FF using MUX D FF operation Comp Arch: pipeline ? cache ? virtual memory ? TLB ? what is the set size for fully associative cache ? Direct associative ? he had given me configuration. Verilog: blocking vs nonblocking initial block ? always ? FSM for 0101. moore vs mealy ?(mealy is prone to glitches. This is what he wanted to hear) verilog code for DFF. Physical: electromigration. setup. hold time, skew ? effect of length, width, thickness on resistance. effect of temp, voltage on Delay. Onsite: First round: she was also Trojan :-) (USC Fight On) tell me about urself. why this transition ? (undergrad in Elec&tele, job in software and MS in EE) Physical Design flow ? what to do to remove setup violation? Hold violation ? sizing, MOS structure, VI curve, effect of voltage on delay, temp on delay ? problem on setup and hold using delay values. power minimization techniques. She was going in depth. Thats it. Second round: Unix commands: how to find .txt files, copy files from one directory to another. find files with particular string. how to execute unix commands in perl script ? (ANS: use exec before each unix command and done) use strict ? what is tht #! usr/bin/perl we write at the start of program ? C vs perl ? Read the file(set up vioations). there are 1000 lines in that file. Print 5 worst delays. array vs linked list with respect to memory allocation. pipeline ? stages ? which CPU is better ? 1GHz vs 2 GHz. Third round: Physical design flow. behavioral: situation when you had conflict with your friend. how you handled situation. how you divide work while working in group. how will you avoid conflict ? (Divide work) how you do finish work before deadline? when you start working on something, you get some problems, you solve it then how do you avoid same mistake in future.(I will note it down. he wanted to hear this) skew, seup time, hold time. Fourth round: Physical Design Flow, synthesis steps, APR steps, problems related to setup and skew. Answer Question
Helpful (1)Accepted OfferPositive ExperienceAverage Interview
I applied through an employee referral. The process took 3 weeks. I interviewed at Intel Corporation (Folsom, CA) in May 2015.
Asked a lot about verilog, system verilog, Unix and perl scripting. Also focused on circuit design concepts and fundamentals in VLSI design, comp arch, HDVL. Was a very good interview. The manager gave a lot of time for me to think through and I felt very comfortable. Brush up on verilog and system verilog before giving the interview.
- Timing analysis, Setup and hold time. Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review