I had a phone screen with the recruiter followed by two phone screens and then the final onsite. I would say that up until and including the first interview i had as part of the onsite was very pleasant. As for the interview process, I think its important to keep a sense of professionalism with regards to a candidate's answer with regards to technical questions. After being unable to answer a question with two interviewers, they tried to abruptly end the interview. Not that one should get their hopes up obviously if they can't answer a question accurately, however it really did make them come off as arrogant. A great example is when one of the interviewers I had expressed his frustration with me not knowing about regex even though I had a web crawling project on my resume. Although regex is an approach, you can also check to see if a specific string is a substring of a larger string. I would've hoped that considering Factual uses a plethora of technologies, that they would realize there are alternative approaches and not just give me the cold shoulder since I didn't know about their approach. Because of this, I decided to drop the ball on the rest of my interviews. One of them said good luck on the job search and finding a fit. From what I could tell about the company during my onsite, expect nothing out of the ordinary from any startup: snacks/drinks, catered meals, not many red tapes to go through, and really just a lot of freedom. As for the questions they asked, without giving anything away, expect something straight from your college level coding textbook, a leetcode medium/hard level question, and two design questions. The design questions were definitely more appropriate for mid/senior level folks. Thus, for anyone applying for a entry level role, I do wish you luck if you are not comfortable in all parts of the stack. Considering not everyone out there is completely full-stack, I guess I do see why there were so many people who got declined an offer on glassdoor and why Factual is the size it is, despite it being almost a decade. As technical interviews don't always show a person's aptitude for success in a company ( for startups, from personal experience, I believe it's really about how much of a self-starter you are), I think Factual should ask more appropriate questions for entry level roles ( most companies do ask OOP design questions). Additionally, it would've been great if more people had asked me about my resume instead of rushing into the technical questions. Lastly, I'd say that really would've appreciated an email instead of a phone call, especially since they had asked for my availability the following week to recap what happened about my status. Taking the time to see what a candidate's schedule is like despite knowing immediately about the feedback from the interviewers is definitely a bad move on their part. I read below that someone from Factual thought it was better to have a phone call than an abrupt email. If that's the case, then why don't most companies do this...? At the end of the day, for anybody else reading this, do remember that companies want more people and aren't deliberately trying to make people fail. It is a learning process, and considering that Factual has been around for almost a decade, I'd imagine their engineering team will stay around the same for a while/into the future whilst growing their sales team. I had heard that engineering is around 40% whilst everyone else being 60%. I don't doubt the possibility that engineering would hit 10% in the future. I do wish them luck in hiring and look forward to seeing what most people say about interviewing with Factual in the future ( I'd imagine I won't be too surprised ).