Forsta logo

Forsta Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 10 interview experiences · FREE TO READ

2.4 Rounds average
Easy Typical difficulty
30% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Forsta.

Showing 3 of 10
Forsta logo
Forsta

Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Technical screen Onsite Background check
Interview formats
Coding Behavioral

I had an interview with the tech team in February and really enjoyed speaking with them, though I didn't end up getting an offer. The interview had two parts: one on Python and one on React. The entire principal team, about six or seven people, watched me solve coding problems. For Python, I had to fix a bug in a Flask project using Replit, explaining my process as I went. The React part was similar, with a new project that had three bugs I needed to fix. After the coding, we had plenty of time for behavioral questions and discussions on various topics. They were friendly, cracked jokes, and I felt a good connection. I really wanted to work there. They said I did well but wanted to interview more people and kept me in consideration. They kept me waiting for almost two months, which was disappointing, before they finally chose someone else. I get they need to find the right cultural fit and someone to help achieve company goals, but the long wait before the rejection was tough.

Confirmed questions1 question
  • What do you envision yourself doing in five years?
Forsta logo
Forsta

Software Developer

Engineering · more than a year ago

Mid Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite Offer
Interview formats
Behavioral Technical Coding

I got an interview for a developer job in Fresno. Finding the place was tough, but a phone call got me good directions. Two managers interviewed me, asking usual stuff and a lot of technical questions about my programming skills. They were okay with me not knowing everything. It was a smooth and comfortable interview because I know my stuff and the interviewers were friendly. There was a timed coding test to check my skills, and the time felt fair. Then the department head talked to me about the company's benefits and values, which was a nice change from me having to sell myself. A few days later, I got a phone call with an offer based on my skills, then a formal offer letter. This was before the company merger, so things might be different now.

Confirmed questions4 questions
  • Can you describe a particularly challenging project you've worked on?
  • What would you say is your biggest weakness?
  • Tell me about a challenging project you were part of.
Forsta logo
Forsta

Software Engineer

Engineering

Entry Easy Negative experience No offer 1 round
Interview process
Phone screen
Interview formats
Technical

It was a first phone call with some technical questions about APIs. API fundamentals, method differences. It was a first phone call with some technical questions about APIs. API fundamentals, method differences. It was a first phone call with some technical questions about APIs. API fundamentals, method differences.

Confirmed questions1 question
  • Regarding POST requests, where are their parameters stored?

Forsta Software Engineer Interview Questions

Quoted word for word from Forsta interview reports.

Regarding POST requests, where are their parameters stored?

Read reports

Can you write a function to determine if a hand of cards is a full house?

Read reports

Can you write a select statement to identify a gap in a sequence of numbers?

Read reports

Could you provide an example of your approach to state management?

Read report

Why did you move to Vancouver and why do you want to work for this company?

Read report

Formats, difficulty and experience

Across all 10 Forsta interview reports.

Interview formats

Technical 36.4%
Behavioral 31.8%
Coding 27.3%
Group 4.5%

Interview difficulty

Easy 50%
Average 50%
Difficult 0%

Candidate experience

Negative 70%
Positive 30%