Can the sinking of the Titanic be averted? - Technical Talend Employee Review

1.0
27 Sept 2023
Recommend
CEO approval
Business outlook

Pros

The acquisition by Qlik (or anyone else) was long overdue and may stop the demise of Talend.

Cons

Talend offers an ageing, outdated technology platform that has not seen a lot of innovation in the last five years. The key components are clobbered together to form an 'integrated platform', that only exists in marketing brochures. Major cloud providers, Databricks, Snowflake, DBT and a few niche players drive the real innovations in the data industry. Talend is still trying to understand what the cloud is about. Studio, REs, TDC & TCDC are all on-prem components (or IaaS of course). The Qlik acquisition may slow down the decay of the Talend platform - IF they invest in rearchitecting the current mess. It won't be cheap, but without it Talend is dead as a herring.

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