Product Support Engineer - Support Engineer Talend Employee Review

3.0
3 May 2018
Recommend
CEO approval
Business outlook

Pros

First and foremost it is an open source due to which it has been used across and preferred by the ETL developers. Lots of connectors for the efficient and better integration with most of the 3rd party products. It will be a great opportunity for the freshers to start with here as support engineer. Package that a fresher could ever imagine for the Associate tech support role and Talend comparatively pays higher than other equivalent and it competitor companies. Its also a best place for Consultant and CSA role. They are given much importance. Lots of products and lots of technologies to explore and that too Bigdata plays the major part. Lots of new implementations.

Cons

R&D team in not much efficient and not quick enough in addressing the issues. No proper basic facilities in India office. No R&D team in India which would be a drawback for the candidates who had closely worked with the developers Setup a Admin team in India which is a basic need.

Explore other reviews about Talend

5.0
28 May 2025
Recommend
CEO approval
Business outlook

Pros

Great culture, colleagues, and products

Cons

Acquisition by Qlik caused major disruptions and drove all existing employees away.

1
4.0
29 Sept 2025
Recommend
CEO approval
Business outlook

Pros

* Talend has a great foundation for technical growth with a strong product centered on Talend Studio which generates Java code for data integration using visual drag-and-drop components * Strong Eclipse technology and community are built into Talend Studio * Talend Studio addresses both batch integration (Jobs) and application integration (Routes) * Very rich palette of Components for batch integration Jobs * Generated code for event driven Routes uses Apache Camel which is excellent

Cons

* Poor generated code quality * Generated code for batch Jobs lacks a mature underlying framework (e.g. there is no underlying Spring Batch or equivalent that the generated code uses) * Design palette for Routes is very limited and does not contain most Camel components * Components for Camel Routes are poorly documented * Generated code for both Jobs and Routes is monolithic and not easily extended * Limited re-use and modularity of user designs. There is some, but it is not as robust or manageable as it should be. * Does not make use of modern software frameworks such as Spring. * Very poor tools for authoring SQL

See reviews by: Helpful|Rating|Date|All