Talend Interview Experience | Set 1
Interview Experience
Talend visited our campus for associative Technical support Engg offering 5.6 lac CTC. JP Nagar 3rd stage, Bangalore, karnataka.Entrance test was: 15 aptitude 15 ...
Full Details
Talend visited our campus for associative Technical support Engg offering 5.6 lac CTC. JP Nagar 3rd stage, Bangalore, karnataka. Entrance test was: 15 aptitude 15 Java questions 15 OS and Database questions. Questions are easy except OS part. In OS they asked about some Unix commands. By the way its written test. All questions are Objectives.
Round 1 Technical round 1 There were nearly 130 members took test and 30 shortlisted. 2 panels were there in room. 1st question was tell about your self. After that based on Resume they started questioning. Some basic Java questions like threads , threads life cycle , inheritance and so on. All basics and that's was very quick and easy.
Round 2 Combined tech 2 and HR round Manager only took this round. 11/30 made through the 1st round. Please note this. He had my booklet with all rough sheets I have used in test and 1st round. There was cube color problem given in aptitude test. He asked me to write code for it. I did it but my Communication skill isnt up to the mark. So I got
rejected. He gently explained why he's rejecting me very well and I'm OK with what he said.
Round 3 Communication skill test I did'nt attended this round but my friend did. This is Skype voice chatting test. They called one of US client and tell him to solve his problem. This is just to check how you communicate with clients. All staffs are good and very responsive. That's it folks.
About This Question
This is a candidate experience report from a talend interview for a swe role during the recruiter round reported in 2017.
It covers the following topics: Sql .
Difficulty rating: Easy
Topics
About Talend Interview Reports
This question was reported by a candidate who interviewed at Talend. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Talend are the higher-signal extractions to take from this report.
For broader preparation context, the Talend interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Talend reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Talend Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Talend reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.