
Fungible Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 24 interview experiences · FREE TO READ
Which role are you interviewing for?
6 roles · 24 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Fungible.
Hardware Verification Engineer
I was rejected after the second round. Here's my take: Round 1 was pretty much about setting expectations and looking at my resume. The interviewer was nice and seemed technically knowledgeable. They asked questions directly from my resume and gave me a quick overview of their product. Round 2, I didn't really vibe with the interviewer's style. They were loud and seemed self-centered, more focused on showing off than understanding my skills. They were also impatient, and the video call quality was bad with lots of background noise. However, I will say they seemed to know their stuff about SV and UVM, technically speaking, but their interviewing skills weren't great.
- Could you elaborate on SV and UVM concepts?
- Explain the sequencer grab mechanism.
- Describe the UVM topology.
Software Engineer
The interview process was very fast, starting with a preliminary coding exercise followed by an onsite interview. My friends spoke highly of this company, so I had high expectations. Unfortunately, I felt I encountered two unsuitable interviewers. The first interviewer seemed confused about array pointers versus pointers to arrays. Despite my confidence in my answer, we debated extensively as he persisted with an incorrect approach. He mentioned that no prior interviewee had ever provided a correct answer, which I found amusing given my certainty. This experience highlighted a lack of openness to new ideas, and I believe companies should vet their interviewers for suitability. This initial interview alone was enough for me to decide against joining that particular team. The second interviewer was pleasant, with a strong grasp of concepts, and he asked me about multithreading programming. Recognizing my limited experience in this area, he was supportive, and we discussed the problem collaboratively. The third interviewer was indifferent; due to my negative experience with the first, I was disengaged and paid little attention. He spent the entire time looking at his computer instead of the whiteboard, which I found rude considering I was investing my time and making a critical decision about my career. It felt disrespectful, and I even considered leaving. Overall, it was a poor experience. While I can't comment on the company as a whole, the two interviewers were clearly not a good fit for their roles. My advice to the company is to diversify interviewers and discourage the use of laptops or phones during interviews, as it's unprofessional and disrespectful. Be more open to alternative solutions; established methods aren't always the only or best ones. I'm unsure of the outcome and frankly, it doesn't matter to me at this point.
- I can't share the exact questions due to NDA, but they were typical data structure and algorithmic problems, likely sourced verbatim from online resources.
- Standard data structure and algorithmic questions.
ASIC Verification Engineer
I had a phone round and then 4 on-site rounds. The phone interview was great, the interviewer was friendly and interested in my background. However, one of the on-site interviews was really negative. The interviewer hadn't even looked at my resume before and seemed unprepared, reading it with me there. They were condescending, implying my resume wasn't interesting enough. I felt they disrespected me, my experience, and my projects, and the effort I put in to be there. That one interviewer made me lose all respect for the company.
- Which of your projects would you like me to ask about?
Software QA Engineer
I had an on-site screen initially, then a full interview with 4 people from both QA and Dev teams. The final round was a meeting with the head of software. Everyone was nice and professional. The interview questions were reasonable and would be easy if you have a deep understanding of the domain. Some coding questions were challenging but interesting and practical. I feel the interview is a mutual process where I also get to interview them. They want to hire smart and qualified people, and I feel the same way.
- Why did you choose Fungible compared to other companies?
Fungible Interview Questions
Quoted word for word from Fungible interview reports.
“What distinguishes a hub from a switch?”
Read reports →“Can you explain Linux commands with options like -h, -l etc.?”
Read reports →“How does OpenFlow assist in networking?”
Read reports →“How would you use 5L and 3L jars to get 4L?”
Read reports →“How would you create a calculator using a tree data structure?”
Read report →“Describe the UVM topology.”
Read report →“Explain the sequencer grab mechanism.”
Read report →“Can you explain VXLAN, including its functionality and necessity?”
Read report →“Describe the usage of OpenStack.”
Read report →Formats, difficulty and experience
Across all 24 Fungible interview reports.