Overall company good, team environment bad - Avis employé Software Engineer Trimble

2,0
28 mai 2023
Recommande
Approbation du PDG
Perspective commerciale

Avantages

Larger organisation ethos is great. Good benefits. Nice people. Problems I have are very specific to those directly above me.

Inconvénients

Nothing to ensure that the organisation ethos is applied to individual parts of the company. A lot of middle management, that seemingly do little. Little accountability on team level. From a management level, happy to give false promises.

Découvrez plus d’avis sur Trimble

5,0
27 mai 2026
Recommande
Approbation du PDG
Perspective commerciale

Avantages

great company with great people around.

Inconvénients

so far it has been very well

1,0
3 juin 2026
Recommande
Approbation du PDG
Perspective commerciale

Avantages

There are not any pros to working for Trimble at this time. Especially if you reside in the US. The current CPO thinks we cost too much and AI can do it.

Inconvénients

Severe Leadership Instability: Navigating four different managers in under a year makes it impossible to maintain consistent alignment on goals, strategy, or expectations. You are constantly adapting to shifting management priorities rather than executing a stable product vision. "Sink or Swim" Culture: Onboarding is virtually non-existent, particularly for highly complex legacy platforms. There is a severe lack of role advocacy and functional coaching. When explicit requests for training are made, they are met with a generalized mandate to "get it done" without providing the necessary executive backing or cross-functional support. The "Generalist" Efficiency Trap: There is intense corporate pressure for product leaders to operate as generic generalists across highly technical, domain-specific platforms. This dilutes subject matter expertise and slows execution. Shifting Goalposts: Performance baselines are inconsistent. You can receive formal documentation from one manager stating you have made "considerable progress on all goals," only to have the organization introduce vast, entirely uncommunicated role metrics for the first time via sudden administrative performance processes. Systemic failures caused by legacy processes are frequently misattributed to individual execution.

Voir les avis par: Utile|Évaluation|Date|Tout