
Forma Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 18 interview experiences · FREE TO READ
Which role are you interviewing for?
9 roles · 18 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Forma.
Operations Analyst
The interview concentrated on DSA, OOP, and machine learning ideas, plus project talks about ECSR and AGC-NET. I explained how things were done and showed I could solve problems and knew the practical stuff well. They asked about projects.
- Why are you interested in this role?
- Can you explain your understanding of DSA?
- What are your thoughts on OOP?
Customer Operations Specialist
So first you'll have a chat with the hiring manager for about 45 to 60 minutes. Then there's a technical or operations assessment, which can vary. It might include a data accuracy/QA test, a workflow simulation where you'll have to triage tickets, prioritize them, and show your communication style. They might also give you a scenario-based troubleshooting problem. There's also a short written exercise to check how clearly you communicate. After that, you'll have a cross-functional panel interview lasting 60 to 90 minutes, meeting people from Engineering, Product, Customer Success, and Support leadership. Finally, there's a 30–45 minute interview for a culture fit.
- Can you explain a complicated process in an easy-to-understand manner?
System Administrator
I applied for a System Administrator job and cleared the initial phone screen. Then I talked to the hiring manager, and it seemed to be going great. After that, I was given a take-home assignment that I spent a lot of time and effort on. They said they would set up a time to talk about the assignment, but I never heard back from them. It's super frustrating and discouraging to feel like my work and time were exploited without any response. This whole thing made me feel used and unvalued.
- Tell me about your IT experience.
- Respond to some technical questions.
Software Engineer
The interview process for this Software Engineer role included two main stages: a phone screen and a technical screen. The phone screen was pretty standard, covering introductions, what the candidate is seeking, and what Twic is looking for. The tech screen had two parts: a programming challenge that was more of a practical exercise or a simple algorithm, where looking up syntax was fine, and then a design portion. The design part was whiteboard-style, focusing on system/API design, and it was all about explaining the architecture and how to handle scaling and reliability. Everyone was really friendly throughout, and a big part of the interviews was seeing how well candidates could explain their ideas.
- Questions were similar to LeetCode Easy.
- Questions were similar to topics in 'System Design Primer' on GitHub.
Forma Interview Questions
Quoted word for word from Forma interview reports.
“What is your definition of customer support?”
Read reports →“Can you explain your understanding of DSA?”
Read reports →“Can you explain the difference between a good product and an okay product, with an example?”
Read reports →“What are your thoughts on OOP?”
Read reports →“Could you discuss some machine learning concepts?”
Read report →“Describe a situation where a client expressed dissatisfaction with the product or service.”
Read report →“Can you explain a complicated process in an easy-to-understand manner?”
Read report →“Can you describe your work on the AGC-NET project?”
Read report →“Why are you interested in Twic?”
Read report →Formats, difficulty and experience
Across all 18 Forma interview reports.