Top products from r/girlsgonewired

I don't think I could do a mock interview exactly... not sure that would be kosher. But I can definitely offer you some tips from my experience with both the intern and full-time interviews.

How to prepare:

• Study algorithms and data structures as much as you can. Google doesn't ask the type of questions where the answer is just "a hash map!" or "depth first search!". But those things will be the building blocks of your solutions, so know your tools.
  
  
• Pick a language you're comfortable in ahead of time. Python is my favorite for interviews, since it's pretty terse and clear. But you can pretty much choose anything. The coding questions aren't language-specific.
  
  
• Take some problems from a textbook or something and practice coding in a plain text document, or even on paper. No IDE, no compiler, no running your code, etc. You won't have any of those tools in the interview, so you should practice without them.
  
  
• If you can beg, borrow, or steal the book "Cracking the Coding Interview" and read it in the next two weeks, do it. The author, Gayle Lakmann McDowell, worked at Google, where she interviewed a ton of candidates and was on a hiring committee. She also has an interview prep website, CareerCup, which I haven't explored.
  
  
• There are some YouTube videos going through the interview process and providing some tips. I linked two but the "Life at Google" channel has more.
  
  
• Feel free to ask the recruiter if there's anything in particular you should study or how you should prepare. They really want you to be ready and do your best, so they should be happy to guide you in the right direction.
  
  How to interview:
  
  
• Take a deep breath first! (literally... you can mute for a moment so you don't sound creepy.) You can do this. You've studied for this and you're ready. Once you've got a problem in front of you, stop thinking of it as an interview at all. It's just coding, and that's your thing.
  
  
• You may get a few easy questions first, but sooner or later you'll be faced with a problem you don't know how to solve. That's exactly as intended. The interviewer wants to know how you approach a hard problem, to get an idea of how you think. In fact, solving the problem is not necessarily the goal.
  
  
• Ask for clarification about the problem. What does the input look like? What does the output look like? How big is the data? How should you handle a certain edge case? The interviewer will be happy to answer, in fact, sometimes the problem can only be solved by asking the right questions first.
  
  
• If you're stuck, your interviewer will likely toss out a hint or nudge you in the right direction. Definitely pay attention to that hint, because the interviewer is honestly trying to help you succeed.
  
  
• Think out loud. As long as you aren't typing, describe what's going through your head. "Well, the naive solution for this would be [...], but that would take O([...]) time, and I think I can figure out something better..." The more you say about what you're thinking, the easier it is for the interviewer to help you. Having been on the interviewer side, it's really hard to think up a hint for someone who's just going "hmmmmmm" over an empty doc.
  
  
• No matter how interview #1 goes, you have a clean slate with interview #2. So stay calm, and whatever happens, let it go and focus on the next problem.
  
  What's next:
  
  
• For interns (at least when I was an intern), they don't do onsites. So this is the main part of the interview process that is basically intended to assess your technical abilities. If it goes well, the rest will be placement interviews where you'll talk to potential hosts and try to find a good fit for an intern project.
  
  Good luck!! It's always really exciting for me to hear about young women applying to Google. Hopefully I'll see you rocking the propeller beanie this summer. :)
  
  P.S. I love your username. Avocados are amaze balls and I don't know what I would eat if they didn't exist.

Knowing what you're working with really helps determine what strategies to try first. It also helps you forgive yourself for having trouble with tasks that are not going to be in your wheelhouse. For me, knowing I'm not 'failing' to be organized, I'm succeeding at being semi-organized, means I can be kinder to myself for forgetting a doctor's appointment.

I rely a lot on bright colors to help organize things, though my apartment seems yet to have succumbed to the 'colorization is a good proxy for organization' theory. For example, I color the tops of pill containers according to when they need to be taken (blue for night, orange for morning, purple for as-needed), so they can all be thrown into a clear bin on the table in a disorganized pile, which is an improvement on not knowing where they were at all. Sometimes I'd find one in the kitchen. Basically, since I'm never going to be good at 'everything has a place' I try to maintain more of an 'everything has a general region'.

Doodles are excellent! Da Vinci would be proud. If you can, have your doodles saying things in word bubbles that were especially important in the lecture. Also, if you need to not be doodling for something, consider getting a fidget toy, there are a ton of different kinds on the market as people get more comfortable with kids fidgeting a little to help them stay in their seats and stay focused, and they're starting to get marketed to adults. Try getting a multi-pack that includes a flippy chain

Figuring out the right balance of occupied attention and difficulty of task takes a bit, but if you have a kind of task you do regularly, eventually you figure something out and can get into a groove. Then you just have to make sure you don't get distracted before you start your routine :) Sometimes, if it's a task that requires sporadic focus, I have to make sure it's an audiobook I know well to hit that balance.

There are a ton of organizing tips for us, but not all solutions will work for all people. And someday I will actually finish this book.

Late to the party, but SailorHG zines/pins are always super cute and awesome. https://shop.bubblesort.io/collections/all

Cute flash drive wristbands for portable tools/fav resources/fav scripts
https://www.amazon.com/FEBNISCTE-10pcs-Flash-Multi-Coloured-Bracelet/dp/B00P2JIHZ4/ref=sr_1_1

Good question. Thanks for asking! What do you mean when you say
>the requirement of unquestioning faith?

As far as I've been able to tell, the crucial things about Christianity - the resurrection of Jesus and the reliability of the Bible - are historically well attested. For me, that's the most compelling thing about Christianity, actually - that it makes sense in light of what I see in the observable world. I think some people have maybe an inaccurate perception of what Christianity's about, and that can be a source of confusion and miscommunication when we talk about "science and religion" (which, by the way, I think is somewhat of a false dichotomy).

That was kind of rambly, but I hope it at least began to answer your question. By nature, I'm a fairly analytical (read: doubting Thomas) kind of person, so I appreciate your asking about this.

If you're interested, Tim Keller's The Reason for God has been a helpful book for me as I've thought through these things.

> ...gain some experience under my belt

I agree with /u/ivix; it's the wrong kind of experience. If you have a CS degree, then you should be developing, not answering phones.

I recently entered the field, and I found https://pramp.com/ to be super useful for technical interviews both over the phone and in-person. They're live, so it feels a lot like a real interview (i.e., nerve-wracking).

Also, Cracking the Coding Interview is a must. There might even be a copy at your library if you don't want to buy your own copy. This walks you through the interview experience at the big software companies (Microsoft, Amazon, Apple, Google, etc.), and teaches you how to solve an algorithm problem, not what the answer to each problem is.

Finally, as dumb as it is, I'd recommend practicing coding on a white board (or a piece of paper). It's stupid that companies do it, but if you practice it, it'll be easier to think about the problem you've been asked and not about how weird it feels to be writing a loop in marker rather than typing it. Write sort algorithms, BFS/DFS, fibonacci, etc. Not that any of that stuff will necessarily help you, but I felt much more comfortable in the actual interview because I was used to drawing code.

Let me know if you have any questions and goodluck!

Sorry about that, this link here should work.

The course is basically taken directly from this book but I did find watching the videos helpful, while the quiz question solutions were discussed in-depth in the book.

Does she like Minecraft? This teaches Python and Arduino

https://www.amazon.com/Adventures-Minecraft-David-Whale/dp/111894691X/ref=pd_sim_14_3?_encoding=UTF8&pd_rd_i=111894691X&pd_rd_r=82ZPBFAWFRG98HK616WR&pd_rd_w=TSabr&pd_rd_wg=QjMrR&psc=1&refRID=82ZPBFAWFRG98HK616WR

Yes, absolutely, I've had feelings like this!

An other perspective which you might find helpful is the idea of 'Stereotype Threat'. Here, the problem is that the self-consciousness and pressure you might be feeling could be distracting you from doing your true best.

https://en.wikipedia.org/wiki/Stereotype_threat
http://www.amazon.com/Whistling-Vivaldi-Stereotypes-Affect-Issues/dp/0393339726

Claude Steele has been studying the phenomena for decades, in an effort to understand why minorities traditionally underperform despite equal credentials and clear talent. Stereotype threat experiments have repeatedly shown that when people are reminded of a negative stereotype related to a difficult task (one that requires focus), they perform worse on the task. For example, in an experiment with Asian women, they reminded half the participants that 'women are bad at math' before giving them a math test and the other half that 'Asians are good at math'. The participants reminded about the negative female stereotype performed significantly worse (in a p-value sense) than the other group.

Furthermore, in his studies of college students, he found that most minority students studied alone. As a result, they learned more slowly -- partly because they had to figure out everything on their own and partly because they missed the opportunity to explain things to others, which is a great way to solidify what you know. This also made them feel isolated, so they don't see how much everyone else is also struggling with the material. So my advice is to try to find some like-minded souls to program with; at minimum, try to do your homework in labs and libraries and strike up conversations with others. Nothing spots a bug like a fresh set of eyes.

And also, please try to keep a growth mindset about learning so you don't sweat every test grade and assignment. Practice makes perfect. Mistakes are opportunities to learn. None of the supposed 'naturals' at coding where born with that skill. Have you ever seen a baby try to the code? They suck at it. They can't even read.

PS - In countries where negative stereotypes about women and math/computing/science don't exist, women frequently outperform men, shown in the following graphic

https://mathbabe.org/2013/02/10/gender-bias-in-math/