iTrellis logo

iTrellis Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
66.7% Positive experience

Which role are you interviewing for?

2 roles · 12 reports

Candidate interview experiences

First-hand accounts from people who interviewed at iTrellis.

Showing 4 of 12
iTrellis logo
iTrellis

Business Analyst

Analytics · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral

After I applied, they were super fast to get back to me. Communication was good, which I appreciated since I'm not from Seattle. The process involved a phone screening, a Business Analyst test where I had to write project requirements, and then a video interview. They gave me the BA test on Thursday afternoon and expected it back Friday, which felt rushed given I have a full-time job. After that, they contacted me the next Monday for a surprise video interview with the CEO during my workday. I also learned they only offer 3-month contracts and reduce pay when you're not assigned to a project. While the interview itself was straightforward, I didn't appreciate them overlooking my current work commitments.

Confirmed questions1 question
  • What are the components of Acceptance Criteria for a clear and effective User Story?
iTrellis logo
iTrellis

Software Development Engineer

Engineering

Entry Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen Offer
Interview formats
Behavioral Coding Technical

So I found this place, iTrellis, and after hearing good stuff and talking to people there, I sent my resume. The recruiter called me for a phone interview, asking typical questions but making it really personal and fun. She then asked if I wanted to move to Phase II: a Code Project. I got an email with three project options and a deadline. I did the project and sent it in. The recruiter said they'd review it and get back to me. After a week of waiting and feeling anxious, I emailed her. She said it was still under review. A few days later, she emailed again, but to say the position was no longer available due to unforeseen reasons. I was bummed, but she said they really wanted me and she'd keep me updated. She sent weekly updates for a few weeks, and then finally, an email asking if I was still interested in Phase III: Code Review. I said yes and prepped by reviewing my project. The interview was at their Seattle office, with three 1-on-1s, each about 45-60 mins. It was a bit intimidating, but each interviewer had a different take on my project, and it was cool to discuss and defend my work. They clearly took it seriously and had reviewed it. Less than a week later, I got an offer. I'm really happy I stuck with it, iTrellis has been great.

Confirmed questions5 questions
  • Why iTrellis?
  • What makes you want to leave your current job?
  • What are your strengths?
iTrellis logo
iTrellis

Software Engineer

Engineering

Senior Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Technical Presentation

They have a three-tiered interview process. Phase 1 starts with a personality phone interview from their recruiter (who is very personable, knowledgeable, and makes you feel at ease) Phase 2 then goes into a pretty challenging code project that you complete on your own time from a list of 3 available sets of requirements Phase 3 is the challenging phase where you come into the office for a 3 phase interview, where you defend your code project, then add a new feature on the fly, and then modify your code project to work a little differently than you designed it.

Confirmed questions3 questions
  • Can you defend your code?
  • Can you add a feature on the fly?
  • Can you change the way your code is implemented?
iTrellis logo
iTrellis

Software Engineer

Engineering

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Onsite
Interview formats
Technical Presentation

I had a quick chat with a recruiter. After that, I was given a choice of a small take-home project, it should take less than 10 hours to complete. I sent it back when I was done. A few days later, I went to the office for the last part of the interview where I had to talk about my work and show off some skills. It was pretty chill, no crazy whiteboarding with a bunch of people. You can tell they care about the interview process and want candidates to know what's up. They even paid for my parking!

Confirmed questions1 question
  • Could you build a basic web app for calculating a somewhat complex scenario and submit it within about a week?

iTrellis Interview Questions

Quoted word for word from iTrellis interview reports.

Could you traverse a tree and identify the largest number within it?

Read reports

What are the components of Acceptance Criteria for a clear and effective User Story?

Read reports

Could you build a trip calculator application as a programming assignment?

Read report

Regarding problem X from the technical problems, what changes would you make to prepare it for check-in?

Read report

Could you build a basic web app for calculating a somewhat complex scenario and submit it within about a week?

Read report

Formats, difficulty and experience

Across all 12 iTrellis interview reports.

Interview formats

Technical 40%
Coding 26.7%
Behavioral 26.7%
Presentation 6.7%

Interview difficulty

Easy 8.3%
Average 66.7%
Difficult 25%

Candidate experience

Positive 66.7%
Neutral 16.7%
Negative 16.7%

Reports by job function

Engineering 10
Analytics 2