Trifacta logo

Trifacta Software Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
53.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Trifacta.

Showing 3 of 15
Trifacta logo
Trifacta

Software Engineer

Engineering · more than a year ago

Intern Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

First, I had a chat with a recruiter about the company and culture. Then, there was a 1-hour phone screen with an engineer. It started with about 20 minutes of background questions like 'tell me about the stack you used for X project on your interview', followed by a coding question, and then some Q&A about engineering life. It was pretty straightforward and fun. After that, I had a phone chat with the engineering manager. It was supposed to be another technical screen, but it turned into a cool conversation about Trifacta’s product, long-term market strategies, and the technology stack. Finally, although not really a screen, I had lunch onsite with some engineers! Overall, a really straightforward and fun interview process.

Confirmed questions1 question
  • Can you describe the stack you used for the X project during your interview?
Trifacta logo
Trifacta

Software Engineer

Engineering

Entry Easy Negative experience No offer 3 rounds
Interview process
Take home Technical screen Recruiter call
Interview formats
Technical Behavioral

So I read the reviews about this company's interview process and honestly, I should have listened. Their first step, which they call preliminary, felt more like they were trying to find flaws in me and was super unprofessional. The hiring manager didn't even bother to read my resume. They seemed too narrow-minded to consider people from different backgrounds. Then there was an automation assignment to submit. They completely disregarded the assignment I submitted. The manager, who just got promoted, seemed to just want to brag about the company and put me down, calling me fake with harsh words. Why ask someone to interview multiple times if you're not even going to evaluate technical skills? This whole thing felt like harassment.

Confirmed questions2 questions
  • Can you tell me about your resume?
  • Which automation framework did you use?
Trifacta logo
Trifacta

Technical Lead

Engineering

Lead Average Negative experience No offer 3 rounds
Interview process
Recruiter call Onsite Onsite
Interview formats
Behavioral Technical Coding

I had 3 rounds: a recruiter call, then 2 on-site interviews. The first on-site was a bit weird, mostly just 'where do you see yourself here?' type questions, which felt odd for the role. The second on-site lasted the entire day, from 10 am to 5 pm. It felt like I met everyone, even interns. The worst part is they never replied after the whole day dedicated to the interview. Pretty disrespectful.

Confirmed questions4 questions
  • How would you approach tiny URL hash generation?
  • Discuss scaling challenges in a μService environment.
  • Can you identify potential bugs in this code?

Trifacta Software Engineer Interview Questions

Quoted word for word from Trifacta interview reports.

Can you find the first duplicate character in a string or array?

Read reports

Could you implement Breadth-First Search (BFS) without any helpers?

Read reports

What is your understanding of Database Management Systems (DBMS)?

Read report

Can you explain the in-memory implementation of common data structures?

Read report

Formats, difficulty and experience

Across all 15 Trifacta interview reports.

Interview formats

Technical 41.7%
Coding 36.1%
Behavioral 19.4%
System Design 2.8%

Interview difficulty

Easy 20%
Average 60%
Difficult 20%

Candidate experience

Positive 53.3%
Negative 33.3%
Neutral 13.3%