Tag: computing (Page 3 of 4)

SensoryPaint

January 17, 2014 / kateringland

Many children with neurodevelopmental disorders, such as autism spectrum disorder, have sensory processing disorders (SPD), which can lead to inappropriate behaviors and impairments. One therapeutic approach to the kinds of SPD frequently observed in children with neurodevelopmental disorders involves the use of a variety of tools including objects with various textures and tactile sensations, mirrors, and Multisensory Environments (MSE) saturated with visual and audible stimuli and specialized equipment for sensory stimulation. However, children with SPD each have a unique prescription for the amount of stimulation they require for the therapy to be effective. MSE must be physically altered before each child receives therapy.

Traditional Multisensory Environments uses mirrors, lights, and objects with different tactile feedback.

Colored rubber balls of different sizes.

Various sizes and colors of balls used in SensoryPaint.

SensoryPaint is an interactive surface with the capability of superimposing the user’s reflection on a projected surface and “painting” this surface with balls of different textures and colors, which was designed to augment traditional therapies. This software uses a Kinect to detect the movements of the user and the balls. The user’s image is reflected on the screen, as well as their shadow superimposed on their reflection. SensoryPaint is a software originally developed at CICESE in Ensenada, Mexico.

Mode with painting and splashes.

Coloring Book Mode with the user using two different colors to fill in the strawberry shape.

Initial studies of the SensoryPaint system are focused on uncovering the potential of this technology to support sensory integration, including stimulus sensitivity, body awareness, motor functioning, and attention and engagement.

Ringland, K.E., Zalapa, R., Neal, M., Escobedo, L., Tentori, M., and Hayes, G.R. “SensoryPaint: A Multimodal Sensory Intervention for Children with Neurodevelopmental Disorders”. Proceedings of the 2014 ACM International Conference on Ubiquitous Computing, ACM (2014).

No posts found.

Daily Log: CHI2013 Day 4

May 17, 2013 / kateringland / 0 Comments

So, I’ve finally found time to write my last day of CHI entries. I was sad to see CHI be over, but on the other hand, four days of solid conference is a lot of conference.

I first attended Vint Cerf‘s talk in the morning (he was one of the inventors of the internet). I thought the whole talk was interesting. He discussed how everything is now going on the internet and it’s important that standards be created so everything can talk to each and talk to the aliens when they come to visit from outer space. The best part of his talk, however, was when he ended the first part of his talk and launched into the necessities of accessibility. Now this just happens to be my area of interest. And apparently, not enough people are interested, unfortunately.

Vint Cerf talks about Computer Conversations

Star Trek and Ubiquitous Computing, Talking to a Mouse

Vint Cerf at the Podium

Slide on Accessibility

I then went the session on Autism. I enjoyed listening to all the papers presented. The first (Why Do They Still Use Paper? Understanding Data Collection and Use in Autism Education by Marcu et al.) covered why teachers and caretakers in schools were still using paper to keep track of all the student records. Basically it comes down to: there is no really good software solution yet for schools. The second paper (TOBY: Early Intervention in Autism through Technology by Venkatesh et al.) was about the Toby Play Pad, which is an app that is meant as an early intervention tool when parents find out their child is autistic. It targets four developmental areas: sensory, imitation, language (receptive and expressive), and social (eye gaze, joint attention). The third paper (Evaluation of Tablet Apps to Encourage Social Interaction in Children with Autism Spectrum Disorders by Hourcade et al.) was on a method to evaluate tablet apps for encouraging social interaction. The fourth paper (Investigating the Use of Circles in Social Networks to Support Independence of Individuals with Autism by Hong et al.) was about social media and using social networks to support youth with autism. This helps shift the burden off over-reliance on the primary caregiver and spreads it around to other people in the youth’s social circles.

In the afternoon, I also attended a panel with Vint Cerf discussing accessibility and what’s currently being done. It’s nice to know some big names in computing are concerned about this and maybe it will get more attention this way.

Finally, here is a slide show of the rest of Paris, in case I don’t get around to a post about that part of my trip:

Daily Log: CHI2013 Day 2

April 30, 2013 / kateringland / 0 Comments

Today was day 2 of CHI for me. It was a long, but wonderful day. I started by attending the CHI Women’s Breakfast. The food was very good and we got some very cool swag from Google, Microsoft, and Facebook. I met a table full of very interesting people including Bonnie John and Arnie Lund. While I was not very happy with the logistics of the breakfast (the organizers tried to direct our conversation, which ended up just making the conversation more stilted and less about what I would have liked to talk about). We still ended up running over into the first morning session.

During the first break I was supposed to talk to people about my poster. Unfortunately, my poster did not get put up after the judging session. I am sad to know I will probably not get it back because a lot of hard work was put into that poster and I was hoping to hold onto it.

My favorite paper for the morning was Analyzing User-Generated YouTube Videos to Understand Touchscreen Use by People with Motor Impairments by Lisa Anthony et al. This was another study that looked at a specific set of videos found by searching on YouTube. I learned about how valuable user generated content on the internet can be as a source of information about a group of people.

Then I went to lunch with my UMBC family. It is really nice to be able to spend time with some people here that are friendly, familiar faces. CHI is so large that it can be quite overwhelming at times. After lunch, I spent some time with Amy and Lisa. They both gave me a lot of really excellent advice about my upcoming transition to grad school. It was nice to get some insight into my journey ahead and also to know that there are safe people I can turn to for advice if I need it. It’s these connections to a support network that will ultimately be the most important thing I foster as a grad student, I think.

In the afternoon session, I especially liked the paper entitled Technology Preferences and Routines for Sharing Health Information during the Treatment of Chronic Illness by Carolyn Pang et al. This was a study of how families with an individual with chronic illness uses different technologies to connect with each other for comfort. This was probably one of my top favorite papers thus far, it’s up there with the Motherhood paper from yesterday.

I then spent about five minutes at the hospitality reception at the convention center. It was way too crowded with not enough to drink, eat, and do. I met up with a bunch of people later to attend the joint UW, U of Michigan, and Georgia Tech party. I met a couple of people that I was happy to meet. Otherwise it was another loud, crowded place with not enough to drink and eat.

I’m happy for all the connections I am making here at the conferences. I feel like I can start this summer of research at UCI strong now. But first! Two more days of CHI!!

Daily Log: CHI2013 Day 1

April 29, 2013 / kateringland / 0 Comments

Woke up at 7 this morning in order to give myself plenty of time to get ready and head to the convention center before the morning keynote. The weather turned really nice today so it was a very nice walk to the convention center from our hotel. It takes about 15 minutes if I walk a little briskly.

The keynote speaker was Paola Antonella from the MOMA. Her talk was about design- what is it and how people perceive it. People often mix up design with art, but they really aren’t the same thing at all. She talked about how design is about the interaction, how people interact with objects and their environment. She explained her video game installment. She maintains that these video games are one way users interact with their world, often times intertwining the physical with the virtual. To me, it now makes sense why Dwarf Fortress would be the perfect sort of interactive object for her installment. I really enjoyed her talk and it made me think a little differently about how I personally view the things I’m interacting with and how I would like to approach design in the future.

CHI 2013 Dwarf Fortress

I then went to the Enhancing Access session. My two favorite papers from the session were Older Adults as Digital Content Producers by Jenny Waycott et al and Health Vlogger- Viewer Interaction in Chronic Illness Management by Leslie Liu et al. The first was interesting because it looked at how older adults can be users and creators of digital content and how that interaction played out amongst themselves. The second showed what vloggers on youtube have done when suffering from chronic illness. The vlogging actually acted as a wider support network for the person suffering from the illness and actually gave them a sense of purpose and comfort by educating viewers on their illness (like showing people they are still a human being even though they are HIV positive or demonstrating how chemo works). I connected with this paper because I have found blogging and making videos therapeutic in my own life.

Then I had lunch from the grocery store at the lower level of the conference center. I just sat on a step and watched people go by for an hour (and there were plenty of them). It was quite refreshing.

I then went to Technologies for Life 1 in the afternoon. Overall, I think I enjoyed this session more than the more session. I don’t know if I was just more awake or if the speakers were just more engaging, or I liked the topics more- or all three. I think my favorite paper was called Digital Motherhood: How does technology help new mothers? by Larna Gibson and Vicki Hanson. This was a study on how new mothers use technology, such as smart phones and the internet, to stay connected to the outside world. As I know a lot of people who have recently had kids I have personally witnessed this phenomenon. I liked the way the study was conducted- the researcher had just had a child so she was already attending “mommy and me” groups. She basically did an anthropological survey and recorded relevant information as it surfaced during conversations. She then later interviewed a select few of the mothers for a more in-depth follow up. The note Access Lens: A Gesture-Based Screen Reader for Real-World Documents by Shaun Kane et all was also really cool. The technology used was a camera that could help a visually impaired user find their way around a paper map, for instance.

I then attended the Student Research Competition judging session. It was a complete mess from an administrative standpoint. The room was too small and there was no where to hang our posters. Students had to alternate holding posters when it was not their turn to talk. Because of the time crunch, the judges had to split into two groups, which meant we had to present our poster twice, once for each set of judges. And the groups went at the same time, so the room was completely silent except for two people talking about their posters at once. Then it was timed, so we had exactly one minute to speak and then 1.5 minutes for questions. The timer would yell “STOP!” really loud at each interval. It was all very nerve-wracking. I think my talk went okay, but I probably could have prepared more. Anyway, I did not win, so I will not have to give a presentation on Wednesday. I still am giving my poster presentation to the public during the first break tomorrow, but then after that I can relax and enjoy the rest of the conference.

I ended my evening with dinner at Oresto just down the street from the conference center. It was my very first Abowd family meeting. I was even presented to the group as the newest family member (second generation apparently). It was really nice. Everyone seems super great and I’m really happy to have such a supportive group of people around me.

A street on my walk back to my hotel in the evening.

Now it is late and I have another long, full day ahead of me tomorrow!

On Getting Into Grad School, Part 4

April 20, 2013 / kateringland / 0 Comments

Did you miss Part 3?

March 2013: UC Irvine Visit and THE Decision

After leaving Boulder and hearing what students there had to say about their school, I was more inclined to accept Irvine’s offer. I wasn’t going to say with 100% certainty until I had visited the school and made sure I clicked with the people there, but based on the research that was happening and what I heard from others, Irvine was the way to go.

It did not take me long to feel like my initial instincts were correct. I got off the plane and already felt like I had come home. Now, I had to be cautious, because in a lot of respects, I had come home. I spent the first 12 years of my life in Southern California. I had decided that Kyle, my husband, needed to come with me on this visit. If this was going to be our home for the next 5+ years, I wanted to make sure it was going to work for him. He was not as impressed at first as I was. I knew what he meant about it not being “green”. The Pacific Northwest is definitely a lot greener, but I think that’s probably not the best reason to turn down a grad school offer. J I also have to say the women huddled around the hot chicken case at the Whole Foods because it was under 70 degrees outside was extremely humorous.

When I checked us into the hotel, I was given a “goodie” bag with snacks and a folder full of information about the school and department. I think the snacks were a really great touch, even though I couldn’t eat most of them. I did enjoy the pudding cup and the Star Wars gummies. The information packet was definitely overwhelming. It had lots of information on what research was going on and other facts about the school. It also contained a hardcopy of my acceptance and award letter. There was also a schedule for Friday, which included what professors I was going to interview with.

Thursday night we had a dinner with the current Informatics grad students. It was great waiting in the hotel lobby and meeting up with some of the people I had met in Boulder. Already knowing a couple people made the whole experience slightly less daunting. The current grad students picked us up and we had a big dinner together. I got to meet my roommate that I will be staying with in Paris for CHI. I also met other students who I would potentially be working with in the future. And apparently my reputation preceded me because at least one of them already knew of me. I am going to admit, it was completely surprising, but also felt pretty good.

I came back to the hotel feeling very excited for the next day. If the grad students were any measure, I was really going to like this place. I’m going to admit, it was hard to share these experiences with Kyle and give him a good sense of how I was feeling. I think my excitement (and exhaustion) was pretty obvious though.

The next day, Friday, I got up early and had breakfast with Kyle. I then waited for the shuttle to take me over to the school. Apparently, there was some confusion and only have of the prospective students had signed up for a ride, so the whole day started a little more slowly than anticipated. We drove straight to the Bren School of Information and Computer Science. I received an additional packet of information that was more general to the entire School. The morning was spent going over all the great things about the school, “the second happiest place on earth” (after Disneyland, of course). Then we broke down into subgroups of Informatics, Computer Science, and Statistics. We spent more time talking about the Informatics department specifically. I learned about the degree, what kinds of courses I would be taking, the research, how the department operates. One of the things that really caught my attention (and this had come up at the grad student dinner as well) was that there seemed to be a lot of collaboration and cooperation. It didn’t feel like there was negative competition, it was more like everyone was trying to help everyone else out. That’s the sort of environment I was looking for.

Then I got to meet with three professors. While they all had really interesting research that I could see myself working on, I knew as soon as Dr. Gillian Hayes told me about the Autism Research Center, I was hooked. This was the sort of assistive tech research that I wanted to be doing. I told her in the interview that I was set to come to Irvine straight away. How soon could I start working?

I feel extremely fortunate that things have worked out this way. I feel lucky that I found a department that feels good and an advisor that I felt an immediate connection to. I know the road ahead will be challenging, but I’m happy that I chose this road or that this road chose me. However that works out.

On Getting Into Grad School, Part 3

April 13, 2013 / kateringland / 0 Comments

Have you read Part 2 yet?

October 2012: More Traveling Fun

Amidst getting through my senior year classes (which were amazingly more difficult than my previous courses), I traveled some more in the fall. At the beginning of October I went to the Grace Hopper 2012 Conference in Baltimore, Maryland. I had been given a scholarship to attend, all expenses paid. It was great because I was traveling with some of my friends from the west coast. We all stayed in the same hotel and I got to show them a little bit of Baltimore (like the train from the airport to downtown).

At Grace Hopper, I was sure to visit the booths of some of the schools I was planning on applying to. It was nice to connect up with people I had made connections with the previous year and with those I had made connections with over the summer.

Later in October, I attended ASSETS 2012 in Boulder, CO. This conference was a lot smaller than anything else I had been to, but it was definitely worth the trip. Here again, I connected up with people from the summer and learned a lot about the assistive tech scene. It was sort of an affirmation that this was the field that I wanted to go into and was proof that it was a viable field to go into. I think one of the best parts was going to dinner with Amy and Michele (that I worked with over the summer) and getting all sorts of advice on how to proceed with my grad school application process. It was a lot more information in one evening than I had ever gotten from anyone at my home institution. I am glad to have made these connections and definitely don’t want to ever turn up the opportunity in the future to make more connections like these.

November 2012: Wrapping Up the Semester and the Applications

By the time I came home from ASSETS I was ready to finish up my applications and get everything done. I had a much stronger idea of what to write for my personal statements and a stronger overall story for the application package. I spent the rest of November writing all the different personal statements and starting to turn in my applications. For the most part, I was able to get all of my applications done by the first of December. This gave me a little breathing room before finals. While the majority of the applications were due December 15^th, I didn’t want to be trying to turn them all in last minute.

It was at the beginning of November that my first paper (I was second author) got presented at a conference. The conference was in Taiwan, so I didn’t have the funds to go, but it was still exciting to have a paper published.

December 2012: This is the End?

I got all my applications done before finals and wrapped up the semester completely exhausted. And broke. Did I mention how much money this whole process ended up costing? I’m a little scared to actually tally up the total, so I won’t. But it was a lot. It was probably in the neighborhood of $1000 after application fees, GRE tests, and transcript requests.

Then the worst part of the entire process began. The waiting.

Knowing that my entire future was in the balance and that the outcome of these applications would determine where I would be living and what I would be doing in less than a year was completely nerve-wracking. And it wasn’t just my life I was messing with- it was also my husband’s.

January 2013: Dealing with Rejection

Luckily, schools were on the ball and started culling their applications by mid-January. I got a couple of rejections right away. While this was a bit discouraging, I had mentally prepared myself for such occurrences. And a rejection was much better than not knowing at all.

But I didn’t have much time to feel sorry for myself or worry too much because I was also keeping myself busy with school and MORE travel! I was prepping at this point to head to the Tapia Conference in Washington, DC. I was to present a poster on work I had done in the fall for my professor.

Right before I left for the conference I found out that I had a phone interview with UC Irvine the Monday after I got back. While I was very nervous about this, I was happy I had made it past the culling phase with at least one school!

I also got invited to interview with Facebook at the Tapia Conference and invited to a Google workshop called Google.GetAJob(). I felt like I would have a lot of hard decisions to make in the next couple of months about our future.

February 2013: It All Starts Coming Together

The first week in February is when I attended the Tapia Conference. While I was there I spent a day visiting my friends at the University of Maryland Baltimore County. I talked to them about my grad school applications and interviews. It was really great to catch up and also know that what I was going through was completely normal. The conference itself was also really great. I got to meet people from all over and network with the research labs. I did a poster presentation, which I had only done once before. I got a lot of really great feedback and most of it was positive, too.

During the conference, immediately after my Facebook interview, I got an email saying that I had been accepted to present my poster at the Student Research Competition at CHI 2013 in Paris. If I had had any thoughts of just skipping graduate school and going to industry, they instantly vanished. I knew I wanted to do well at CHI and continue doing research that I enjoyed so much.

After I came home from the Tapia Conference, I had my interview with UC Irvine. It was very informal and a really positive experience. I was able to tell them I had gotten accepted to CHI, which really helped my own confidence.

I also found out that I was invited to an interview on campus at University of Colorado, Boulder set for the 14^th of February. So, off I went on another trip after having just come back from Washington DC.

The night before I left for Boulder, I found out that I had gotten into UC Irvine. I was over the moon. It also made me feel much more comfortable while traveling to Boulder. There I met with students and faculty on the campus. I really loved the town, at least until I got snowed in and ended up staying an extra day. I’m not sure I could live in a place where there’s that much snow. It was still a great learning experience and I got a good idea of what I wanted to find out about Irvine when I visited them in March.

On Getting Into Grad School, Part 2

April 6, 2013 / kateringland / 0 Comments

Did you miss Part 1?

Summer 2012: DREU Internship, University of Maryland, Baltimore County

I won’t go into all the great details of my life during this summer internship. Most of it can be found other places on this blog already. The highlights I will mention are: after working at UMBC I began to realize that going to grad school could really happen and that I might actually enjoy it, Amy and others at the school really mentored me and helped me get a deeper understanding of the whole process of grad school applications, and I started actually writing my grad school application material.

Having this internship gave me a perspective into what grad school could be like. I can’t imagine applying to grad school without knowing that experience and knowing whether or not it was something I could handle/enjoy. I was also able to talk with Amy about potential schools and make a list of schools I would consider applying to in the fall. It was the mentorship and guidance that I really appreciated. Just being able to talk to someone who knew the field and could give solid feedback about my ideas was great.

I also got to do some really cool research and see other people working on some equally awesome stuff. I got the chance to write a paper (which I later submitted, more on that later) and present a poster at the end of summer festival. I was even selected to present my work to the entire festival, which was a huge learning experience. I had to put the power point together (make a video for it!), write the presentation, and then speak to a room with at least 100 people in it. It felt like every step I had taken that summer was a new one, going deeper into a mysterious cave of wonder or something.

August 2012: Home Again (And Time To Get To It!)

By the time I had come home and started back at school for my senior year, I had already completed my list of schools I was going to apply to, started a rough draft of my statement of purpose, and signed up (and taken the week before classes started) for the GREs.

It was at this point I made one of my bigger mistakes. I really should have asked for more help. It’s hard when you’re at a small university and very few people truly understand why you would even want to apply to a PhD program. As has been a consistent theme for me, I felt isolated and, therefore, isolated myself. I could have reached out to more mentors (at home and at UMBC), but I decided to go it alone. This was especially difficult to write and edit my statement of purpose(s) and the essay for the NSF GRFP.

I sorted out my references as soon as classes began. I committed one of those faux pas where I only had three letter writers. Fortunately, they all pulled through and I didn’t to materialize another letter writer at the last minute. I used two professors from my home institution that I had worked with on research and with my ACM-W Chapter. My third reference was my mentor from UMBC.

September 2012: Keeping it All Straight

I think the hardest thing from September on was keeping everything organized. I had to keep track of all the materials I was submitting to each institution. It felt like every single one had different essay requirements (not to mention all the other requirements!). Some wanted multiple essays, others wanted just one. And the length was different for each as well. Some only wanted 500 words or less, while others were 2000 words. There was no real way to write just one essay and tweak it for each. I had to write fresh essays for almost every university I was applying to.

Next week: lots of traveling and the submissions in Part 3!

On Getting Into Grad School, Part 1

March 30, 2013 / kateringland / 0 Comments

This blog is probably one that would have been better written in the moment rather than as a retrospective, but as you will see from the timeline I was too overwhelmed with everything else going on to think about writing a blog.

When I was looking to apply to grad school I scoured the internet for information from other grad students and professors looking for anything that would give me the best possible chance at a) knowing if this grad school thing was what I wanted to do and b) giving me the best possible chance of getting into the grad school that was going to be best for me. Now that I’m on the other side of the application process and I’m feeling great about the outcome, I thought I would attempt to share my experience for the next generation of applicants looking for more information.

DISCLAIMER: This is a completely personal experience and should in no way be treated as a how-to guide. Everyone is going to be different, coming from a variety of backgrounds and going into a multitude of different fields of study. Please don’t read this as the perfect way to get into the grad school of your choice; I’m sure there are much easier ways of doing it.

I think the best way to do this is write this out as a timeline of events, with links and info about each of the events. If this gets to be too long, I’ll break this into multiple parts and if something needs more attention than everything else, I’ll break that into its own blog article.

October 2011: Grace Hopper 2011

I went to Grace Hopper in Portland, OR as a student volunteer. It was the first time I got a real good look at what someone could really do with a computer science background. I met a lot of students who were in grad school working towards their PhD. I heard about some cool research being done that I learned was in the field of Human-Computer Interaction (HCI). Up until this point, I thought a computer science degree was good for getting a job at a software company writing code. The seed of the idea of grad school is planted.

January 2012: Industry Job Interviews

Between Grace Hopper and early 2012, I subjected myself to several really uncomfortable industry interviews. Let’s just say coding on the fly, in a high pressure situation and recalling complex algorithms and data structure optimization is *not* my strongest skill. It’s at this point I really start to question what I am doing and why I am trying to push myself into something that clearly isn’t working out.

February 2012: DREU Internship Application

At the very last minute, I decided to apply to the CRA-W’s DREU internship. It’s also around this time that I started working with a professor at my campus on his smart grid research. He had asked for volunteers, so I decided that it was worth the experience.

It was also around this time I decided that I wanted to pursue a career more in the area of HCI. I was taking the elective “Intro to HCI” offered by my school (which turns out was that great of an intro) and thought my interdisciplinary studies in Psychology and Computer Science were a good fit for this area. I applied for a scholarship to attend CHI 2012 in Austin, TX through the ACM-W.

March 2012: DREU Acceptance and Matching Results

At the beginning of March I received an email saying that I had been accepted to the DREU program for the summer. I was really excited and very worried at the same time. I hadn’t done any extensive traveling and never really on my own. They said they would email me soon with my matched mentor and the location I would be traveling to for the summer. I looked at all the past mentors and their universities. Where would I be living that summer? Who would I have to work with? The only things I had heard from friends that had completed REUs was how awful it was. The mentors just give you some project and are too busy to actually mentor you. The projects aren’t of much consequence or the results end up being something you can’t get a publishable paper out of… I started wondering if I had done the right thing.

I was up all night worrying I would be shipped off to some strange place I couldn’t survive and have a mentor I wouldn’t be able to work with. However, I was not in agony long. It was at school the next day when I got my match-up. The rest, as they say, is history. You can read plenty about my DREU internship on my blog space. Dr. Amy Hurst was the best mentor a person could ask for. She was exactly what I needed at a time when I didn’t even know what I needed or what I was doing with my life.

April 2012: CHI 2012 in Austin, TX

My first real research conference was CHI. Talk about amazingly overwhelming. It’s a lot of people. And I had never been to Texas before. And it was my first time on a plane in years. I really enjoyed it, nonetheless. I think my overall impression was excitement that so many people from so many different places were all passionate about the same thing. There were more computer-oriented people and there were more psychology-oriented people, but they all meshed together to make something pretty exhilarating.

People ask me what my favorite talk was and I don’t even remember. I think if I went back to the program notes and see what I went to, I would probably recall. I have learned a lot since I was there though. How to go to conferences and pick what talks you want to see is an important skill.

CHI is also where I met Dr. Amy Hurst for the first time and some of her students. All in all, it was a good first experience into a world I was soon to submerge myself in.

The saga continues next time in PART 2…

Because It’s a FAQ…

March 26, 2013 / kateringland / 0 Comments

I just wanted to write a short blog entry about this whole “grad school” thing because I’ve been getting some questions about what exactly it is I’ll be doing in the next few months.

This fall I’ll start towards my PhD in Informatics from the University of California Irvine. My research area is in Assistive Technology and I think I’ll be doing my work in the area of tech helping kids with Autism and chronic illness. I really won’t know my research space until I get into the work and get a feel for what I’m doing.

The way grad school works, at least in the field of tech and computer science, is that when a school offers you acceptance there is usually some sort of funding package that comes along with it. For instance, a lot of schools will offer 3 years of funding, which usually covers tuition and then gives you a monthly stipend. In order to earn that monthly stipend, depending on the school, of course, you work 20 hours a week doing research or TAing. In my case, I’ll be expected to TA one year and then do research projects for the remaining time in the program. After you second year or so, you have usually settled on an advisor and a research path and can start getting grants for the work you are doing. This will be in lieu of “working” for the department. I have been getting some questions as to how I’m going to live while getting my PhD and there is the answer: I’ll be getting paid to do it. Yes, it won’t be as much money as I could be making as a programmer straight out of my bachelor’s degree, but if I wanted to be a programmer, I wouldn’t be going to grad school. I’ll still be making way more money than I’m currently earning, and I guess that’s the perspective I’m going in with. I’ll be quite comfortable with what I have.

I’m going to grad school because I love doing the research. This is what I learned from completing my DREU at UMBC last summer. That really was the one of the best experiences I have ever had in terms of my own personal growth. At this point in time, I haven’t really thought PAST earning my PhD; it’s be a long road just to get this far. I’m sure that in due course, it will become apparent where I want to pursue my career, whether it is in industry or academia.

Do feel free to email me if this didn’t clear things up for you. I’m quite happy to talk about all the in’s an out’s! =D

Google.GetAJob() 2013

February 11, 2013 / kateringland / 0 Comments

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:

Apply to the job you want.
Your resume is reviewed by real human beings, not machines, and then passed along if it is found qualifying.
1^st 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.
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.
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.