Sign In Solutions logo

Sign In Solutions Interview Questions
& Process

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

Based on 45 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
84.4% Positive experience

Which role are you interviewing for?

18 roles · 45 reports

Candidate interview experiences

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

Showing 4 of 45
Sign In Solutions logo
Sign In Solutions

Quality Assurance Analyst

Engineering · more than a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Presentation Panel Group Background check
Interview formats
Technical Coding Presentation Behavioral Group

The interviews were quite thorough. If you genuinely had experience in the skills on your resume, it was pretty straightforward as the questions were designed so only someone who actually worked with the tech/tool/skill could answer them. The interviewers were super nice, calm, and chill, which gave me a good feel for the company culture (which is awesome btw!!). Round 1 was a technical interview via video call. After clearing Round 1, I got an assignment to demo to a panel. Round 2 was the Demo of the Assignment. Round 3 was a Cultural Interview. Round 1 had all the QA and QE questions, really focusing on the skills and tools I listed on my resume. After Round 1, I got an assignment to demo. The assignment seemed easy, but I figured they'd be looking for extra effort on things not explicitly asked for, stuff an experienced person would know to include. I demoed to a polite panel who watched closely and asked questions based on my presentation. After clearing Round 2, I got an invite for my Cultural Round in Jaipur. I hadn't done a cultural round before, so I wasn't sure what to expect, but after some searching, I realized it's basically a way for both the candidate and the company to get to know each other better as future colleagues and see if it's a good fit. The cultural round was fun and exciting. Our onsite counterparts and 3 senior folks from Jaipur were on the panel. We chatted about anything *but* what was on the resume, focusing on our interests, passions, and sharing experiences. The whole process was thorough but also fun and exciting.

Confirmed questions8 questions
  • Can you tell us a bit about yourself?
  • What's your approach when a developer disagrees with a defect you've reported?
  • Can you give examples of issues that are low severity but high priority?
Sign In Solutions logo
Sign In Solutions

IOS Developer

Engineering

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Onsite Take home Technical screen Group
Interview formats
Behavioral Technical Presentation Other

The whole process was composed of 5 steps. It starts with a phone screening with a HR recruiter. Secondly, a in-person meeting with the CTO. Then, a home assignment (in my case, to build a mobile app) followed by a demo/interview with the technical team. And finally a cultural fit breakfast with different members of the company. What most impressed me in the whole process is how they treat you differently. No "good cop/bad cop" with someone trying to intimidate you or adding unnecessary pressure to see how you will behave. The company implements the culture of "we are cool, if you are too we will want you on the team". And what is even better is that the same treatment is given to you after you join the company. It doesn't stop in the hiring process. Which is awesome!!

Confirmed questions5 questions
  • Can you explain the architecture of your demo app?
  • How do you approach debugging your code?
  • What challenges did you face while working on the demo app?
Sign In Solutions logo
Sign In Solutions

DevOps Engineer

Engineering

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Presentation Group Background check Offer
Interview formats
Behavioral Technical Presentation Group

After a recruiter intro and a first phone screen, I had a 1:1 with the CTO. This initial on-site was pretty laid-back, mostly chatting about personality, past experiences, and skills, really focusing on the 'how will you fit' aspect, like everything at Traction. Then came the Demo! I had a few days to prep and present a high-level architecture solution for improving a SaaS application, which involved chatting with some team members. After that, there was a cultural meeting over breakfast with some Traction folks (not necessarily future teammates). It was conversational, a chance to ask anything and for them to gauge how I'd fit in as a person. Free breakfast included! You should hear back from the hiring manager fairly soon after. All in all, it was a pretty smooth process, no tricks, and good communication – no desperately waiting days for an email.

Confirmed questions4 questions
  • Can you discuss your previous experience with cloud technologies and your devops skills?
  • Given a scenario to improve a SaaS app, can you present your solution?
  • How would you fit into the team and company?
Sign In Solutions logo
Sign In Solutions

iOS Developer

Engineering

Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Onsite Take home Presentation
Interview formats
Behavioral Technical Presentation

I applied for a data engineering role, but they steered me towards a mobile role. I went through two phone screens. Then, I had an onsite with the CTO. It was very casual, and I led the discussion, which let me explore a lot of topics. After that, I got a take-home assignment. I found it a bit vague and undirected, possibly on purpose. I focused on the architecture of my take-home submission rather than the polish, which seemed to catch them off guard. When I presented the take-home to a UI/UX designer and two developers, they struggled technically and managerially with the interview itself. Their questions were generic and poorly asked. After this fourth interview, I felt I was operating at a significantly higher level than everyone else there. I was surprised when they rejected me two days later. I thought I performed well and even taught them things during the interviews. I don't think I was overly aggressive, as I discussed leadership, mentorship, and collaboration. I haven't received any feedback yet, so I'm unsure of the exact reasons for the rejection.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Sign In Solutions Interview Questions

Quoted word for word from Sign In Solutions interview reports.

What's the method to disable JavaScript in a browser through Selenium code?

Read reports

What is the difference between the values undefined and null?

Read reports

What is the difference between Smoke Testing and Sanity Testing?

Read reports

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

Read reports

What is the distinction between Assert and Verify in the context of automation testing?

Read report

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

Read report

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

Formats, difficulty and experience

Across all 45 Sign In Solutions interview reports.

Interview formats

Behavioral 36.4%
Technical 23.7%
Presentation 22.9%
Coding 6.8%
Group 6.8%

Interview difficulty

Easy 13.3%
Average 62.2%
Difficult 24.4%

Candidate experience

Positive 84.4%
Negative 11.1%
Neutral 4.4%

Reports by job function

Engineering 22
Sales 12
Marketing 6
Operations 3
Product 1
Design 1