[tombert]

I think my biggest ongoing frustration was how much time I was expected to read and reply to emails; on my first day one of the first things I was instructed to do was to use their internal email filtering system (the name of which I can't remember), because if you didn't you'd have literally thousands of emails going into your main inbox. Mostly alerts, lots of cross-team announcements that weren't relevant to me, some Radar updates on tickets that I wasn't assigned to IIRC.

Even when I got the filters more or less under control, I would still have to spend a lot of time replying to emails throughout the day, or risk getting in trouble for letting them pile up.

It was pretty depressing, and I remember the first time I pushed back I ended up kind of yelling at my boss's boss about it when I said something like "You know, during the interview you asked me a lot of really hard computer science questions, I thought that's why you hired me, but maybe we should revise the process to just be a fucking endurance test of replying to emails for two hours and see how they do." He didn't like this suggestion, for whatever reason.

So I don't completely blame them for saying I had a bad attitude, and frankly I don't think I was a good fit for the AMP team of Apple; I am far too unorganized.

[BuckRogers]

I'm a so-so to possibly bad programmer, but I am very well organized, responsible (respond to everything immediately), and very good at enduring pain and BS like you describe. Lifetime of it, it's how I survive. I'd never get hired at Google due to the interview process I'm sure, but it sounds like I'd be their ideal employee. Shame that marriage made in heaven will never be consummated!