Truelogic Software Solutions Frontend Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

3.4 Rounds average

Average Typical difficulty

60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Truelogic Software Solutions.

Showing 3 of 5

Truelogic Software Solutions

Senior Frontend Developer

Engineering · a year ago

Senior Average Neutral experience No offer 3 rounds

Interview process

Recruiter call Technical screen Take home

Interview formats

Technical Coding

So I had this interview, first with HR, then a logic test on HackerRank, followed by a technical interview where they asked me about TypeScript and the framework for the role. There was another logic test at the end. I passed all that and they sent my resume to the client, but then they just ghosted me without saying anything about not being chosen to talk to the client.

Confirmed questions1 question

Can you explain the difference between types and interfaces?

Truelogic Software Solutions

Front End Developer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 5 rounds

Interview process

Recruiter call Phone screen Technical screen Onsite Offer

Interview formats

Technical Behavioral

The process was okay but really slow, taking about a month between each step, and I didn't get any updates on how things were going. Someone reached out to me on LinkedIn, and then I went through a few interviews: a phone screen, a 1:1, a technical interview, an interview with the client, and finally, we talked about the contract and my rate.

Confirmed questions4 questions

Could you let me know your notice period?
What is your expected hourly rate?
Can you list the technologies you have experience with?

Truelogic Software Solutions

Front End Developer

Engineering

Entry Difficult Negative experience No offer 2 rounds

Interview process

Recruiter call Technical screen

Interview formats

Behavioral Coding

This is a complete waste of time. First, you're asked to talk about your entire career, and then you end up in a technical interview doing a live coding challenge where you have to guess what the interviewer wants. You need to think about multiple things in a short amount of time. It's required to optimize an application that you build from scratch while also trying to make it work. It's the most stupid way to interview a developer. Don't waste your time here.

Confirmed questions2 questions