c0110

5 ms·

1.
by c0110 5y ago
Everyone learns differently, so find the way you learn best. If you learn best by doing, you should do side projects, and they don't need to be novel ideas. There are tons of lists of project ideas (e.g. https://austinhenl
2.
by c0110 7y ago
First, whatever you may feel about your tech lead -- don't let it get out to prospective teams. Complaining about people in a previous team will look bad on you. (Even if it's not your fault, that's how interviewers may perce
3.
by c0110 9y ago
Don't know if you can say Google as a whole does 20% time. But there are many Googlers who do 20% time. I've done several 20% projects in the last 2 years.
4.
by c0110 9y ago
The Quora link another poster submitted is a good starting place. * Steve Yegge's advice (often cited when people ask how to prepare for Google interviews): https://steve-yegge.blogspot.com/2008/03/get-that-jo
5.
by c0110 9y ago
Did the recruiter give you a list of materials to review? You need to practice whiteboard coding in a timed setting as well. Leetcode is a good place to practice online, but a whiteboard is even better. If you need interview practice, you c
6.
by c0110 10y ago
The best feedback I received was from a hiring manager who said I was not senior enough for the position (they only hire senior engineers at that company). After my onsite interviews, we had a series of phone calls that pushed me out of my
7.
by c0110 10y ago
+1 to this. I was in the same situation as OP (company laid off most employees due to funding) and I always told my interviewers, "Honestly, I really didn't want to leave :)" None of the interviewers really raised an eyebrow
8.
by c0110 10y ago
This is exactly how I am. It takes a little practice to balance out the silence with speaking but when you find your comfort level, you'll be ok. :) I've told interviewers something to the effect of, "Sorry, give me one secon
9.
by c0110 10y ago
I found that mock interviews helped me to some degree with this. It's hard for me to talk and write code simultaneously, so practicing in front of someone who is an experienced interviewer helped me gain some confidence in whiteboard c
10.
by c0110 10y ago
This is anecdotal -- but it seems like companies are more or less pretty understanding if your reason is justifiable. I had a string of jobs (fulltime, then laid off, then consulting for 3 separate clients). I interviewed with over 20 compa
11.
by c0110 10y ago
I've worked with 2 graduates from Dev Bootcamp who contributed a lot on the team. (~5-7 developers total) One of them came on as an intern (originally we weren't going to take him on, but we re-interviewed him. The second time aro
12.
by c0110 10y ago
Hey there. I didn't take Algorithms in college and am also not so good at it. Don't fret -- you'll get it. Grab a couple interview study books, the Algorithms Design Manual, etc. and study. It'll be hard and you might no
13.
by c0110 11y ago
I don't have a project, but I wish the best of luck and hope things turn out better for you!
14.
by c0110 11y ago
Trying to drink from the firehose without taking a break to breathe every so often. I usually don't think about it till the body starts freaking out and refuses to let me keep going. This year I started 4 new jobs. 1 at a startup after