NoRedInk logo

NoRedInk Software Engineer Interview Questions
& Process

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

Based on 19 interview experiences · FREE TO READ

3.9 Rounds average
Average Typical difficulty
57.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at NoRedInk.

Showing 3 of 19
NoRedInk logo
NoRedInk

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Coding Behavioral

It was a pretty long process, like a month and a half. I knew this going in because I saw it in reviews and they told me upfront. I ended up meeting a bunch of different people from various teams, both technical and non-technical. There was one take-home assignment, and then three live coding interviews that covered a pretty wide range of topics, from standard problems to some more unique ones, which was actually pretty cool.

Confirmed questions4 questions
  • Tell me about your interest in NoRedInk.
  • What do you consider your strengths and weaknesses?
  • What feedback would your previous managers give you?
NoRedInk logo
NoRedInk

Software Engineer

Engineering · more than a year ago

Mid Easy Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Onsite Onsite Onsite Onsite Offer
Interview formats
Behavioral Coding System Design Technical

So, the process is: first, a get-to-know-you interview, about an hour. Then, about 3 technical interviews, each lasting roughly 1.5 hours. After that, a resume deep dive, which took about 2 hours. Then, a meet-the-team session, which is non-evaluative and about 30 minutes, but it can go longer if you like. Also, an interview coordinator check-in, also non-evaluative, about 30 minutes. Finally, an interview with the CTO, lasting about an hour. The 3 technical interviews covered different areas: code fluency (how well you can code and if it's clean/understandable), system design and modeling, and API design.

Confirmed questions1 question
  • Tell me about a situation where you faced failure.
NoRedInk logo
NoRedInk

Software Developer

Engineering · more than a year ago

Entry Average Neutral experience No offer 3 rounds
Interview process
Take home Recruiter call Phone screen
Interview formats
Technical Behavioral

I applied online and got an automated email with a take-home challenge due in 5 days, with a 2-hour time limit. It was a moderately difficult task, best tackled with a pre-made project boilerplate. The submission process was all handled through a web app. About 3 days after submitting, I got an email congratulating me and asking to schedule a video call with a senior tech person. The email sender was weird though, like a copy-paste. The video call was friendly, but I expected technical questions or a review of my take-home work given the interviewer's role. Instead, it was just short, introspective questions about personal strengths, weaknesses, and other HR-like topics. The call lasted around 20 minutes. A few hours later, I got another automated email saying they weren't moving forward, with no feedback.

Confirmed questions4 questions
  • Can you tell me why you're interested in NoRedInk?
  • What do you consider your greatest strengths?
  • What are your biggest weaknesses?

NoRedInk Software Engineer Interview Questions

Quoted word for word from NoRedInk interview reports.

Could you please rebuild our main web page from scratch, without needing to make it pixel perfect?

Read reports

What's your motivation for wanting to pick up Haskell and Elm?

Read report

I'm only posting this review because the last person I talked to was so unprofessional. He referred to two programming languages as "enemies," like we were five years old. For all the questions: him: Why do you like this and not that? me: Because... him: That's not an answer to my question, let me ask again. After the technical part: him: Others have done this way faster. me: OK. him: Your code is a mess.

Read report

Tell me about another weakness you have. And another. And another.

Read report

Formats, difficulty and experience

Across all 19 NoRedInk interview reports.

Interview formats

Behavioral 36%
Coding 30%
Technical 30%
System Design 4%

Interview difficulty

Easy 10.5%
Average 73.7%
Difficult 15.8%

Candidate experience

Neutral 15.8%
Negative 26.3%
Positive 57.9%