Textio logo

Textio Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Textio.

Showing 3 of 5
Textio logo
Textio

Software Engineer

Engineering · more than a year ago

Staff Average Positive experience No offer 5 rounds
Interview process
Take home Technical screen Technical screen Panel Panel
Interview formats
Technical Technical Technical Behavioral Behavioral

So I had this interview for Staff Software Engineer. First, there was a take-home assignment that took about 2 hours, mainly using React, to build something like their product with mock data. Then, I had a technical interview where we reviewed the take-home and talked about ways to make it better or add more features. After that, another technical interview focused on application architecture with a senior engineer. Then, there were two non-technical interviews: one with engineering management about leadership and another with engineering leadership about my growth.

Confirmed questions8 questions
  • Build something very similar to their product based on mock data.
  • Tell me about a time you were in scenario X and how you handled it.
  • Tell me about a time you were in scenario Y and how you handled it.
Textio logo
Textio

Software Engineer

Engineering · more than a year ago

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

I had an initial recruiter call, which was fine, but didn't feel very inclusive despite the company's emphasis on diversity. The process involves a 2-3 hour take-home project, followed by a call about it. If successful, there's a longer, full-day take-home project and then a full-day onsite. This seems like a lot of interviews and upfront work for an individual contributor role. I also had a strange conversation about salary expectations with the recruiter, where they wouldn't even discuss ranges, which felt unusual given their stated values.

Confirmed questions5 questions
  • Can you walk me through your past positions and what draws you to Textio?
  • What are your thoughts on salary expectations?
  • Can you take me through your previous roles?
Textio logo
Textio

Software Engineer

Engineering

Mid Average Neutral experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Coding Technical

I really wanted to enjoy this process because the recruiter and interviewer were nice. It was different from the usual tech interviews, which I usually like. However, the communication and execution of the coding exercise were not good. It definitely didn't show my ability to do the job. I do like that they're not using whiteboards anymore, but I think they need to improve more so they don't miss out on great developers and good people.

Confirmed questions1 question
  • Complete a front-end and backend coding exercise that requires a significant time commitment.

Textio Software Engineer Interview Questions

Quoted word for word from Textio interview reports.

Build something very similar to their product based on mock data.

Read reports

Can you explain the code you wrote for the coding challenge?

Read reports

Can you explain your code, detailing each line and the reasoning behind your choices, to a group?

Read reports

Tell me about a time you were in scenario X and how you handled it.

Read report

Can you walk me through your past positions and what draws you to Textio?

Read report

Formats, difficulty and experience

Across all 5 Textio interview reports.

Interview formats

Technical 43.8%
Coding 25%
Behavioral 18.8%
Presentation 6.2%
Other 6.2%

Interview difficulty

Easy 0%
Average 80%
Difficult 20%

Candidate experience

Positive 40%
Neutral 20%
Negative 40%