Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4 stories

Likes earn the author +10 XP for the first 3 likes each day

TredenceData Scientist
Reported Jul 2026

Tredence Data Scientist interview: NLP and GenAI gap

About a week after a recruiter call, I had one technical round. It began with my current project and resume, so the discussion initially felt grounded in my background. Then it shifted to NLP and GenAI, including transformers. I had not worked hands-on in that exact area. When I could not speak confidently about what they wanted, the energy dropped quickly and the interview effectively ended soon…

Other0
TredenceData Engineer
Reported Jul 2026

Data Engineer interview at Tredence

For this Data Engineer role, the process ran about 4 to 5 rounds. It started with a HackerEarth assessment mixing aptitude, SQL, and coding, then a communication round. Two technical rounds followed, with strong emphasis on SQL and PySpark plus basic DSA. The questions required precision and speed, and the interviewers pushed on how I approached data-engineering work, not only the tools I had use…

Offer0
TredenceData Engineer
Reported Jul 2026

Tredence Data Engineer interview: PySpark, Spark architecture and SQL

After an initial recruiter-style conversation, I had a focused technical screen that lasted about 30 minutes. We discussed PySpark, SQL and how I worked with Azure Databricks. The panel's tone felt positive. The questions covered data engineering fundamentals. I explained Spark architecture in detail, talked through ways to parse JSON and, toward the end, wrote a SQL query to find three consecuti…

In progressTechnical Screen0
TredenceSoftware Engineer
Reported Jul 2026

Tredence Software Engineer interview: React, Node.js, SQL, and scenarios

After a recruiter touchpoint, I had a technical screen about a week later. The process included three technical discussions and another technical round at their office. The difficulty was easy to medium, and the recurring topics were React, Node.js, and SQL. They combined basic DSA questions with scenarios about common web-app problems. The final in-person round stayed with the same themes instea…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP