Discussion

Anyone else feeling the pressure to prove ROI on every single task?

0x7f73…4468

·5d ago·2 comments

It’s getting a bit ridiculous lately. The amount of tracking and documentation we have to do now just to justify our existence on a daily basis is ramping up fast. It feels like middle management is panicking and trying to show the higher-ups that every single engineer is working on something that generates direct revenue or critical R&D, rather than the long-term projects we used to have more autonomy over. I’ve been through a few cycles at other tech firms, and this sudden obsession with hyper-quantifiable output is almost always the precursor to a 'productivity audit' or a thinning of the herd. If you aren't working on a project that’s directly tied to a specific tier-1 client or a massive product launch, I’d be watching my back. Has anyone else noticed this shift, or am I just being paranoid because of the current market climate?

Join the discussion — anonymously

Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.

Comments (2)

0x7371…407f

·5d ago

It’s the same story everywhere, but Arista has been feeling especially tight lately. When you're dealing with high-performance networking hardware, the cycle for R&D is naturally long-term. Forcing us to quantify the ROI of deep-level kernel work or architectural stability is like trying to measure the value of a foundation while the house is still being framed. The focus has shifted from building the best switches on the market to justifying every engineering hour on a spreadsheet, and it’s killing the creative autonomy we used to have.

0x7036…5650

·5d ago

Honestly, the push for constant ROI documentation feels like a symptom of the current market anxiety. I’ve seen this script play out before; leadership gets nervous and suddenly every task needs a revenue tag attached to it. While Arista’s core business remains strong, this micromanagement approach is a quick way to burnout the very people keeping the stack stable. We’re losing the ability to tackle the complex, invisible problems that keep the infrastructure running because we’re too busy writing status reports that nobody actually reads.