Tag Archives: students

My Path to Google: Julius Adebayo, Google AI Resident

Welcome to the 14th installment of our blog series “My Path to Google.” These are real stories from Googlers, interns, and alumni highlighting how they got to Google, what their roles are like, and even some tips on how to prepare for interviews.

Today’s post is all about Julius Adebayo. Read on!



Can you tell us a bit about yourself?

I grew up in Nigeria, and came to the US for college. I studied mechanical engineering in undergrad, but started to drift towards machine learning (ML) around my last year. Afterwards, I ended up pursuing a master’s degree in computer science, focused on machine learning, and another in technology policy. In general, I am interested in research that tries to provide guarantees that deployment of machine learning in the real-world will be safe and reliable. My focus has been in studying bias, interpretability, and privacy/security all within an ML context. I also enjoy thinking about the intersection of machine learning and policy, especially how current advancements will affect daily life down the line. Outside of school and work, I enjoy listening to Jazz and Nigerian music in all its glory. I like playing soccer, and watching the NBA. Lately, I have become more interested in trying to spread machine learning knowledge to places in West Africa where machine learning expertise is not abundant.



What’s your role at Google?

I am one of the current residents in the Google AI Residency Program. The goal is to collaborate with researchers and engineers on the Google Brain team to do deep learning research.  Deep learning research is new to me, and I am actually coming to it as a skeptic. There is a famous quote attributed to Von Neumann that says, "With four parameters I can fit an elephant. Give me five and I can make it wiggle its tail." The point of that quote is you typically want models that don't have too many parameters because you could make such models do anything. However, deep learning models tend to violate that requirement. Since being here, I have come to appreciate working with neural networks. There is a vibrant community here that is actively working to address several problems with the current models, especially in regards to security, potential bias, and stability of machine learning models. The work I am doing now is focused on assessing the performance of neural network explanation methods. (This link is closely related.)



What inspires you to come in every day?

The Google Brain team has several researchers and engineers who are working on really interesting projects. Talking to other residents and researchers, I find that I leave every conversation having learned something new. The breadth and depth of research on the team is incredible and it is quite fun to be in an environment like that.



Can you tell us about your decision to enter the process?

I found out about the residency program through a friend. As someone working at a startup doing ML, it was impossible to not hear about deep learning on a daily basis. I figured the residency would be a way to try and get to the cutting edge of work in this area as fast as possible. The Google Brain team has several researchers doing really interesting work. I remember reading some papers from ICLR, and noticed that a few of the papers I enjoyed reading came from researchers on the team.


How did the recruitment process go for you?

The recruitment process was quite smooth. I felt like I was aware of what was required at each stage, and I found the recruiters to be accommodating to my requests or questions. I was also given an opportunity to talk to a few researchers on the team.



What do you wish you’d known when you started the process?

Google can be overwhelming, especially given the concentration of expertise on the team. I would be more open to asking questions and reaching out to people doing interesting work.


Can you tell us about the resources you used to prepare for your interview or role?

The residency interview had a coding and research portion.
I had gone through software engineering interviews before, so my preparation there was using the whiteboard type experience I already had in that context. For the research angle, I went through a few deep learning papers that I found interesting, and tried to understand them. A few of the papers were discussed extensively in some of my interviews. I also spent some time reviewing past research I had done, so I could explain it well to others.


Do you have any tips you’d like to share with aspiring Googlers?

Apply for the Residency Program now at g.co/airesidency/apply!

Google Summer of Code 2017 Mentor Summit

This year Google brought over 320 mentors from all over the world (33 countries!) to Google's offices in Sunnyvale, California for the 2017 Google Summer of Code Mentor Summit. This year 149 organizations were represented, which provided the perfect opportunity to meet like-minded open source enthusiasts and discuss ways to make open source better and more sustainable.
Group photo by Dmitry Levin used under a CC BY-SA 4.0 license.
The Mentor Summit is run as an unconference in which attendees create and join sessions based on their interests. “I liked the unconference sessions, that they were casual and discussion based and I got a lot out of them. It was the place I connected with the most people,” said Cassie Tarakajian, attending on behalf of the Processing Foundation.

Attendees quickly filled the schedule boards with interesting sessions. One theme in this year’s session schedule was the challenging topic of failing students. Derk Ruitenbeek, part of the phpBB contingent, had this to say:
“This year our organisation had a high failure rate of 3 out of 5 accepted students. During the Mentor Summit I attended multiple sessions about failing students and rating proposals and got a lot [of] useful tips. Talking with other mentors about this really helped me find ways to improve student selection for our organisation next time.”
This year was the largest Mentor Summit ever – with the exception of our 10 Year Reunion in 2014 – and had the best gender diversity yet. Katarina Behrens, a mentor who worked with LibreOffice, observed:
“I was pleased to see many more women at the summit than last time I participated. I'm also beyond happy that now not only women themselves, but also men engage in increasing (not only gender) diversity of their projects and teams.”
We've held the Mentor Summit for the past 10+ years as a way to meet some of the thousands of mentors whose generous work for the students makes the program successful, and to give some of them and the projects they represent a chance to meet. This year was their first Mentor Summit for 52% of the attendees, giving us a lot of fresh perspectives to learn from!

We love hosting the Mentor Summit and attendees enjoy it, as well, especially the opportunity to meet each other. In fact, some attendees met in person for the first time at the Mentor Summit after years of collaborating remotely! According to Aveek Basu, who mentored for The Linux Foundation, the event was an excellent opportunity for “networking with like minded people from different communities. Also it was nice to know about people working in different fields from bioinformatics to robotics, and not only hard core computer science.” 

You can browse the event website and read through some of the session notes that attendees took to learn a bit more about this year’s Mentor Summit.

Now that Google Summer of Code 2017 and the Mentor Summit have come to a close, our team is busy gearing up for the 2018 program. We hope to see you then!

By Maria Webb, Google Open Source 

Google Code-in contest for teenagers starts today!

Today marks the start of the 8th consecutive year of Google Code-in (GCI). It’s the biggest contest ever and we hope you’ll come along for the ride!

The Basics

What is Google Code-in?

Our global, online contest introducing students to open source development. The contest runs for 7 weeks until January 17, 2018.

Who can register?

Pre-university students ages 13-17 that have their parent or guardian’s permission to register for the contest.

How do students register?

Students can register for the contest beginning today at g.co/gci. Once students have registered and the parental consent form has been submitted, students can choose which task they want to work on first. Students choose the task they find interesting from a list of hundreds of available tasks created by 25 participating open source organizations. Tasks take an average of 3-5 hours to complete. The task categories are:
  • Coding
  • Documentation/Training
  • Outreach/Research
  • Quality Assurance
  • User Interface

Why should students participate?

Students not only have the opportunity to work on a real open source software project, thus gaining invaluable experience, but they also have the opportunity to be a part of the open source community. Mentors are readily available to help answer their questions while they work through the tasks.

Google Code-in is a contest so there are prizes! Complete one task and receive a digital certificate. Three completed tasks and you’ll also get a fun Google t-shirt. Finalists get a hoodie. Grand Prize winners receive an all expense paid trip to Google headquarters in California!

Details

Over the last 7 years, more than 4,500 students from 99 countries have successfully completed over 23,000 tasks in GCI. Intrigued? Learn more about GCI by checking out our rules and FAQs. And please visit our contest site and read the Getting Started Guide.

Teachers, if you are interested in getting your students involved in Google Code-in we have resources available to help you get started.

By Stephanie Taylor, Google Open Source

Bring Computer Science to Your Community: Volunteer with Google igniteCS

Google’s igniteCS student volunteer program is kicking off another year of computer science (CS) volunteering! For the past three years, university students around the US with a passion for computer science have gone into local K12 schools, spreading the excitement to the next generation about where computer science can take them. We’ve seen over 2,000 students share their love for computer science and this year, we’re excited to welcome the next cohort from states like Florida, Ohio, and New Mexico. We’d love for you to join the Google student volunteer community too! You can register on the website and we’ll send you everything you need to get started.

Piero Castillo, a third year CS major at the University of Central Florida, and a member of the Society of Hispanic Professional Engineers (SHPE), has been volunteering through the student volunteers program  at a local high school for the past year.  

He developed a love for CS early into his college career and believes “CS is always relevant…technology is part of everything.” Sharing his knowledge and passion with younger students has created a lasting impact on Piero and the students he worked with. At the end of last school year, a high school student who was motivated by his experience with the igniteCS volunteers said that he “never realized how much CS could accomplish and wanted to keep learning.”

Piero Castillo, CS major at the University of Central Florida


Over at the University of Cincinnati, Mansi Patel, a leader on her school’s ACM Council on Women in Computing (ACM-W), began volunteering with Google’s CS student volunteer program when she realized there were issues engaging undergraduate women in the CS major.




She wanted to get students involved starting in high school, showing the girls that going to college and majoring in CS were real options for them. Mansi has seen “a huge difference in the students [she’s] taught” and continues to lead the way in bringing CS to the next generation.

Mansi Patel, igniteCS volunteer at the University of Cincinnati


We invite you to join this community of over 2,000 college volunteers to bring computer science to your community. Registered university students have access to lesson plans, materials, and support from Google to implement volunteer programming. Just gather a group of students at your college and register on the website. We’ll send you lesson plans and a free kit of materials to get started.

Happy volunteering!

_____

To register for igniteCS, visit the website or email [email protected] for more information.




My Path to Google: Derek Pierce, Staffing Services Associate

Welcome to the thirteenth installment of our blog series “My Path to Google.” These are real stories from Googlers, interns, and alumni highlighting how they got to Google, what their roles are like, and even some tips on how to prepare for interviews.

Today’s post is all about Derek Pierce. Read on!


Can you tell us a bit about yourself?

I'm from the suburbs of Philadelphia (specifically Doylestown, for anyone familiar). I attended James Madison University (JMU) in Harrisonburg, Virginia, and received degrees in Quantitative Finance and Mathematics. When I'm not working, I love to keep active, and I also enjoy a good brunch! I’ve recently gotten back into surfing, and I’m looking forward to the upcoming snowboarding season.


What’s your role at Google?

I am a Staffing Services Associate (SSA) on the College Staffing Services Team. I primarily engage with software engineers who are about to graduate from an undergraduate, masters, or PhD program. I also specialize in scheduling research scientist candidates and internal Googlers. I like working on the specialty candidates the most because they come from extremely diverse backgrounds and are usually being brought on to develop the next Google product.

Currently, I’m working on a project to grow our interviewer pool by gathering more complete information about our interviewers, so we can properly match their expertise with our candidates.


What inspires you to come in every day?

It’s very exciting to be with a company that’s motivated to make an impact on a global scale every single day. I feel very fortunate to be here and want to play my part in finding the next generation of Googlers.


Can you tell us about your decision to enter the process?

I was interested in working for Google ever since I was a sophomore in high school. I kept hearing that Google was the paradise version of work, where you could change the world for the better and have fun doing it. I applied for every program that I thought I was qualified for, and was very determined to work here one day. I was ultimately given an interview during my senior year of college, and although I had a different background than most people entering the staffing industry, I was optimistic about my chances.

How did the recruitment process go for you?

I first applied to be a Data Scientist through an alumni of JMU and was redirected to interview for the Staffing Services Associate position. I instantly took them up on the offer to interview. After passing through the phone interview stage, I remember flying out the next day to interview onsite, then flying back just in time to take my fall semester finals.


Can you tell us about the resources you used to prepare for your interview or role?

I used the provided resources from the recruiter, as well as anything I could find on the internet, specifically YouTube. I reviewed the "How We Hire" page and the job posting about 20 times before the interview.


Do you have any tips you’d like to share with aspiring Googlers?

Talk to anyone you know who has been through the process. Use resources such as YouTube, and brainstorm possible questions based on the job posting.





See yourself at Google as a Staffing Services Associate? Apply now!

Bring Google Hash Code to your university: Register your hub today





Hash Code is back for its 5th year of challenging students and professionals in Europe, the Middle East, and Africa to solve a Google engineering problem. Registration to compete opens in early January, but hub registration is open now at g.co/hashcode. Bring developers at your university together to compete — register your Hash Code 2018 hub today!



More than 26,000 participants teamed up to optimize how videos are served online for the Hash Code 2017 Online Qualification Round. Excitement and tensions were high across the region, especially at the 467 Hash Code hubs organized by university clubs, developer meetup groups, and participants.



Hubs bring teams in the same local area together for the Online Qualification Round. While teams can compete from wherever they’d like, participating from a Hash Code hub adds a bit of extra fun to the competition — as evidenced by last year’s hub photos!



To give you more insight into Hash Code, we caught up with Dominika and Adam, who organized a hub in Kraków, Poland last year, to find out more about their experience:





Why did you choose to organize a hub?

We chose to organize a hub because we felt that providing an opportunity for people to come together and work on a challenging problem is the best way to let them develop their skills and themselves.


What was the process of setting up your hub?

There was the normal event stuff, like booking a room, getting approvals from our university, and ensuring Wifi was set up. We also started promoting the event a few weeks earlier to be sure we had as many participants as possible. The real fun started just before the competition when we decorated the room with balloons and posters — luckily a few participants came early so they decided to join us and help!


What's your favorite part about hosting a hub?


Meeting new people! That’s definitely the best part. You can feel the passion and excitement in the room.






The Online Qualification Round for Hash Code 2018 will take place on March 1, 2018. If you think you’d like to organize a hub at your university, you can sign up today. If you can’t host a hub but would like to compete in Hash Code 2018, fill in this form and we’ll email you as soon as registration opens early next year.

My Path to Google: Melissa Holguin, Software Engineer, YouTube Music

Welcome to the twelfth installment of our blog series “My Path to Google.” These are real stories from Googlers, interns, and alumni highlighting how they got to Google, what their roles are like, and even some tips on how to prepare for interviews.

Today’s post is all about Melissa Holguin. Read on!


Can you tell us a bit about yourself?
I grew up in Doral, Florida, which is a suburb of Miami. I went to college at the University of Central Florida and studied a full circle of engineering majors. I started in Computer Science (CS), then switched to Electrical Engineering, switched again to Computer Engineering, and finally ended up returning to CS my junior year of college, adding on a Music minor to go along with my CS degree. Outside of work, I like archery, bowling, video games, and binging on TV shows. Every once in a while, I get inspired and do some music producing.

What’s your role at Google?
I'm a Software Engineer on the YouTube Music Analytics team. I love that I get to be on a team that mixes music and technology. I just recently started on this team, but it looks like I'll be working on improving charts for music artists and tracks.

What inspires you to come in every day?
Even after a year of working at Google, it still feels surreal sometimes that I get to work with the most brilliant minds — it inspires me to work hard every day and makes me feel that my creativity will be put to good use.

Can you tell us about your decision to enter the process?
I had always thought of Google as the top dog of technology companies. It was definitely on my list of dream jobs, but I always thought it would be a long time before I'd be qualified to work there. I was thrilled to find out that someone thought I was ready just as I was finishing up my degree in CS.

How did the recruitment process go for you?
I was contacted by a recruiter that found my profile on Linkedin. I was extremely surprised, since I still had two semesters to finish before graduation, and I wasn't planning on applying anywhere until I was in my final semester. The recruiter first reached out in September and I didn't get my final decision until January, so I was definitely anxious in the time between because it was such a huge deal for me.

What do you wish you’d known when you started the process?
I wish I would've known about the Engineering Residency program beforehand. It ended up being the perfect fit for me!

Can you tell us more about the resources you used to prep?
I mainly used this website called InterviewBit, which was really good for practicing coding questions from all different categories. I spent around five hours a day solving problems for a week leading up to my first technical interview.

To finish, do you have any tips you’d like to share with aspiring Googlers?
Keep an open mind and don't pass on an opportunity based on specifics alone. In large companies like Google, there is so much room for growth and change. You never know what kind of opportunities will open up in the future, so your knowledge and experience will be a useful thing to have.

Want to learn more about the Engineering Residency? Watch our video, or head over to g.co/EngResidency. Ready to apply to the residency? We're currently accepting applications at https://goo.gl/rhBmj1.

My Path to Google: Olumuyiwa Adenaike, Software Engineer

Welcome to the eleventh installment of our blog series “My Path to Google.” These are real stories from Googlers, interns, and alumni highlighting how they got to Google, what their roles are like, and even some tips on how to prepare for interviews.

Today’s post is all about Olumuyiwa Adenaike. Read on!


Can you tell us a bit about yourself?
I was born and raised in Lagos, Nigeria, Africa's largest city. Growing up, I was always intrigued by science and math, and this inspired me to move to the US right after high school to major in computer science at DePaul University in Chicago. Outside of work, I like to stay active as much as I can by playing soccer, basketball, and lifting weights. I also enjoy cooking new dishes from time to time.


What’s your role at Google?
I am a Software Engineer (SWE) on the Google Now quality team, which ensures that we are serving users with content they are interested in. A cool project that I am currently working on uses Machine Learning to predict what content to show the user depending on their interaction with the app.


What inspires you to come in every day?
I am inspired every day by the product I work on. Knowing that millions of people all over the world use and depend on what I help build makes me always eager to work and learn new things. I am also inspired by my team members who share my eagerness, as well as their deep technical knowledge and expertise. I appreciate the opportunity to learn from them every day.


Can you tell us about your decision to enter the process?
I was interested in Google because of the principles the company stands for, such as fairness and equity, freedom of speech and information, and charity. Also, I knew the best minds were at Google, and in order for me to move forward in my career, joining Google was the best choice.


How did the recruitment process go for you?
I was contacted by a Google recruiter during my senior year in college. I went through the process while I was studying for finals, so I was anxious the entire time. The hiring process was smooth, and although I had a lot of interviews, I was happy with the outcome at the end.


What do you wish you’d known when you started the process?
I wish I had spent more time on personal projects and also on larger collaborative projects throughout my college years. I feel that would have helped me learn to get my points and ideas across better in the interviews.


Can you tell us more about the resources you used to prep?
I spent a lot of time practicing algorithm-based questions for the technical interviews. I also did research about the position and met with other software engineers at Google to get advice on navigating the process. In addition, I had a practice interview with a Google engineer, which really helped me have a better idea of what to expect.


To finish, do you have any tips you’d like to share with aspiring Googlers?
Spend a good amount of time honing your skills and refining your craft. It is important that you believe in yourself and your abilities, as they will speak for you during the interview process and in your day-to-day work. Also, don't be discouraged if you don't make it; there are many people at Google who got hired after several tries.


Want to learn more about the Engineering Residency? Watch our video, or head over to g.co/EngResidency. Ready to apply to the residency? We're currently accepting applications at https://goo.gl/rhBmj1.

Welcoming 25 mentor organizations for Google Code-in 2017

We’re thrilled to introduce 25 open source organizations that are participating in Google Code-in 2017. The contest, now in its eighth year, offers 13-17 year old pre-university students an opportunity to learn and practice their skills while contributing to open source projects.

Google Code-in officially starts for students on November 28. Students are encouraged to learn about the participating organizations ahead of time and can get started by clicking on the links below:

  • Apertium: rule-based machine translation platform
  • BRL-CAD: computer graphics, 2D and 3D geometry modeling and computer-aided design (CAD)
  • Catrobat: visual programming for creating mobile games and animations
  • CCExtractor: open source tools for subtitle generation
  • CloudCV: building platforms for reproducible AI research
  • coala: a unified interface for linting and fixing code, regardless of the programming languages used
  • Drupal: content management platform
  • FOSSASIA: developing communities across all ages and borders to form a better future with Open Technologies and ICT
  • Haiku: operating system specifically targeting personal computing
  • JBoss Community: a community of projects around JBoss Middleware
  • LibreHealth: aiming to bring open source healthcare IT to all of humanity
  • Liquid Galaxy: an interactive, panoramic and immersive visualization tool
  • MetaBrainz: builds community maintained databases
  • Mifos Initiative: transforming the delivery of financial services to the poor and the unbanked
  • MovingBlocks: a Minecraft-inspired open source game
  • OpenMRS: open source medical records system for the world
  • OpenWISP: build and manage low cost networks such as public wifi
  • OSGeo: building open source geospatial tools
  • Sugar Labs: learning platform and activities for elementary education
  • SCoRe: research lab seeking sustainable solutions for problems faced by developing countries
  • Systers: community for women involved in technical aspects of computing
  • Ubuntu: an open source operating system
  • Wikimedia: non-profit foundation dedicated to bringing free content to the world, operating Wikipedia
  • XWiki: a web platform for developing collaborative applications using the wiki paradigm
  • Zulip: powerful, threaded open source group chat with apps for every major platform

These mentor organizations are hard at work creating thousands of tasks for students to work on, including code, documentation, user interface, quality assurance, outreach, research and training tasks. The contest officially starts for students on Tuesday, November 28th at 9:00am PST.

You can learn more about Google Code-in on the contest site where you’ll find Contest Rules, Frequently Asked Questions and Important Dates. There you’ll also find flyers and other helpful information including the Getting Started Guide. Our discussion mailing list is a great way to talk with other students, mentors and organization administrators about the contest.

By Josh Simmons, Google Open Source

Rajat Talesra brings Applied CS with Android to Dhirubhai Ambani Institute of Information and Communication Technology

Today we get the chance to hear from Rajat Talesra, an entrepreneur and outstanding Applied CS with Android facilitator who studied Information and Communication Technology at Dhirubhai Ambani Institute, Gandhinagar from 2012 to 2016. Through his work with Applied CS, he’s trained over 900 students across 13 universities to build simple Android games with important CS concepts.

IMG_20170624_155538.jpg

Can you tell us a bit about yourself?
I’m an enthusiastic entrepreneur, Android application developer, and passionate teacher. In my first two years, I did volunteer work for various clubs and committees during college festivals and also organized and managed events in technical and annual festivals.

How did you get interested in Android/mobile development in the first place?
After completing two years of  technical studies in college, I started learning Android application development. I started with online video lectures, and after that, I tried to create one simple Aptitude-based Android application, which was finally uploaded to the Google Play Store. By the end of my third year, I had worked for two different startups as an Android developer. Through this experience, I was able to create some applications on the side, conducted events, and managed a technical festival for our college. I also participated in a good number of competitions and hackathons at my school, which was great exposure to Android technology.

How did you hear about Applied CS and why did you want to participate as a facilitator?
In my third year of university, with the help of the IEEE student branch, the local Google Developer Groups (GDGs), and my enrollment in Udacity Android courses, I was involved not just in learning how to build Android applications, but teaching and supporting other university students learning how to program for Android. Because of this Android and teaching experience, I was nominated to be a facilitator for the Applied CS program.

What are some of the things you learned as a facilitator?
First is that you’re inevitably going to make mistakes, and that’s OK! You don’t have to be an expert, and there are no illusions that you have all the answers. During the first workshop I facilitated, I misspoke a couple of times and had some errors in the code I was writing on the board to demonstrate the functions and app to the participants. Despite those errors at the beginning, the most important part was to be available to help address any and all doubts from every participant during the workshop, troubleshooting and working alongside them, and navigating through any errors or bugs together. This was most important to the participants— that I be flexible and available to help out.

Second, I learned to prepare! I’d also recommend to facilitators to take some additional time to prep—in the two weeks beforehand, I took a look over the materials and the content to strengthen my basic understanding.

Lastly, facilitating this program helped me realize that teaching technology was a passion, and I wanted to take on more of these initiatives on my own. I ended up not joining a company when I got selected for industry placement, but instead, I started teaching Android to various groups and also started working on my initial ideas for some products.

What was the most challenging part of being an Applied CS facilitator?
I quickly realized that reviewing all the required concepts for the program was helpful, but not the most important part of running successful workshops. Even after reviewing the technical concepts we’d be covering, I realized that figuring out the best way to explain them to other students was the more important piece. I started creating different kinds of materials— presentations, some pseudo code, sketches to visualize concepts on board. The most successful resource was comparing the visualizations with the code.

Now, the Applied CS technical unit videos help take off a large amount of the pressure to explain, but I’d still recommend knowing what you will demo or say to introduce the workshop.

What do you think was your greatest success as an Applied CS facilitator?
Since becoming a facilitator, I’ve brought the program to over five universities and hundreds of new students, and been offered opportunities to guest lecture about Android, which is all awesome. But in addition to that, it feels good to see others I’ve worked with benefit from the knowledge and pay it forward through teaching others themselves. Student volunteers who helped me run the workshops have now become facilitators, and it feels great to see them grow and teach others.

Lastly, my love for Android and teaching/facilitating helped inspire my career. I’ve started to create a mobile app that can help teachers mark student attendance in classrooms. And facilitating has opened doors for me to teach Android more formally. I started my own ‘AndroidMonk’ tutorial service, where I have trained even more students and even employees at companies!

What would be your biggest piece of advice to anyone who wants to bring the Applied CS program to their university?

Don’t try to take on the world by yourself. As a facilitator, reach out to friends and other students who are passionate and excited about Android and computer science education to help you out as volunteers or co-facilitators in the workshops. Create one small and strong team to conduct workshops, and then the results will be great. Also, always feel free to reach other facilitators to know what they are doing at their universities.