Interviewing as a "Software Engineer, Engineering Productivity" role. Reading up about the role online seems to suggest that it got rebranded from SETI Engineer (Software Engineering Tools and Infrastructure) to Software Engineer, Engineering Productivity a short while ago - there seems to have been a difference in how general SWEs and SETIs were looked upon earlier with some stigma attached to the latter - I'm wary of this "Engineering Productivity" role having the same kind of baggage - don't want to get into the whole QA rut and be shut out from the software engineering world. My questions: 1. Is "Engineering productivity" a team, or a role? What is the work like? Pros/cons? 2. Is there anyone from Google who might be able to share more insights into the work the Engineering Productivity team does, and what the perceptions are - any pros/cons - anything I should be wary of? 3. Should I reach out now and tell the recruiter that I'm not interested in this role, or should I wait till after the interviews are done, and if I pass them, then take it up with the recruiter and ask to be matched with Software Engineer in a different role? Is that even possible?
2024 Presidential Election
Yesterday
2273
Biden ruined America and tech! Tax plans are insane
Tech Industry
Yesterday
1258
RIP Lacework
Tech Industry
Yesterday
632
Chances of meta clearing E5 with screwing up one coding one round and acing all other
India
Yesterday
1511
Please vote sensibly 🙏
Tech Industry
2d
53904
Goog Employees Arrested
Dude make it shorter next time. EngProd is old SETI at G and SDET at M. They merged ladder now so your ladder is same as SWE. That said, the hiring process might still be different which I don’t know much.