Validity logo

Validity Software Engineer Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
55.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Validity.

Showing 3 of 9
Validity logo
Validity

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen Onsite Background check Offer
Interview formats
Technical Coding System Design Behavioral

I applied online and got a quick call from the recruiter who critiqued my resume and sent a take-home test within 5 minutes, even though the deadline they gave verbally was shorter than what was in the test. The take-home was okay, but they wanted it in a different language than the job actually uses. Then I talked to the hiring manager, who was a bit late but nice. After that, it was the on-site. The address listed online was wrong, so I had trouble finding the place, and they didn't even tell me. I had to send vaccine info beforehand, but when I arrived, they hadn't told the front desk I was coming, so I had to wait to be let in. The on-site interviews themselves were fine, just three one-on-ones. The first was more about me as a developer, not super technical. The second was a standard system design question. The third was another chat with the hiring manager. They said I'd hear back in a couple of days, but I never did, not even a rejection email. To top it off, a few weeks later, the same recruiter messaged me about a different job, acting like he didn't remember me at all. It really shows how they treat candidates.

Confirmed questions1 question
  • How would you design a news feed that displays the newest posts first, similar to Twitter or Instagram?
Validity logo
Validity

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Panel Offer
Interview formats
Behavioral Technical Coding

Started with a recruiter phone screen, then a call with the hiring manager. Had a take-home assignment where I had to find duplicates in a CSV file, which they estimated would take 2-4 hours. This was followed by a 2.5-hour video interview with the hiring manager and four team members, with no breaks. During this interview, two team members asked how I could improve my assignment, which felt like they wanted free suggestions. They also asked some basic undergrad-level questions, seemingly to show off rather than assess relevant skills. The technical part felt more like an interrogation than a discussion. I also spoke with two recent hires, which made it hard to gauge the company culture, product impact, or career growth potential. About 48 hours after the interview, I received a generic rejection email. Given my experience and recent negative Glassdoor reviews, I wouldn't recommend this company unless you're just looking for interview practice. The recruiter hinted the previous person in this role was fired, raising concerns about communication and transparency.

Confirmed questions3 questions
  • What improvements could you suggest for your take-home assignment?
  • How would you locate a specific value within a list of integers?
  • Explain the process of performing a binary search.
Validity logo
Validity

Software Engineer

Engineering · more than a year ago

Intern Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Onsite
Interview formats
Behavioral Technical Coding

I applied online and HR reached out the next day to set up a phone interview. After that, I got a take-home assignment that took me about 3-4 hours. Once I sent it back, a software engineer manager scheduled an on-site interview for me. The on-site was 2 hours long and I talked with several team members and the manager about my technical experience and my take-home exercise solution. They also gave me a coding question. I didn't get the offer because I'm going to grad school for my master's, and they wanted someone who could potentially become a full-time employee later. It was a good interview experience overall; the teams were nice and HR was quick to respond to emails.

Confirmed questions4 questions
  • Describe a past problem you encountered and how you resolved it.
  • Can you explain how you tackled the take-home problem?
  • Tell me about your technical background.

Validity Software Engineer Interview Questions

Quoted word for word from Validity interview reports.

How would you locate a specific value within a list of integers?

Read reports

How would you design a news feed that displays the newest posts first, similar to Twitter or Instagram?

Read reports

How would you identify duplicate entries within a CSV file?

Read reports

Can you describe the deployment strategy for the CSV duplicate detection tool?

Read reports

What are your ideas for enhancing the CSV duplicate-finding approach?

Read report

Were the in-person interview questions based on the take-home assignment?

Read report

Formats, difficulty and experience

Across all 9 Validity interview reports.

Interview formats

Technical 33.3%
Coding 25%
Behavioral 25%
System Design 8.3%
Other 4.2%

Interview difficulty

Easy 11.1%
Average 88.9%
Difficult 0%

Candidate experience

Negative 44.4%
Positive 55.6%