
fabric Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at fabric.
Software Engineer
So I applied online and then a recruiter hit me up for a phone screen first. They wanted to talk about the job and see if I was interested and what my goals were. After that, I had a chat with the hiring manager, no tech stuff, just to go over my past work and projects. The final interviews were 3 parts: 2 coding and 1 low-level OOP design. The first coding interview was pretty standard, like easy to medium LeetCode. The second coding interview was more creative, with the problem relating to something from the real world. The low-level design part was about basic OOP ideas and how to build a system using some provided APIs. The interviewers were nice enough, but honestly, they weren't super helpful during the interviews. They'd either just sit there watching me code or ask really vague questions without giving any hints on what they were looking for.
- Leetcode problems of easy/medium difficulty
- A coding problem that's open-ended and relates to a real-world scenario
- Low-level OOP design questions
Senior Software Engineer
The interview process was really smooth. It kicked off with an intro call from HR, who was super enthusiastic and detailed about everything. After that, there were three main rounds: first, a coding round, then a combined coding and Low-Level Design (LLD) round, and finally a High-Level Design (HLD) round. Each round lasted about an hour, and the interviewers were helpful with feedback and explanations. I got an offer which was pretty good, but I couldn't accept it for personal reasons. I'd definitely be interested in working here again if I get the chance.
No confirmed questions were included in this interview report.
Software Engineer
HR reached out to me for this role and they were super professional in scheduling interviews, which I really liked. There were 4 rounds in total. The first round had some JavaScript questions, including 4 problem-solving ones. The second round featured some front-end design questions along with another problem-solving question. In the third round, we talked about design systems and they asked some backend questions. The final round was with the Engineering Lead and included both backend and frontend questions, but no problem-solving this time. The whole thing took about two weeks, and I was pleased with how it went. Everyone from HR to the Engineering Lead was professional, friendly, and made me feel comfortable, so there wasn't any pressure.
- Could you tell me about your experience with Arrays?
- Let's discuss Recursion.
- What are your thoughts on Design Systems?
fabric Software Engineer Interview Questions
Quoted word for word from fabric interview reports.
“What are the basic principles of linked lists?”
Read reports →“What are the core concepts in Node.js?”
Read reports →“What are the basic concepts of Javascript?”
Read reports →“What are the basic concepts related to databases?”
Read reports →“Solve these 3 problems in JS.”
Read report →“Design a system with given APIs”
Read report →“Could you explain the fundamental concepts of MySQL?”
Read report →“Could you explain the fundamental concepts of Data Structures and Algorithms (DSA)?”
Read report →“How would you explain Object-Oriented Programming?”
Read report →Formats, difficulty and experience
Across all 15 fabric interview reports.