Tag: graduate school (Page 5 of 5)

Google.GetAJob() 2013

Recently, I had the great fortune of attending Google.GetAJob() at the Google office in Washington, DC during the Tapia Conference (more on that in another blog!). This is a program Google puts on for students that have a minority status in the computing field. I know they hold this events for certain universities, but since my university is so tiny, it’s great they decided to put this on for Tapia Conference attendees.

I did have to fill out a survey and be selected for this workshop. I think checking the box “have done multiple technical interviews and never had an offer” might have tipped the scale. No way to know. Doesn’t matter, I’m just happy to have had the experience.

To sum up in one word: empowering.

I feel like the Googlers there took the power of the technical interview situation and put it back in my hands. All of the sudden, these engineers weren’t these amazing, untouchable computer gods (don’t get me wrong, they are still amazing at what they do), but instead they are just people. In fact, they are women and minorities- many of them who have recently graduated and were in the same exact position I am in now (except I want to go to grad school and put off that amazing Google job for a few more years, but I digress).

Since I got all this great info on the in’s and out’s of the ominous technical interview, I thought I would pass it along to the magical internet land. So, here are some of my notes and thoughts. I realize some of them may seem obvious, but I want to have this all together in one location (for my own future reference!).

How the application process works at Google is as follows:

  1. Apply to the job you want.
  2. Your resume is reviewed by real human beings, not machines, and then passed along if it is found qualifying.
  3. 1st round of interviews on the phone. There will be probably 2 of these and they will be technical. The coding is usually done in a google doc or something of that ilk.
  4. If applying for a Full Time position, 3-5 technical interviews are then done on site. If applying for an internship, there is a host matching process to see if there is a good place for you.
  5. A hiring committee then decides whether or not to extend the offer.

The entire process will take ~1-2 months, unless there is a specific time crunch (other offers, etc).

Obviously, this is very Google specific, but I know most of the big tech companies are going to do something at least similar. Facebook, for instance, (I know since I just did a first round of interviews with them) does a phone screen (or conference/campus screen) which is a technical interview. If they like you, they will fly you out to Menlo Park for ~3 interviews onsite.

Another important thing to point out: no matter what position you are applying for, whether it is software engineer or ux researcher, you will have to do technical interviews.

An interesting Google tidbit is they highly encourage their employees to publish their work. This doesn’t apply to all work, but if the research isn’t something they want to hold on to for a while for obvious reasons, they will encourage it to be published.

Resumes. These are what get you the first interview, so they are very important. Since this was a workshop for students, I’m going to be describing what a typical student resume should strive for.

The most important things should be top, front, center. Education (when you are graduating, gpa, name of school), what position type you are looking for (internship versus full time), and languages. For languages, list them including proficiency. The Googler reviewing my resume recommended using the phrases “Proficient in: language list” and “Familiar with: language list”. This keeps is clean and easy to figure out what exactly you know. Also, never include the word “expert” unless you wrote the language yourself because it’s just asking for trouble in your interviews.

Next on the resume should be relevant experience. I originally had projects/experience listed separately from my work experience and my reviewer recommended lumping them all together in one clean section. Sort this list by relevance, not chronology. Remember, anything closer to the top will get noticed first (and possibly be the only thing that gets noticed during the skim). So, if you did something amazing on a project, put that first. Sell yourself.

Another big thing that I heard several times was that Google was sad to see so little in terms of Open Source projects on student resumes. List any projects and especially highlight any open source work. If you have time, maybe go DO an open source project because it will a) make you a more awesome programmer and b) help you get a job. The reason open source is coveted is because employers can easily just go look at any code you have written and see your abilities. They can get a really good feel for how you program without the pressure of an interview.

Do include towards the end of the resume your other great stuff: awards, honors, publications, patents, conferences, presentations, and interests. Google wants to hire interesting people, so if you are doing something interesting in your spare time (do you actually have spare time as a cs student???) then add it.

Key Resume Ideas:

  • Sell Yourself
  • It’s okay if your resume is more than a single page, as long as your most valuable info is on the front at the top
  • Be interesting!

The Technical Interview. I am going to be honest. So far, I have really been terrible at these. I am the sort of person, who when their intelligence is questioned freeze up and look way dumber than one can possibly imagine. I know that this part of the getting hired process is always going to be the hardest thing for me. I have accepted that and can live with it. I just need to get good enough to get through.

Biggest take home message for the technical interview. Know your programming language of choice inside and out. Be good at it. How do you do this outside of your course work? Do your own projects! Make an app, code up a game, or do something you think is fun and interesting. It doesn’t have to ever leave your computer if you don’t want it to, but it’s important to just practice, practice, practice. Remember how I was talking about the whole open source project. Join one of those cool open source communities and start working on their code. It’s a great way to get coding and meet a whole new support group.

Data structures, algorithms, and generally being able to problem solve will also be must haves for the interview process. Big companies will expect you to know the general structure (and be able to code) things like stacks, queues, graphs, hashmaps, trees, etc.

At the end of the day this is what they are really looking at during a technical interview:

  • Do you know the language you picked? Can you code?
  • Can you analyze a problem and then algorithmically optimize that solution?
    • You don’t have to be optimal at the first go, just get a solution out and then start talking optimization.
    • Does the code you wrote on the board work? Would it compile?
  • Before saying you’re done, test your code! Be sure to keep edge cases in mind (it might be a good idea to write these down before you even start coding).

One big thing that I saw today in the mock interviews and have been guilty of myself in the past, is jumping right into coding before mapping out your idea, writing out test cases, and generally clarifying the problem. If the interviewer asks you to define a function, it’s totally okay to ask all the questions you need in order to write the most productively. Today some of the students in my group didn’t know how a stack worked, so they just froze up and freaked out. Ask questions! Is the string you are working with in ASCII or UTF-8? How is the data being stored in that tree? What kind of data are we sorting? And so on… Then draw pictures, write out ideas, outline the solution, write snippets of pseudocode. These things will help when it comes to finally coding up your solution. First, it will help you not get lost in the code. “What was this loop supposed to iterate on, again…?” And it may help when it comes to testing and optimizing too!

One final tech interview tip: listen to the hints your interviewer is giving you. They really do want you to do well! Think of the interview as more of a coding amongst friends situation (yeah, I find that advice a little hard to follow as well).

Doing mock interviews was an excellent experience for me, not because I practiced writing code up on a whiteboard or solving these problems on the fly, but because I got a chance to see just how NOT behind I am in terms of my abilities. I am in a constant state of not believing in myself when it comes to my coding abilities. I dread telling people I’m a senior because then they expect me to be able to code things. But honestly, the students I coded with today were all over the place in terms of their abilities. So maybe I can do this afterall…

That about sums up my notes from today. It was an AMAZING experience. Everything I have heard about Google’s work place seems to be fairly accurate: nice space, cool toys, and great food. Everyone there was extremely nice to me. I definitely recommend if anyone has the opportunity to attend one of these workshops in your neighborhood. If you don’t get the chance, I hope these notes will help you along the way to your own CS career.

Just remember to seek out new opportunities and seize them! Good luck on your endeavors.

ASSETS 2012 Conference

To be honest, I started this blog immediately after I returned from the ASSETS 2012 conference, but everything else in this semester got away from me and I didn’t post it. I’m on winter break now, so I am finally able to catch up on things.

I have finally returned home from my journey to Boulder, Colorado. Firstly, we drove. We should have realized what a crazy idea this was when we stood in a room full of Ringlands, told them our plan to drive down to Boulder and back in a week, and no one even batted an eye.

Family eating lutefisk dinner.

Some of the Ringlands eating at the lutefisk dinner in Poulsbo.

With a belly full of lutefisk (because nothing says the start to a great road trip than unending plates of lefse and lutefisk) we left Poulsbo, WA to arrive 36 hours later in Boulder, CO. I’m going to admit upfront that I missed the keynote Monday morning.  We rolled into the hotel as the address was about half-way over.  If only we hadn’t stopped for that 2 hours of sleep in Rawlins, Wyoming!

First impressions:

*ASSETS is much, MUCH smaller than any other conference I have attended (less than 100 people versus a couple thousand plus).  This allowed me to get to know a lot of the people there.

*ASSETS is a single-track deal.  This was great!  I didn’t have to choose between two awesome papers.  Everything is in one room.  With the exception of the keynote, I didn’t have to miss any of the conference.

*It’s really nice having such a close-knit, small community.  People were super enthusiastic not only about their own projects, but other people’s work and were very willing to get in there and give each other ideas.

There was a lot of really fantastic work presented at the conference.  It ranged from web accessibility to assistive tech hardware to biofeedback interfaces. The populations being worked with were quite varied from physically disabled to the elderly to the visually impaired and so on. I think the most heartening thing about the conference was to see how much great work is being done to help people.

The grad student I worked with on my DREU project, Michele A. Burton, gave her presentation on the accessible fashion we had been working on. She did a fantastic job. I very much wish to follow in her footsteps.

Boulder itself was absolutely beautiful. I had the opportunity to visit the campus and see the Human-Centered Computing Lab there. It was great to meet some of the students and see what projects they are working on. This is definitely one of my top choices for graduate schools.

We got 5 inches of snow just as the conference was ending. It forced us to stay an extra day, but it was worth it.

Snowy creek and trees.

A creek near our hotel in Boulder, CO.

Fall Week 6

This past week has been EXHAUSTING.  It was a whirlwind of exams and getting everything finished up for Grace Hopper.

GREs were on Monday.  I took about 3 hours and I’m happy with my scores.  They aren’t official for another week or so, but I got an estimate right after the test was over.  I’m glad I have one less thing to worry about when it comes to grad school applications.

Tuesday I had my Web Data Management midterm and Thursday was Algorithms. PHEW!  Both went well, I think.   We also gave the demo for our first team project in Web Data Management.  This was the first time I really had to do a demo for an instructor like this.  I had one demo for Systems in the spring, but it definitely wasn’t anything like this.  Now I know what to expect for next time- the prof actually asking us why we chose to do things certain ways, etc.

After exams finished, I was able to focus back on grad school stuff.  I’m working on getting my three essays written for the NSF grant, which is due Nov 13th.  I know that the deadline is going to come at me way too fast, so I want to get rough drafts written for everything.  I have a personal statement draft for grad school applications done, so I’m hoping to use at least some of that for NSF.  I’ve also got a draft of my previous research done.  All that’s left is the research proposal.  I have an idea for it, but I have to do some more background research first to make sure it’s viable.  I hope so because it will be pretty good, and go fairly painlessly (I hope) once I have the research bit done.

My CREU research is also experiencing some forward momentum, as I’m starting the process of collecting wattage data.  I’m hoping after I get back from Grace Hopper to have some more done!

Off to Baltimore!!

Fall Week 5

I have yet to have a blog post this semester get published on time.  I am endeavoring to correct this.  Perhaps this is the week I get lucky!  This week I had to make some tough decisions and figure out what was going to get cut from my schedule because I am just too busy.  Between working (research), school work, home life (some of my home life is feeling sorely neglected at the moment), traveling, and getting ready for grad applications I have zero time.  It’s getting me sick and I’m super exhausted.  So, something has to give.

I decided to drop the Game Design class, even though it is by far my favorite elective.  I am still going to attend the lectures, but I simply don’t have time for all the homework.  I was spending ten times more of my outside class time working on projects for that class than all my other classes put together.  Not a good balance.

This week started off the first round of exams.  This coming week I have GREs on Monday, Web Data Management on Tuesday, and Algorithms on Thursday.  Luckily, then I’m off to Baltimore for Grace Hopper!  I have finished downloading the conference app on both my phone and tablet.  I’m starting to figure out exactly what I need to pack.  I’m super excited!!

Since dropping the extra class, I’ve actually managed to get some things accomplished.  I’ve finished fixing up my DREU section of the website, so that I can get my last paycheck (which I could really use right now).  That was a huge weight on me.  Now I have to build a new section for my CREU work, which I’ve been putting off.  I think I will actually have enough time this weekend to get that done too.  I’ve also gotten a nice chunk of research work for CREU done as well.  I’ll hopefully get around to updating my website, so I can start sharing snippets of that.

I also attended the club orientation on campus so that our ACM-W Chapter can be official.  I got some good ideas for things I would like to do with the group, so I need to start organizing meetings for that.  I still have to work on the website, but I think some of this will have to wait until after Grace Hopper, unfortunately.  There is just not enough time in the day for everything!

Fall Week 4

This week was kind of a blur, except that the newest member of the family was born Thursday night!  I was able to go visit him in the hospital Friday afternoon.  Here’s a picture of me with Thane:

Auntie Kate and Little Thane, September 14, 2012

School has been very overwhelming.  I feel like I don’t have time to spend on the things I really want to be learning and spending time on, like my research, because everything is just sucking up all of my time.

I did do a quick run (THANKS to Kyle for driving me!!) to Seattle Thursday afternoon to attend the iSchool information session.  I had an opportunity to talk to the PhD advisor and hear a bit about the program.  The biggest thing I realized is that I really need to get on this whole writing to professors, drafting up my essays, and generally getting more serious about grad school applications!

Fall Week 2

Well, as it might be imagined, I am super swamped.  I feel like I’m being pulled every which way and I need to get a better system for organizing my life.  I’ve this giant running to do list that is a little overwhelming.  I’ve started breaking things down by day and trying to organize one 24-hour period at a time.  We’ll see how it goes.

I’ve been trying to get my DREU final report finished up and sent off.  I’m actually quite happy with the results.  I migrated my work into LaTex and am starting to feel pretty proficient in editing in it.  I’m going to post my paper in my portfolio, if you’re interested.  I am a little bummed I couldn’t participate in some of the interviews and maybe work on getting something into CHI for this year.  I guess I could still possibly submit something for the Student Posters in January.  We’ll see.

I’ve also officially bought my plane tickets to Balitmore for Grace Hopper the first week of October.  I’m excited to have won the scholarship.  I’m looking forward to seeing Baltimore again too.  I’m already planning on meeting up with my friends from UMBC that I met during the DREU program.

I think that’s all for now.  I’m hoping I can use these blogs to get myself organized too.  We’ll see how it goes. 🙂

Week 8

This week I finished up putting tags into the clothes. I also did a lot of writing this week.  I submitted two poster abstracts- one to the campus Research Festival and one to Grace Hopper.  I also started a draft of the final paper for this project I have been working on all summer.  Luckily, actually quite enjoy the writing process.  I’ll be finding out this coming week if my poster abstracts were accepted.  Next up:  making a poster!

On Thursday, I went to the ADA Celebration on campus.  We put some of our projects on display, including the clothe I have tagged.  It was really great meeting people and talking a bit about the work we have been doing.  We also heard speeches from Dr. Hrabowski and Governor O’Malley.

UMBC HCC Group at the ADA Celebration July 26, 2012

UMBC HCC Group at the ADA Celebration July 26, 2012

Me at the ADA Celebration

Me at the ADA Celebration

This coming week I’ll be working more on my paper and designing my poster.  I hope the RFID reader parts come in, so that I can build the last system for the project.  I’ll also be playing around with an NFC enabled tablet to see if I can get it to read the tags we have in the lab!

 

Week 7

There was a lot going on this last week, especially now as I am looking at deadlines for my poster abstracts and wrapping up for the summer.

We finally got our “smart closet” put together with shelving and all!

Smart Closet

A nice, organized closet space for our clothes that are going to be tagged.

We narrowed down our list of tagging systems that we want to prototype.  We had a fashion hackathon on Tuesday to put together the website that will be part of our prototypes.  For some of our systems, the user can look up a button shape or specific location to help remind them of what it identifies (color, how to wash, etc).  In another web based system, the user can input a number that is written in braille on a tag inside the clothes to get all the information about it.

Fashion Hackathon

Fashion Hackathon

3 Braille Tags in Puff Paint

Ribbon with Braille in Puff Paint

 

 

Star Button Tag in Shirt

This star represent certain information about this shirt.

 

 

 

 

 

 

I also built some prototypes with a more high-tech solution.  One uses the QR code iron-on to the clothes.  A second solution is the RFID tag with reader.I am still waiting on the parts for the reader before I can prototype this system.

Row of QR Codes

QR Codes ready to be printed.

On Wednesday, I went to the Summer Horizons grad school information session on campus.  The information presented was phenomenal.  They went over the timelines,  keys to admissions (GRE Scores, Letters of Recommendation, and the Statement of Purpose), and what life is like as a grad student.  There was a panel of grad students that answered questions about their own application process and what their lives are like now.  To finish everything off, Dr. Freeman Hrabowski gave a great keynote speech.  I wish I had recorded it, but I was too busy watching!

One of the things Dr. Hrabowski said was the following quote, which really stuck with me: “Watch your thoughts; they become words. Watch your words; they become actions. Watch your actions; they become habit. Watch your habits; they become character. Watch your character; it becomes your destiny.”
– Lao Tzu

I’m glad I attended this information session, even though it wasn’t strictly a part of the internship I am doing.  It helped me to really start exploring the reasons I want to go to grad school and how to organize my thoughts so I can get my applications together.

Wednesday afternoon, summer students from the Maryland School for the Blind came to visit UMBC.  As part of their visit, the HCC department gave them some information about the research they do here on campus.  Michele and I got to informally talk with some of the students about my project that I have been working on this summer.  Some of them were really excited about the idea of just scanning clothes and getting the information about them.  One student wanted to know when they would be able to buy the system.  It’s really nice getting such positive feedback about the work I have been doing.

This coming week I will be writing abstracts for my research posters.  I will be finishing up my prototypes, which will probably take the bulk of my time.  I’m down to sewing in buttons and ribbons.  As soon as we have IRB approval, we will be able to take our clothes to users to see what they think of our prototypes!

Week 6

This week I worked with Amy and Michele to redevelop my project scope for the rest of the summer.  In addition to RFID tags and readers for clothing, I am going to help brainstorm other ways someone could tag their clothing.  I spent the first part of the week looking up how people are currently keeping track of their clothes.

I then decided on some different ways to tag clothes.  Some ideas were buttons, safety pins, QR codes inside the clothes, and RFID tags.  I then went on a shopping trip with Michele to stock our closet and get supplies for our prototype systems.  At the end of the week I started prototyping some tags.

Sample Tag

I also spent some time with Amy looking forward to see where this research is headed.  I’ve started thinking about what I will be doing after this summer is over and applying to graduate school.  This experience hasn’t gotten me excited about keeping the momentum I have here going.

Newer posts »

© 2024 Kate Ringland, PhD

Theme by Anders NorenUp ↑