271–280 of 359 posts
Earlier quoted context omitted.
What sort of background thing are you talking about? Criminal? Civil?
Criminal, and that is the extent that I will follow up. I will also reiterate "minor".
Earlier quoted context omitted.
And blacklist myself entirely from this career? This throwaway comment is pushing it already in terms of burning bridges, not to mention getting fired from Google itself after my extended network congratulated me on the position. Who, in this incestuous valley, would hire the guy that sued Google for an employment issue? I've seen it happen, no way. Right to work, too, sigh. To be clear I moved from the Oakland area…
Fair enough. Best of luck.
Earlier quoted context omitted.
Because then your interviewer does a hatchet-job on you in a feedback form and you get shitlisted from interviewing at Google forever. That's the problem with large companies. There are companies where I would just walk out of an abusive interview, because the brokenness represents their whole company. Then you have massive, mega, ultra-sized companies like Google where even though this particular team is beating you…
Funny that there seems to be a consensus that Google can effectively black-list people, and yet it seems they can't even keep track of who they are supposed to actually interview or who they have previously contacted about interviewing.
A couple months later Rackspace cold called me to work there. It's a usual thing, I think, and I don't hold it against them.
Earlier quoted context omitted.
Funny that there seems to be a consensus that Google can effectively black-list people, and yet it seems they can't even keep track of who they are supposed to actually interview or who they have previously contacted about interviewing.
If you are blacklisted, then someone needs to check the blacklist just once for your process to get terminated. If you are scheduled, many people must refrain from screwing up. It even took them months to figure out that they hired an ex convict, after he personally disclosed the fact multiple times. I had great hopes for Google to innovate in sense of culture. I saw Larry Page and Sergey Brin as intellectuals. Turns…
Earlier quoted context omitted.
No, any settlement would almost certainly include a mutual non-disclosure agreement and mutual non-disparagement agreement. Complaining about it here makes it more difficult to get those, though, and any settlement in general. Moreover, that's not how it works in SV. Assuming you do good work, nobody will care if you sued Google and settled except perhaps Google. I know plenty of engineers who were fired from compani…
I appreciate your thoughts and haven't taken them lightly. That's the thing, is this stupid college mistake on my record undermines my integrity. Never mind that I've been employed at multiple companies and been trusted with user data far and beyond what Google would ever trust me with. I would have hoped that after a five year history in this industry, I would have demonstrated some integrity. Not even my character…
Earlier quoted context omitted.
It sounds like you've decided your rejection is fait accompli . I don't think that's the case, but I'm not here to convince you otherwise. Good luck!
No, I have irons in the fire. I won't deny that it got me down, and I know that's coming across. Thank you for the support, I really appreciate it.
Earlier quoted context omitted.
It sounds like you've decided your rejection is fait accompli . I don't think that's the case, but I'm not here to convince you otherwise. Good luck!
No, I have irons in the fire. I won't deny that it got me down, and I know that's coming across. Thank you for the support, I really appreciate it.
One strategy is to try to hide your past, figuring it won't hurt you with the latter two and might incrementally help you with the former. I wouldn't adopt this strategy.
Instead, assuming it truly is "minor," I'd own it. Write a blog post about how your past has made it harder for you to find work. Talk about what you did, specifically, and all your feelings about it then and now.
Don't name names of companies, but perhaps share some (anonymized) stories. Whatever you do, it can't sound like sour grapes. You have to be magnanimous to the last drop. You have to swallow every last bite of indignation you have. You need to say and believe things like, "If I'm honest with myself, I can understand why Company X made the decision they did even if I felt they handled it inappropriately and ultimately made the wrong decision for the wrong reason."
Try to tie it into a larger story, perhaps raising questions about whether the tech world is really a meritocracy, e.g., "Silicon Valley is a Meritocracy, Unless You Broke the Law as a Kid." Maybe try to reach out to other folks who have had similar experiences, e.g., "Are you an engineer whose past makes it hard for you to find work? You're not alone."
The response on this thread alone should be good enough evidence that folks would be interested in the story.
This will do a few things. First, it gets you exposure. Second, it immediately gets the attention of folks in the neutral and positive camps. The former will go, "WTF? We don't care about this. How stupid of people to reject a candidate for those reasons; let's interview him." The latter will go, "Holy shit! This is our kind of guy; let's interview him!"
You have nothing to lose, really, because this information is going to come out over the course of any interview no matter what. Turn it into your armor rather than resign yourself to having a sword in your belly.
Curious about the 'official' answer to the counter question. I'd have thought just having something triggered daily to clear out increments older than a day would be enough.
I don't know about an official answer but using a simple variation on a round-robin database (RRD) ought to do the trick. Basically: day count = [last 23 hour buckets] + hour count hour count = [last 59 minute buckets] + minute count minute count = [last 59 second buckets] + second count second count = You end up losing a small amount of accuracy, the worst being for keeping track of the second counts. You can avoid…
Curious about the 'official' answer to the counter question. I'd have thought just having something triggered daily to clear out increments older than a day would be enough.
I don't know about an official answer but using a simple variation on a round-robin database (RRD) ought to do the trick. Basically: day count = [last 23 hour buckets] + hour count hour count = [last 59 minute buckets] + minute count minute count = [last 59 second buckets] + second count second count = You end up losing a small amount of accuracy, the worst being for keeping track of the second counts. You can avoid…
Earlier quoted context omitted.
It seems like everything they do are CRUD apps, in the sense that they are concerned with creating, updating, reading, and destroying database records. They are just massively parallelized on the backend to deal with all the traffic. Sometimes I wonder what all these engineers do every day. Their main apps are not getting exponentially better, and they have fewer of them. Why is all this algorithmic knowledge really…
I think this is being relatively unfair in assessment. Google hasn't had a hit product in a while? Search and Ads are dominant. Android is the #1 mobile smartphone OS with 80% of the market. Chrome is now the #1 browser. Google Maps is the #1 mapping application. Gmail is now #1 in active users. G+ now has 190 million active posters now monthly now (Twitter only has 110 million active posters) YouTube is the top vide…
It seems disingenuous to have the achievements of those companies be co-opted by/as Google/'s