Sign In Solutions logo

Sign In Solutions Software Engineer Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
83.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Sign In Solutions.

Showing 3 of 6
Sign In Solutions logo
Sign In Solutions

Software Developer

Engineering · a year ago

Entry Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Onsite Panel
Interview formats
Behavioral

It started with a quick chat with HR. Then I met with the Tech leads in person. The last part was an interview with the CTO and CEO. The vibe was pretty relaxed, and it mostly felt like a casual conversation to see if I'd be a good fit personality-wise and culturally.

Confirmed questions1 question
  • What's your motivation for joining this company?
Sign In Solutions logo
Sign In Solutions

Software Developer

Engineering · more than a year ago

Mid Easy Positive experience Accept offer 5 rounds
Interview process
Recruiter call Take home Technical screen Presentation Panel
Interview formats
Coding Technical Presentation Behavioral

First there was an intro interview, then I had to do an open-ended coding assignment. After that, a technical interview. Then, I demoed my coding assignment to some of the company's developers and answered their questions about architecture and implementation. Finally, there was a culture interview over breakfast.

Confirmed questions2 questions
  • Asked to build an application that consumes a rest API
  • Asked technical questions about architecture and implementation for the coding assignment
Sign In Solutions logo
Sign In Solutions

Software Engineer

Engineering

Senior Average Neutral experience No offer 2 rounds
Interview process
Take home Recruiter call Technical screen
Interview formats
Coding Behavioral Technical

They sent me an invitation for an interview along with a Google doc containing 10 javascript questions to answer and send back. The actual interview focused on discussing the role and my experience, referencing the technical test I'd submitted. The technical part went well because they stuck to questions related to the test. They seemed more interested in my past projects and why I was looking to change jobs. After two days, I got a rejection email citing a high volume of applications.

Confirmed questions7 questions
  • Explain the difference between the equality operators == and ===.
  • What is the difference between the values undefined and null?
  • Could you describe the difference between var and let keywords?

Sign In Solutions Software Engineer Interview Questions

Quoted word for word from Sign In Solutions interview reports.

What is the difference between the values undefined and null?

Read reports

Explain the difference between the equality operators == and ===.

Read reports

How does state management work in React? Can we set state without using setState?

Read reports

Explain the mechanism of state management in React. Is it possible to update the state without calling setState?

Read report

Could you describe the difference between var and let keywords?

Read report

How does a website remember your identity after you log in?

Read report

Describe the functionality of the array methods .map(), .filter(), and .reduce().

Read report

What would you have done differently on the project given more time?

Read report

Formats, difficulty and experience

Across all 6 Sign In Solutions interview reports.

Interview formats

Behavioral 37.5%
Technical 31.2%
Presentation 18.8%
Coding 12.5%

Interview difficulty

Easy 33.3%
Average 66.7%
Difficult 0%

Candidate experience

Positive 83.3%
Neutral 16.7%