It can be hard for people to tell if you are working, because the codebase is so bad that it can take ages to do the most basic things. On the other hand, a lot of people work overtime to try and make up for how slow things go.
Filled with corporate politics, promotions are stalled by default. All the tools you use are in-house and ancient, so the experience you gain is mostly worthless. HR is nonexistent and will never do anything, even in serious situations.
First off, I'll say there was a huge language barrier between my interviewer and me. He did not speak fluent English by a long shot. The choppy Google Voice connection, mixed with him being fairly quiet, didn't help either. He asked me questions lik
I was emailed by a Google recruiter to assess my compatibility for a position in Software Engineering. The recruiter sent a list of questions via email. Most of these questions were boilerplate, and some could have been readily answered with a curso
So far, the process has been an informal chat with a technical sourcer/recruiter at Google, followed by a technical phone screen with an engineer. The recruiter will give you a bunch of resources and links. You should look through them and truly kno
First off, I'll say there was a huge language barrier between my interviewer and me. He did not speak fluent English by a long shot. The choppy Google Voice connection, mixed with him being fairly quiet, didn't help either. He asked me questions lik
I was emailed by a Google recruiter to assess my compatibility for a position in Software Engineering. The recruiter sent a list of questions via email. Most of these questions were boilerplate, and some could have been readily answered with a curso
So far, the process has been an informal chat with a technical sourcer/recruiter at Google, followed by a technical phone screen with an engineer. The recruiter will give you a bunch of resources and links. You should look through them and truly kno