Teradata

Pros: I really liked the hybrid work model here. As a Data Analyst, I could split my time between the San Diego office and working from home, which helped my work-life balance. That flexibility was key for my daily routine.
Cons: The "flexible" part of hybrid isn't always that flexible. Sometimes I'd have to come in for meetings that could easily be remote. Plus, getting approval for full remote options for data roles seems super tough, even in the big data industry.
Advice to Management: Really evaluate which meetings truly need to be in-person. Consider offering more fully remote options for certain roles, especially when there's no real need to be onsite.

Pros: The remote work flexibility is a huge plus, really helps with personal life. As a Data Engineer, I generally stick to standard 40-hour weeks most of the time. It's a solid setup for those in the data warehousing industry.
Cons: There are definitely crunch times with big project deadlines, and you'll put in extra hours. Sometimes communication for these spikes could be clearer from leadership, making it tough to plan personal time.
Advice to Management: Try to give more heads-up on demanding project timelines. It would help everyone manage their schedules better.

Pros: The hybrid work model is pretty solid here. As a data engineer, I can usually WFH a couple days a week. It's a big help with personal appointments and avoiding that San Diego traffic.
Cons: Sometimes the office requirements feel a bit arbitrary. For bigger cloud analytics projects, they're really pushing for onsite collaboration. It can definitely mess with your routine when you've planned for WFH.
Advice to Management: Be more consistent with hybrid policies across different teams. Clarify when onsite work is truly necessary for specific project phases and for different engineering roles.

Pros: My direct manager, as a Data Engineer in the San Diego office, was great. They really supported skill development and team collaboration. There are good opportunities to work on cutting-edge cloud data platform technologies.
Cons: The higher-level leadership can feel pretty disconnected from daily work. Strategic decisions often seem slow in this big corporate environment. Sometimes it feels like there's a lack of clear vision from the top.
Advice to Management: Focus on better communication and more consistent strategic direction. Empower mid-level managers more. Try to connect more with the individual contributor roles.

Pros: My direct manager was usually pretty solid. They really tried to support our team, especially when tackling complex cloud data analytics projects. It felt good to have that immediate leadership support and guidance.
Cons: Upper leadership can sometimes feel completely disconnected from what's happening on the ground. Strategic decisions often come down without much explanation, which is tough. This top-down approach can make it hard to innovate in a big tech corporate structure.
Advice to Management: Try to loop in individual contributors more before big strategic shifts. More transparency from upper management would definitely boost morale in this data warehousing space.

Pros: The hybrid model is okay; I could work from home sometimes. For my Software Engineer role, I appreciated some WFH days. It's better than being completely onsite in the San Diego office.
Cons: They really push for more office time, even for engineers. True remote work options are tough to get unless you're senior. It feels like they're trying to roll back the work flexibility we had during COVID.
Advice to Management: Listen to employees on WFH preferences. More work flexibility keeps good data analytics talent, especially for critical cloud infrastructure roles.

Pros: You'll find some really smart people here, especially on the engineering teams. As a Software Engineer, the health benefits were solid, and the San Diego office environment was pretty decent physically.
Cons: The company culture sometimes feels stuck in the past. It's tough to get new initiatives moving quickly in this big corporate structure. There's a lot of red tape, which isn't great for innovation in data warehousing.

Pros: My salary as a Senior Data Engineer was pretty solid. For remote roles like mine, the base pay is competitive and there's usually a good annual bonus tied to performance in the cloud analytics space. I felt fairly compensated for my day-to-day.
Cons: The health benefits weren't amazing; the premiums felt a bit high compared to other established software vendors. Also, the 401k match wasn't as generous as I've seen elsewhere. It's not bad, just not top-tier.
Advice to Management: Look into improving the health insurance options and increasing the 401k match to be more competitive with other big tech companies. Investing in these areas would definitely help with talent retention, especially for critical data engineering roles.

Pros: My immediate managers were usually solid. They tried their best to support us, especially with the hybrid model. There's a decent benefits package too, and the work itself in data warehousing is challenging.
Cons: Upper leadership can be a real issue. It feels like they don't always understand the engineering challenges we face. Decision-making is slow, and there's a lack of clear strategic vision for the future of cloud analytics. That makes it tough.
Advice to Management: Seriously, connect more with the teams doing the actual work. Get a clear, actionable strategy for the future of Teradata's products. Transparency helps a lot.

Pros: I've been remote from the start, which is a big plus for a big corporate company like Teradata. As a Data Engineer, I've got a pretty solid WFH setup and generally don't have to be online 24/7. It's nice to have that flexibility for personal appointments.
Cons: The work flexibility really depends on your specific manager, which is a bummer. Some teams offer great autonomy, but others still push for strict 9-5 hours even in a remote environment. There isn't a consistent hybrid model for everyone, which can be frustrating.
Advice to Management: Try to standardize work flexibility policies across all teams, especially for technical roles. This would help avoid situations where some employees feel micromanaged compared to others and improve consistency for remote workers.