OfTheCross
Veteran
Banking operations..what field are you looking in?
But honestly I wouldn't mind working for an Electric company or HVAC or some other mechanical shyt...
They just gotta be willing to train me
Banking operations..what field are you looking in?
It might be dead on if you see reviews that are similar. I know my old job has lots of negative reviews & are legit. I was told by old coworkers that the job has been posting positive reviews on thereHow much weight do yall put into online reviews, namely from Glassdoor, of certain companies? Its some places I wanna work at that I been reading some sheisty ass shyt about but I said fukk it and sent in an application anyway and look to follow up. Should I be takin these online reviews more seriously so Im not burnin up my time or are the majority of those bad reviews left by scornful nikkas?
How much weight do yall put into online reviews, namely from Glassdoor, of certain companies? Its some places I wanna work at that I been reading some sheisty ass shyt about but I said fukk it and sent in an application anyway and look to follow up. Should I be takin these online reviews more seriously so Im not burnin up my time or are the majority of those bad reviews left by scornful nikkas?
So I mentioned in The College Thread, I believe, that a professor of mine hooked me up with a HR person at Google. I shot the HR rep a couple of emails and he ended up referring me to another person; initially I was hesitant on that since I felt like I was being pawned off on someone else for an eventual rejection. But I got in contact with this new HR person and we set up a time to talk. That was supposed to happen on Tuesday, but thanks to some miscommunication () we had to reschedule for today. I expected him to be a little upset but he was really cordial and enthusiastic
. I was hoping to get fast tracked in
but he pretty much pointed me towards a different position within Google. Basically you're an employee for a year, they groom you to work at Google, and if you're good enough then they'll probably hire you on full time. Here's a shortlist of what he asked me:
- Most proficient language (If it's C# like it was for me
, get into C++ and Java)
- A recent project you worked on that was a success
- Familiarity with Google products
- Your areas of expertise (I flubbed this a bit
)
- If you have a GitHub (If you don't
)
- Open to relocation (Basically to the Bay Area [I would have preferred Orange County
])
- When you think you'll be ready to start the process
- Are you talking to any other recruiters
The position I'd be going for is 2 45 minute phone interviews, then a series of on-site interviews if you make it that far. Like I mentioned before, or in another thread, basically be prepared for anything. Data structures, algorithms, logic and reasoning, Big O notation, writing clean and efficient syntax, thinking out loud, asking clarifying questions, things of that nature. I have about 5 months to prepare so I have no excuses if I don't nail this shyt. Time to dive in.
Good luck my boy recently got a software engineer job at google. Relocated to cali and allSo I mentioned in The College Thread, I believe, that a professor of mine hooked me up with a HR person at Google. I shot the HR rep a couple of emails and he ended up referring me to another person; initially I was hesitant on that since I felt like I was being pawned off on someone else for an eventual rejection. But I got in contact with this new HR person and we set up a time to talk. That was supposed to happen on Tuesday, but thanks to some miscommunication () we had to reschedule for today. I expected him to be a little upset but he was really cordial and enthusiastic
. I was hoping to get fast tracked in
but he pretty much pointed me towards a different position within Google. Basically you're an employee for a year, they groom you to work at Google, and if you're good enough then they'll probably hire you on full time. Here's a shortlist of what he asked me:
- Most proficient language (If it's C# like it was for me
, get into C++ and Java)
- A recent project you worked on that was a success
- Familiarity with Google products
- Your areas of expertise (I flubbed this a bit
)
- If you have a GitHub (If you don't
)
- Open to relocation (Basically to the Bay Area [I would have preferred Orange County
])
- When you think you'll be ready to start the process
- Are you talking to any other recruiters
The position I'd be going for is 2 45 minute phone interviews, then a series of on-site interviews if you make it that far. Like I mentioned before, or in another thread, basically be prepared for anything. Data structures, algorithms, logic and reasoning, Big O notation, writing clean and efficient syntax, thinking out loud, asking clarifying questions, things of that nature. I have about 5 months to prepare so I have no excuses if I don't nail this shyt. Time to dive in.
Good looking out. The dude actually emailed me the 4th edition of the book. I already have the 5th and 6th. I've been slowly working through it, but I need to pick up the pace. The problem I'm having is thinking too much about efficiency rather than solving the problem. I'm also not cool with having to come up with a solution in 30 minutesGood luck my boy recently got a software engineer job at google. Relocated to cali and all
He said this book was a HUGE help. The questions in here were harder than what was asked he told me.
Good looking out. The dude actually emailed me the 4th edition of the book. I already have the 5th and 6th. I've been slowly working through it, but I need to pick up the pace. The problem I'm having is thinking too much about efficiency rather than solving the problem. I'm also not cool with having to come up with a solution in 30 minutes. My thinking is that if you need to come up with production code in that short amount of time then you made some serious missteps earlier in the development process. You'll get either an elegant solution or a quick fix out of me, but it ain't gonna be both
.
He asked about it and I gave it to him. I uploaded a class project earlier in the day in preparation. I need to go back and clean up some of my other repositories though. No documentation, hastily thrown together. I might as well tackle that now since I'm sat here doing nothing.Your github will sell your talents far more than any interview will
If you have a repository with > 50K lines of solid code doing useful things you will have doors opened for you