Inkling logo

Inkling Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Inkling.

Showing 3 of 7
Inkling logo
Inkling

Software Engineer

Engineering · more than a year ago

Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Onsite Technical screen
Interview formats
Coding Technical

The interview process was disorganized. The recruiter didn't mention the pair programming format until the onsite interview, which felt like a surprise. Management seems to prefer hiring interns for full-time roles, perhaps to maintain tight control, which might lead to inexperienced engineers and bad habits. There seems to be a lack of understanding of CS fundamentals among the engineers and leaders, despite aiming to build large-scale systems. I question the scalability of their backend architecture due to immature and inexperienced leadership. Scheduling was also an issue, with interviewers sometimes being late.

Confirmed questions3 questions
  • I need you to dictate code to me, character by character, while I watch your screen.
  • Could you explain your understanding of basic Complexity theory?
  • What are your thoughts on the scalability of our backend architecture?
Inkling logo
Inkling

Software Engineer

Engineering

Mid Average Positive experience No offer 7 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Other Technical Coding Behavioral System Design

The interview process with Inkling is pretty standard. I had an initial phone call with a technical recruiter which led to an hour technical code screening with the hiring manager and eventually on-site to meet with the team. The Inkling office is in a convenient location within the financial district (just several blocks away from the Montgomery Bart/Muni station). My on-site interview was scheduled for about 6 hours beginning from 9am - 3pm. I had 6 one-on-one interviews and had the opportunity to eat lunch with a couple people at the office. My first interview was a product demo, followed by 2 technical interviews where I peer-programmed on a computer, 2 behavioral/fitment interviews, and a systems design interview. Throughout this whole process, everyone that I spoke/interviewed with were extremely kind and easy-going. I appreciated that a lot because it takes away the pressure and nervousness that I would otherwise feel. I did not feel rushed by the interviewers to spit out answers and everything felt very collaborative (especially with the coding interviews). The only portion of the interview that felt off for me was during the Systems Design portion, because I felt like I couldn't understand the interviewers question too clearly. Aside from the interviews itself, I really enjoyed learning about the product over at Inkling. It seems like they are working with really exciting technologies and actually making things happen quickly to improve Inkling's future. Although this was by far the longest interview I've had, it was also one of the best interviews I've experienced so far.

Confirmed questions1 question
  • Could you provide a high-level overview design of Squarespace?
Inkling logo
Inkling

Software Engineer Intern

Engineering

Intern Difficult Positive experience Accept offer 4 rounds
Interview process
Take home Phone screen Technical screen Background check
Interview formats
Coding Technical Behavioral

I saw the job on LinkedIn and applied. They sent me a coding challenge first. After I finished that, we emailed back and forth to set up a technical phone interview. That interview had questions about JavaScript, libraries I know, algorithms, and some personal stuff. The next week, we emailed again to schedule another interview. This one was more about my personality, my past work experience, and salary expectations. Then, they arranged a call with one of my references.

Confirmed questions1 question
  • How do you perceive others perceive you?

Inkling Software Engineer Interview Questions

Quoted word for word from Inkling interview reports.

Could you provide a high-level overview design of Squarespace?

Read reports

Could you explain your understanding of basic Complexity theory?

Read reports

What are your thoughts on the scalability of our backend architecture?

Read report

What specifically about Inkling attracted you to apply here?

Read report

Can you tell me why you're looking to leave your current job?

Read report

Can you tell me about a recent school project you worked on?

Read report

Formats, difficulty and experience

Across all 7 Inkling interview reports.

Interview formats

Behavioral 29.4%
Technical 29.4%
Coding 29.4%
Other 5.9%
System Design 5.9%

Interview difficulty

Easy 28.6%
Average 42.9%
Difficult 28.6%

Candidate experience

Positive 57.1%
Negative 42.9%