
Fungible Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Fungible.
Senior Software Engineer
It started with a technical phone screen, then there were two rounds of on-site interviews. The questions were mostly technical, not very behavioral, and of average difficulty. They were mostly specific to the job. It seemed like they were quite busy because two of the interviewers couldn't make it and had to be replaced. I got the offer about two weeks after the last interview.
- Can you detail the TCP connection establishment and teardown process?
Software Engineer
Applied through referral... had about 5 interviews over 3 visits spanning across weeks. Not particularly challenging... very standard coding questions. Overall experience was good. One interviewer wasn't up to the task, had to correct his ideas and reasoning, and that messed him up. Cannot imagine working with such individuals. Everything went fine, 100% skill match but didn't get. May be because of one question I asked everyone....'Is there a requirement to work on weekends...!!'. Of course there's no official policy but they work on weekends..... a 'no no' for me... I will work hard but not on the weekends.... after all there are only 100s of weekend to enjoy... :)
- Standard questions... spend few weeks on leetcode/geeksforgeeks/interviewbit... you'll ace the coding... but that's not what they are looking for :)
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.
Fungible Software Engineer Interview Questions
Quoted word for word from Fungible interview reports.
“What distinguishes a hub from a switch?”
Read reports →“How does OpenFlow assist in networking?”
Read reports →“How would you create a calculator using a tree data structure?”
Read reports →“Can you explain VXLAN, including its functionality and necessity?”
Read reports →“Describe the usage of OpenStack.”
Read report →“Can you detail the TCP connection establishment and teardown process?”
Read report →“How would you implement the algorithm to find the best day to sell a stock if provided with its chart?”
Read report →“Can you explain the network stack?”
Read report →“Can you discuss some basic L2 lookup concepts?”
Read report →Formats, difficulty and experience
Across all 11 Fungible interview reports.