How's the Engineering Productivity group at Google?
I was initially approached by a recruiter about a SETI role a few months back but now after another contact I was told there's no such role anymore and only SWEs exist in a dedicated Engineering Productivity org building tools across several Google services. Any idea if this org means the role/group is in terms of impact and interesting work? I am still skeptical and conveyed that to the recruiter - he did mention I could still match with any other team if I get to the offer stage. I was just curious to hear from folks here.
In plain English, EngProd means writing test frameworks for other people’s code. Are you excited about that?
Is TC less?
That sounds miserable no matter the company
Instead of working on the core product features that customers see, you work on making sure those features are built well. That could mean writing test harnesses, acting as customer advocates for simplifying excessively complicated code, or running stress tests to get data to prove that some system needs more attention before release.
I see. I assume the work would be related to working on tools like Blaze, Borg etc. which have been opensourced very successfully.
Not necessarily. They could be building completely in-house tools or they could be working with the core dev team to add certain features to the product to enable better test ability debugability telemetry etc
I'm in the same boat, mind if I DM you?
Avoid. Avoid. Avoid.