Lumenalta

Pros: The base salary for a Software Engineer at Lumenalta is decent, especially if you're early in your career. They do have a pretty solid 401k match, which is good for long-term savings. The hybrid work setup in our Austin, TX office also helps cut down on commute costs.
Cons: Health benefits aren't great; plans are expensive with high deductibles. You won't see big bonuses or any stock options here, which is tough for a mid-sized tech company. The overall compensation package just doesn't feel competitive compared to other tech industry players.
Advice to Management: Seriously re-evaluate your benefits packages. Employees notice when health insurance is subpar and there are no competitive stock options or performance bonuses, especially for key roles like Software Engineers. Catch up to what other tech companies offer.

Pros: My immediate team lead was awesome, really helped with software development tasks. There's a decent amount of autonomy if you're working remote from Austin, TX. It's a solid place for new software engineers to learn.
Cons: Upper management often changes direction without much warning, impacting project timelines. Communication isn't their strong suit for a mid-sized tech company. We often felt out of the loop on big decisions.
Advice to Management: Try to be more transparent with your teams about company strategy and product roadmap changes. Consistent communication helps everyone, especially for us working hybrid.

Pros: The hybrid work model is a lifesaver, especially for Software Engineer roles. We get two days remote from home, which really helps cut down on the San Francisco commute. My team's pretty chill and respects when I need to step away for personal appointments, which is a big plus for work flexibility.
Cons: But honestly, it's still a fast-paced tech startup. You'll often find yourself pushing past 5 PM, especially with tight deadlines in software development. The pressure to deliver quickly can definitely eat into your evenings and weekends, making consistent 40-hour weeks a challenge.
Advice to Management: Try to set more realistic project timelines, especially for critical software development cycles. It would really help prevent burnout among the engineering teams and improve overall morale.

Pros: I've found the hybrid model really helpful for my personal life. As a software engineer, I usually stick to 40-45 hours a week, which is solid for the Austin tech scene. You can actually take your PTO without much hassle.
Cons: Sometimes, client deadlines mean late nights, especially if you're on a critical project. There's also pressure from leadership around release cycles. The remote team members can sometimes make meeting times weird.
Advice to Management: Try to put more guardrails around after-hours meetings, especially for teams working across many time zones. Protect personal time better during crunch periods.