Worst Sales Org I've Ever Been a Part Of - Account Executive Talend Employee Review

1.0
15 Jun 2022
Recommend
CEO approval
Business outlook

Pros

Legacy tool with fair number of inbound leads, a few caring leaders. Other than that honestly nothing.

Cons

Get with the times or be completely left behind. This is a worst in class sales org. Reps aren't hitting anywhere close to quotas, sales ops processes are basically non existent, turnover is high, product is legacy, and there is a general bad attitude and lack of collaboration between departments. The worst experience I have had in my professional career in sales.

avatar
Talend Response
3y
Thank you for your review; we appreciate feedback. There are many sites for candidates to research companies and read organic reviews, and we are proud of our company culture. Talend has never asked any of our sales teams to publicly enter their earnings data to show our teams are successful and many overachieving. Markets can sometimes be hard, but we love challenges here at Talend. We are changing the way the world makes decisions, and we are excited about our journey to becoming a best-in-class SaaS company.

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