Co-op Stories: Roan Farsab

By: Roan Farsab

Roan Farsab, a junior in the Electrical Engineering program at Wentworth, completed her optional co-op at California State Polytechnic University, Pomona. She discussed her role with CO-OPS + CAREERS and shared advice for students looking to complete a research co-op:

Roan Farsab Headshot

  • What drew you to finding a research co-op?

In the future I plan on attending Graduate school. My Research Co-op taught me more about grad school and the process of applying. I was also able to learn more about what I can do with my degree. After completing this co-op I learned a lot about UAV technologies and plan on working with them in the future.

  • What was your search and interview process like?

My main search process was the National science foundation website. This website showed all of the research positions that are funded by the National science foundation.

  • What is a typical day like at your co-op?

There isn’t really a typical day as we work on different tasks each day. While one day I could be researching on how to set up a sensor and program it for the drone, the other day I could be coding in python or welding parts of the drone. This is one of the reasons why I enjoyed my co-op; I was exposed to different things other than my major and learned something new every day. 

  • While on co-op, what project(s) have you been a part of that inspired you? 

I worked on a project with a group of two other students. We worked together building a drone on the subject of Autonomous Search and Rescue Vehicles. This drone was designed to work in times of human distress and disaster and to minimize the loss of life. Increasingly, safety and risk prevention has been valued, and the deployment of human rescuers into dangerous and high-risk areas to perform SAR missions is one field where safety and risk prevention can be improved. This inspired me because it showed me how our technologies today can be used during times of disaster to save lives.

  • What advice do you have for students interested in pursuing research for their co-op?

I advise students to be patient. Looking for a research co-op isn’t easy and often may be a very stressful process. People all over the country apply for research positions so don’t be discouraged if you don’t get in to one or the one you wanted. Also, during your research sometimes you will feel that you aren’t learning because you searching for results for something or working on something that didn’t make progress so remember failure is a result that you can learn from your mistakes.

Thank you for sharing your experience with us, Roan! Be on the lookout for our next co-op feature. If you would like to share your co-op experience with us (positive or not-as-expected), or have any questions about the co-op process, please email us at coopsandcareers@wit.edu.

As always, to make an appointment with your CO-OP + CAREER Advisor call the front desk at 617.989.4101 or stop by the CO-OPS + CAREERS Office.

How to Ace a Phone Interview

By: STEAM Boston Writing Team

This article was originally posted to STEAM Boston. Read the full story here: https://www.steamboston.com/how-to-ace-a-phone-interview/

A phone interview is how many companies start the interview process. The interviewer will typically discuss the position requirements and attempt to gauge your interest in the position. Though a phone interview seems like low stakes on the surface, it’s actually your first point of contact with the company– and first impressions are everything.

Phone interviews are typically scheduled in advance, but there are some cases when a recruiter might give you a surprise call. Always be ready to answer the phone in a professional tone and have a voicemail is professional as well. If you’re caught off guard by a call, set a later time to chat when you can get to a quieter place (whether it be 15 minutes or later that week).

Woman at table with tablet

Ask questions and do research

Prior to your phone interview, there are a handful of things you should be able to talk about with confidence. First, you should be able to articulate a clear understanding of the position. If you can’t, write down some questions to ask during your phone interview to clear things up. Second, check how your resume matches up with the position requirements. Make notes in areas that the interviewer might ask you about. And third, be ready to talk about yourself. The interviewer will likely ask what makes you interested in the position and how you’ve learned from your previous experiences. Be ready to talk about how your past experience and future goals make you a good candidate.

Keep your notes handy

The great news about a phone interview is that no one can see you, so you can refer to notes during the conversation. Keep your resume, cover letter, and the job description handy so you don’t have to recite them off the top of your head. You should also take notes during the interview to help you stay on track. Plus, they’ll be something to refer back to if you move on to an in-person interview.

Remember to articulate

However, being behind the phone is a double-edged sword. While your interviewer can’t see your notes, they also can’t see the hand gestures or facial expressions that help you communicate. It’s important to be articulate during your phone interview and maintain a friendly yet professional tone. Smiling while you speak can help you project a more positive image. And for some people, it helps to dress up and sit in a mirror during the call to mimic a face-to-face interview. You should also keep a glass of water nearby if your throat runs dry.

Plan, Practice, and Prepare

Phone interviews can be nerve-wracking, but they’re a great opportunity for you to get your foot in the door. The key is to prepare, listen closely, and be polite. A follow-up email thanking the interviewer for their time never hurts either. Be sure to mention a few details from the conversation. In the end, preparing for a phone interview isn’t that different from an in-person one. With a little confidence and a lot of preparation, you’ll be in the second round in no time.


If you are a student or professional in the “Science, Technology, Engineering, Arts, and Mathematics” field and you want to tell us your story email stories@steamboston.com or tweet @steamboston and let’s talk.

STEAM Boston helps students in the Greater Boston area with career exploration and career advice, check them out at steamboston.com

7 Questions to Ask in a Software Engineering Interview to Figure Out If It’s the Right Fit

By: Joy Ebertz

This article was originally posted by The Muse. Read the full story here: https://www.themuse.com/advice/software-engineer-questions-to-ask-interview-find-the-right-fit

When you’re looking for a new job, it’s obvious that the company is interviewing you. It can be harder to remember that you’re also interviewing the company to see if the role, the team, and the organization as a whole are the right fit for you. After all, the last thing you want is to spend a couple of years stuck in a job you wish you’d never taken.

And you can and should be picky: As an engineer, you have skills that are in high demand. It seems like everyone in the tech industry is hiring—and software is expanding into many other industries, too. That’s all the more reason to make sure you’re screening and evaluating companies based on fit.

But how do you actually do that? If you’re a programmer embarking on a job search, what questions should you ask to figure out if a company and role are a good fit? As a senior staff software engineer who has also spent some time as a hiring manager and interviewed many times on both side of the fence, I’ve given some thought to it.

While the exact qualities you’re prioritizing and looking for will vary depending on what you value and on your working style, there are a few questions that can be especially revealing.

  1. What Does the Team Look Like?
  2. What Are Your Expectations for the Person in This Role?
  3. What’s Your Tech Stack and What Development Tools Do You Use?
  4. How Are Design Decisions Made? And If There Are Conflicts, How Are Those Conflicts Resolved?
  5. How Are Projects Prioritized and Planned?
  6. What Are the Biggest Challenges Facing Your Team?
  7. What Is Your Diversity and Inclusion Strategy?

1. What Does the Team Look Like?

Because you’ll be working most closely with your team, those people will have the biggest impact on your experience at the company. So you’ll probably want to have a sense of what the team looks like. How many people are there? What are their roles? How do they interact? Some people thrive on larger teams while others do best on much smaller teams; some people like the context that working closely with people on other teams brings while others find it more distracting than helpful.

Asking about the size and structure of your potential team and learning about its day-to-day functioning can tell you something about how cross-collaborative the team is, what the seniority of its members is, and how job responsibilities are distributed. Does the team work a lot with product management or NOC (the network operations center)? Are those functions considered to be part of the team? Is there a separate Ops team or is the team practicing devOps? Does the team have insight into customer concerns or input into product features? How is the manager involved with the team? Are there senior team members to learn from or junior people to mentor?

There’s a lot to unpack here, but the answers can reveal whether there are opportunities to learn the things you want to learn—such as how to keep a server running or how to run a usability test—and they can give you a sense of what the team dynamic will be.

You may have a very clear image of what you’re looking for in a team, but if you’re struggling to figure out exactly what’s important to you, think about past experiences and what you loved or found frustrating about them. The patterns you see will help you identify your priorities.

2. What Are Your Expectations for the Person in This Role?

While this can reveal interesting information at any level and for any kind of role, it’s especially important for higher-level engineers. Entry-level software positions typically look similar across companies and titles and bands are consistent. However, at higher levels, there tends to be a lot more variation.

For example, a senior staff software engineer job at two different companies can come with completely different sets of expectations. When I was recently interviewing for roles with this title, I found that some companies expected me to be on a small scrum team and spend all of my time coding while others expected me to spend a large percentage (in at least one case, more than half) of my time mentoring, speaking, or working cross-functionally. Some hoped to leverage particular knowledge I already had while others wanted to leverage more general design thinking or leadership experience. None of these are bad, but they might not be what you’re looking for.

It’s also important to find out if a company will offer growth opportunities in the areas you want to focus on. For example, if they want you to leverage your deep knowledge of Java but you want to learn a new programming language, you’re going to have problems. If, however, they want to leverage your knowledge of API design while still allowing you to learn a new language, that might be a good fit.

3. What’s Your Tech Stack and What Development Tools Do You Use?

Many engineers care a lot about the tech stack they work in and the tools they’ll be using. If you’re one of them, you should definitely ask this question and make sure the answers align with your preferences. I’ve personally never cared too much about the exact languages or development tools a company uses, but I still find them useful to ask about because these questions can also reveal the company’s approach to code and projects more broadly.

For example, when I was interviewing recently, I discovered that one of the companies I was talking to was using a cutting-edge programming language. Using brand-new technologies can be an opportunity to become an expert and help shape the direction that technology takes industry-wide. However, it can also mean surprise bugs that take weeks or months to unearth and a lack of community support.

What development tools a company is using can also be informative. Are they picking best of breed or cheaper alternatives? Are they trying to build everything in-house? Are they missing key elements? For example, do they seem to skimp on or lack monitoring tools? If they aren’t following industry best practices, that might be a red flag—or you could see it as an opportunity for you to introduce those practices. Influencing an engineering culture in a positive way is often a good way to get promoted, but it can also be a lot of work, or in some cases, an unwinnable battle.

Natalia Vinnik, Senior Engineering Manager at Google, likes to ask specifically about code review tools. She’s not tied to a specific tool, but rather she’s trying to see if there’s a culture around code and design reviews. First of all, is there a code review tool? And do they gate production changes?

“It tells a lot about eng culture,” she says. For example, it can tell you “if people are open to get feedback from each other or if it’s more about implementation and [code] doesn’t matter as long as it works.” Companies that have a strong culture of feedback on code are often more open to feedback in other areas.

4. How Are Design Decisions Made? And If There Are Conflicts, How Are Those Conflicts Resolved?

Some companies are very collaborative and others are very hierarchical; some have strict processes and others are more fluid. Asking about design decisions is a great way to learn which ways a company leans. Plus, design discussions are one of the places where conflict is most likely to arise, so understanding how those conflicts are resolved can help you get a sense of the overall working style at an organization.

Does the team plan designs in collaborative sessions or does one engineer go off and write a design document? Who is in charge of various designs? Is it always a single tech lead or is responsibility shared, with different team members playing the lead role for different projects? Is feedback discussed in group meetings, one-on-one sessions, emails, or not at all? (It can be a problem if there’s no chance to give feedback.) If there are disagreements, does the lead engineer make the decision or the manager or the group with a vote?

If you’re like me, one of the things you like most about software is having a say in design and other technical decisions, which may not be a possibility if you’re more junior and the company is very hierarchical. However, the other extreme can be a red flag too—I’ve seen companies where very little gets done because the culture is so collaborative that you need to get everyone to agree on each little detail before moving forward.

There’s no correct answer here, just one that appeals to your preferences. The exact balance that works best for you may depend on how much you enjoy being involved in design in the first place, how much structure and instruction you prefer, how willing you are to speak up and voice your opinion, and how adept you are at influencing others.

5. How Are Projects Prioritized and Planned?

Understanding how a company picks which projects to put its resources toward and how it goes about bringing those projects to fruition can tell you a lot about what’s important there—both in terms of products and in terms of engineering values. For example, is the company prioritizing tech debt or only focusing on new features? Are they able to focus on doing a few things well or do they try to do a little bit of everything? Are they building things to last or are they over-engineering?

But that’s not the only reason to ask this question. The answer can also indicate how much influence you, as an individual engineer, might have. If you have a great idea, what would it take to make it a reality? Is there a lot of red tape or would you have a good amount of freedom to test things out? If they mention holding hackathons and actually implementing features inspired by hacks, for example, it can indicate an openness to ideas coming from anywhere.

This question can also give good insight into how nimble and fast moving the company really is. Every software company I’ve ever talked to has claimed to practice Agile (almost all Scrum). However, some of them are actually mostly using the Waterfall methodology with a facade of Agile. Some people thrive better in a truly Agile environment where they are constantly making adjustments and pivoting, but others do better with more predictability and longer time horizons. Digging into what processes actually look like—rather than going solely by terminology that may not reflect reality—can ensure that you find the right fit for you.

6. What Are the Biggest Challenges Facing Your Team?

I like to leave this question open-ended since I think it’s interesting to see if people pick something technical, cultural, or process related. Regardless, the answer can tell you a lot about team culture and can give you insight into what you might be working on.

Are the challenges they bring up something you’re excited to try to fix or at least willing to work with? Samantha Paras, Engineering Tech Lead at DataFox, also likes to ask this to gauge if one of the challenges mentioned is an area that she feels like she can contribute to. Knowing that she can make an impact makes her much more excited about a company.

Are there challenges? If a team isn’t trying to improve anything, that can indicate apathy or little room for growth on the team. Does everyone on the team reference the same challenge? Consistency can mean good self-awareness across the team (or alternately, a serious problem). Do they seem optimistic about finding a solution?

When I was interviewing at one company, every single person I talked to referenced their design and decision making process being cumbersome and slow. While I obviously wouldn’t want to deal with that, the fact that everyone noticed the problem and wanted it fixed made it seem likely to be addressed quickly. Several of them also referenced discussions they were already having around changing that process.

A good follow-up question might be, “How easy is it to make changes?” or “How empowered do you feel to solve that challenge?” Too much change can be bad, but it’s also a bad sign if it’s impossible to course correct or confront challenges.

Vinnik likes to ask a slightly different question: “What keeps you up at night?” But she’s looking for the same sort of information. “I like to know what real technical and [organizational] challenges the company faces and how they think about [them]. I look for transparency and how they approach challenges,” she says. “If they only talk about working a lot and being paged a lot without thinking about fundamental changes that can help, it’s a red flag. If they say there are no challenges or something vague it’s a yellow flag.”

7. What Is Your Diversity and Inclusion Strategy?

The tech industry (and software engineering in particular) really struggles with diversity and inclusion—despite the fact that research has shown that diversity improves performance.

Paras always wants to make sure that a company isn’t just looking to hire a diverse group, which is often the easier and more obvious thing, but is also working to make their culture more inclusive. Inclusion efforts might mean supporting employee resource groups, educating leaders, and fostering company values around celebrating differences. Paras also points out that with diversity and inclusion, grassroots efforts alone aren’t enough, so it’s important to find out if and how leadership supports the efforts.

You’d be hard-pressed to find a software company with perfect diversity numbers, so you’re not necessarily looking for them to have everything figured out. Instead, you’re trying to gauge how they respond to a longstanding problem, if they’re even willing to admit they have one. I find it extremely telling to see if a company tries to put a positive spin on something negative or if they admit they have work to do. I also like to see how much thought and effort they’ve put toward doing better. Are they trying creative solutions? Are they using data to inform their efforts? Are they actually working to fix the issue or are they complacent and giving excuses? (Read more about how to tell if a company’s walking the walk on diversity and inclusion here.)

The answer might tell you more about the company than just its D&I strategy. How a company approaches this very challenging problem can be indicative of how they approach other complicated issues and how transparent they tend to be. Do they face obstacles head-on and strive for constant improvement even when it’s hard or do they just push things under the rug?

With most of these questions, there isn’t a general right or wrong answer. It’s all about finding the place that sounds perfect to you. Do you thrive with consistency or chaos? Do you work well under pressure or do you shut down? Do you get excited about working with brand-new technologies or do you get tired even contemplating it?

Almost every company you’ll talk to leaves at least five minutes at the end of each interview for you to ask any questions you have. Use that time wisely. Your job is a big part of your life, so it’s worth taking the time to ensure the one you’re accepting is the best possible fit for you.

CO-OP + CAREER Fair Event Recap

By: Abbey Pober

Our annual Fall CO-OP + CAREER Fair was held on Tuesday, October 2nd from 3:00 pm – 6:00 pm in Tansey Gymnasium. The event hosted 180 employers ranging from local design firms to international technology organizations and everything in between. It was our most well attended Fair to date, drawing 875 students from all majors, seeking both co-op and full-time opportunities. Students came prepared to spend the afternoon learning and making new connections.

Fall Career Fair

Students who attended the CO-OP + CAREER Fair, below are some tips for following up. If you had a LinkedIn photo taken, look for an email from coopsandcareers@wit.edu in about a month.

  • Send a thank you email to the employers with whom you spoke. Find our guide to thank you notes here. If you need a reminder of which companies with whom you spoke a list of employers is available on our website for reference. Use this opportunity to include a copy of your resume, even if you gave them one at the Fair.
  • If a recruiter gave you specific instructions, be sure to follow through on those items and then follow up with the recruiter.
  • Unable to send a thank-you note for lack of contact information? Stay connected through social media: find the company or even the person you spoke with on LinkedIn or Twitter. Follow their feeds to stay up to date on new openings and other news!
  • You are always welcome to check in with your Co-op + Career Advisor to see if they can provide you with any helpful information, too.

Fall Career Fair Booths

If you were unable to attend the Fair be on the lookout for future opportunities to connect with employers, including the announcement about the spring CO-OP + CAREER Fair. Our next event is Mock Interview Day, on October 22nd , and student registration is now open on WITworks. This is a great opportunity to practice your interview skills and get feedback directly from employers.

Employers, be on the lookout for future recruiting opportunities in the coming months, and for details about our spring CO-OP + CAREER Fair. Interested in participating in Mock Interview Day? Register for this free event through your WITworks account or by contacting Chris McIntyre, mintyrec@wit.edu.

Thank you to everyone who joined on October 2nd for the Fair. A special thank you to our sponsors: BOND BrothersCommodore BuildersDACONElectric Supply Center, NOVO Construction, Schneider Electric, and TG Gallagher. Your support makes all the difference.

 

We look forward to seeing everyone at our next event!

What Jobs Can I Get With a Major in Computer Information Systems?

By: STEAM Boston Team

Computer Information Systems (CIS) is a growing Information Technology (IT) discipline that is getting a lot of attention nowadays. There is plenty of entry-level jobs for Computer Information Systems graduates. It also has an excellent long-term outlook. For example, the demand for Computer and Information Systems Managers is supposed to grow 12 percent between 2016-2026. That’s a faster growth rate than the average for all occupations. So, a CIS degree can offer you a high-earning, satisfying long-term career.

CIS – Understanding the Business of Technology

Computer with glasses in front

Computer technology is a vast field with many disciplines and sub-disciplines. So students often struggle to understand what a Computer Information Systems degree means for them. Also, it’s easy to confuse Computer Science and Computer Information Systems degrees.

A Computer Science (CS) degree is intended for students who want to pursue hardcore computer programming. It teaches you how to build software. The emphasis is on math and problem-solving for software creation. However, in real-world environments, most companies don’t develop their software. They purchase ready-made applications from vendors and then customize them for their business requirements. The business of choosing the right software and customization requires less computer programming skills and more understanding of business needs. Computer Information Systems curriculums are designed to teach students how to use the right technology effectively for businesses.

In a Computer Information Systems major, you will learn about topics like system analysis, information architecture, information organization and management, and business consulting. You will be able to help businesses choose the right technology.

Types of Entry-Level Jobs You Can Get

A CIS major opens up many job options for you. Here are some entry-level jobs for Computer Information Systems (CIS) graduates:

Technical Support Specialist or Help Desk – Technical support specialists help users with software and hardware problems. You will assist customers with your technical know-how. You will use both your customer service skills and computer knowledge to solve everyday problems. The median income is around $49,595.

Business/Systems Analyst or Consultant – As a business/systems analyst, you’ll look at a company’s current operations and help them implement new systems or improve the current ones. The median income of a business/systems analyst is around $68,146.

Network/System Administrator – Network/system administrators are responsible for the implementation, management, and maintenance of the network infrastructure of a business. It requires both hardware and software knowledge. Network administrator median salary is around $57,747.

Database Administrator – Database administrators look after the design and maintenance of database systems. It requires an understanding of databases and how to protect data through backups and redundancies. The median salary for database administrators is around $71,833.

Web Developer or Programmer – Web developers help businesses with their websites. A web developer’s responsibilities include gathering business requirements, designing websites, implementing solutions and maintaining already running websites. Depending on your interest, you can work on the design side or the programming side of web development. The median salary for a web developer is around $58,483.

Educational Opportunities in the Greater Boston Area

The greater Boston area has lots of great colleges and universities that have CIS majors. Institutions like Wentworth Institute of TechnologyNortheastern UniversityBentley UniversityUniversity of Massachusetts – Boston and more provide excellent Computer Information Systems (CIS) degrees to start your career.

References:

Interested in joining the STEAM Boston Community, then visit this link: https://community.steamboston.com/

You will have the opportunity to expand your network and connect with students & professionals in the STEAM field in the Greater Boston area.

This story was originally posted on STEAM Boston’s blog site. Original story here: https://www.steamboston.com/what-jobs-can-i-get-with-a-major-in-computer-information-systems/

From Co-op to Commencement

By: Abbey Pober

When he first discovered his passion for software engineering Ethan Arrowood never thought he’d be turning down opportunities to interview with Google and Twitter to accept a co-op offer from Microsoft. Across his back-to-back co-ops, Ethan gained experience as a software engineer and worked with groundbreaking technologies to deliver innovative cloud-computing applications to leading Microsoft clients around the world. His key to success as a growing programmer? Getting involved with opensource and finding a developer community that supported him. On campus, Ethan’s active involvement with Accelerate is what led to his interview, co-op, and ultimately a full-time role with Microsoft.

Our Spring 2019 Intern, Lauren Rodolakis, spent the semester learning all about Ethan’s journey from co-op search to accepting his full-time offer at Microsoft. Read the full article on the Wentworth website, and check out our video interview here.

Arrowood at MicrosoftThank you for sharing your experience with us, Ethan! Be on the lookout for our next co-op feature. If you would like to share your co-op experience (positive or not-as-expected), or have any questions about the co-op process, please email us at coopsandcareers@wit.edu.

As always, to make an appointment with your Co-op + Career Advisor call the front desk at 617.989.4101 or stop by the CO-OPS + CAREERS Office.

Co-op Stories: Jasmine Andrade

By: Jasmine Andrade

Jasmine is a Wentworth Junior studying Interdisciplinary Engineering concentrating in Manufacturing Engineering and minoring in Industrial Design & Business Management, with a concentration in Project Management. She recently completed her second co-op at Amazon Robotics (AR) as the Technical Operations Co-op, Process Engineer. Jasmine generously shared her story with us:

Jasmine at Amazon Robotics

Her career goal is to become a Product Design Engineer or Innovation and Design Engineer, so she chose this combination of concentrations and minors to make her a well-rounded engineer and to meet her career goal.

“In a Product Design Engineer role, it is important to have skills in Design/Innovation (Industrial Design Minor), Research & Development (Interdisciplinary Engineering) and Manufacturing/Process/Industrial Engineering (Manufacturing Engineering Concentration). You must also have the ability for negotiating and communicating with internal and external business partners, contractors and vendors (Business Management minor). The variety of knowledge and perspectives that my concentration and minor provides allows me to continuously look at a problem through a multidisciplinary lens.”

  • Tell us about your second co-op at Amazon Robotics: 

The Technical Operations Co-op is responsible for delivering and supporting operations and production projects by collaborating with Amazon Robotics Tech Ops Engineering process owners and other cross-functional team members.

  • What interested you in this company/the role?

The culture of Amazon, the peculiar and eccentric ways of sustaining their mission to being “earth’s most customer-centric company for four primary customer sets: consumers, sellers, enterprises, and content creators” is what stood out. Amazon gives you the freedom to think a little differently and to embrace differences. Amazon works to avoid being bland, “big homogeneous, corporate Borg” and aims to stay transparent in what the company needs to continuously work on and improve.

The role stood out because it was different from the my previous role as a Surface Mount Technology (SMT) Manufacturing Engineer at Raytheon IDS, the Process Engineering positions would provide me with a new skillset and also build on what I learned as an SMT Engineer. The position description also starts with “Are you inspired by invention? Is problem solving through teamwork in your DNA? Do you like the idea of seeing how your work impacts the bigger picture? Answer yes to any of these and you’ll fit right in here at Amazon Robotics (AR). We are a smart team of doers that work passionately to apply cutting edge advances in robotics and software to solve real-world challenges that will transform our customers’ experiences in ways we can’t even image yet. We invent new improvements every day. We are Amazon Robotics and we will give you the tools and support you need to invent with us in ways that are rewarding, fulfilling and fun.” The statement provided before you even look at the position description draws you into the possibilities and potential with AR.

  • What was your search process like? And how did you prepare for your interviews?

My search process included applying to 30+ co-op positions that fit my interest and skill set. I also reached out to my LinkedIn network for positions that I was interested in. I utilized the CO-OPS + CAREERS interviews questions list and wrote out all my questions for my on the phone interview for reference. For the in person interview, Amazon provided an outline for potential questions and the format for how they “grade” or determine if you fit culture and position. I wrote out all those questions and practiced answering them out-loud by myself and did a practice interview with friends.

  • While on co-op, what project(s) were you a part of, or something that you worked on, that has inspired you? 

One of the project I had the pleasure to work on was for “a new, fully-electric delivery system – Amazon Scout – designed to safely get packages to customers using autonomous delivery devices” (https://blog.aboutamazon.com/transportation/meet-scout). I worked on preparing work instructions and set up for the alpha build. Through this process I was able to see how important the Process Engineering and Technical Operation is to Amazon and how we function cross- functionally with other divisions in Amazon to sustain the mission of being a customer-centric company. This project encouraged me to “Think Big”, “Insist on the Highest Standards” and to “Deliver Results”. These principles are something that stood out within this project and motivated me to continue to develop these skills in the projects that followed.

  • Knowing what you know now, how will you approach your Fall co-op/co-op search differently?

My approach to applying for fall co-op is to find/apply for positions that I see myself transitioning into a full time role. In addition, look at the company culture, history and mission. I am differently more picky in selecting co-ops this semester because I want to make sure I am applying to a companies that I see myself at, long-term and will provide me what the skills I need to acquire to meet my career goal of being a Product Design Engineer.

  • What advice do you have for students who are interested in working for a company like Amazon Robotics?

Go for it! Don’t be afraid to be yourself in your interview, embrace your experiences and peculiar ways to engineering and design thinking. Learn and be curious about everything, commit to being a life-long learner and dive deep into understanding the problem before seeking a solution. Also, remember who your customer is and how your idea or solution will benefit them.

Thank you for sharing your experience with us, Jasmine! Be on the lookout for our next co-op feature. If you would like to share your co-op experience (positive or not-as-expected), or have any questions about the co-op process, please email us at coopsandcareers@wit.edu.

As always, to make an appointment with your Co-op + Career Advisor call the front desk at 617.989.4101 or stop by the CO-OPS + CAREERS Office.

Summer 2019 Drop-In Hours: Wednesday and Thursday 2:00pm – 4:00pm while classes are in session.

Co-op Stories: Joey Cordeiro

By: Joey Cordeiro

Joey Cordeiro is a Junior in the Electrical Engineering program at Wentworth. He completed his first co-op with Naval Undersea Warfare Center (NUWC) in Newport, RI as a Student Trainee/Torpedo Systems Engineer. Joey recently sat down with CO-OPS + CAREERS to share his co-op story.

Student on Naval Base

Tell us about your first co-op:

I worked in the Systems Integration and Test Branch in the Undersea Weapons, Vehicles, and Defensive Systems Department. My role was to support the build and programming of a test set for an electronics assembly used in a weapon system. I worked under and was mentored by several experienced electrical and computer engineers. I had already completed a summer internship with NUWC last summer.

What interested you in NUWC?

Working for a defensive and weapons company has sparked my interest for a few years now. I always knew that if I got into this line of engineering then it would be a very satisfying job, and I would be working on something that has an impact on today’s world.

Applying for a role with the Navy, were there extra steps you needed to take?

The application process was like most other engineering internships, including submission of a lengthy application, resume, and doing a few initial phone interviews. The process became much more involved once an offer was made and I accepted. The process of acquiring the required security clearance to work this government job was a lengthy one at that. The procedure was well worth it looking back; getting the great opportunity to work for a strong Navy operation such as NUWC.

What was a typical day like at your co-op?

I normally spend my mornings reading torpedo specification documents and reading up on the hardware that I would be working with. There is an abundance of information and aspects of undersea weapons to learn about. The rich history of the vigorous engineering and years of hard work that has gotten NUWC to where it is today is truly what gets me excited to come to work every morning. I would typically spend all of my afternoon in the labs with my project team members working on the various tasks of our project. This spring co-op, I spent a majority of my time building a test set for the electronics assembly being programmed for the torpedo.

You are completing your second co-op with the Naval Undersea Warfare Center. What has changed between your first co-op and your current?

I, along with my co-workers and managers, had more confidence in me to give me more responsibility and work load. I was able to work on multiple aspects of my electronics assembly program. On my first co-op I spent a lot of time working on specification documents, and revising and updated them to Navy standards. This time around, I was able to complete more hands-on work involving design, fabrication, and testing of a torpedo test-set.

Why did you choose to return for a second co-op with your employer? What advice do you have for students who are interested in returning to their first co-op employer?

I returned to NUWC for this co-op for many reasons. One of the main reasons is because of the satisfaction I got from working for the Navy. Seeing the great things we do as a 3000-person team here at NUWC, it was a no-brainer for me to return. A lot of it also had to do with my knowledge of defense systems as a whole. I learned a lot on my first internship, but I wanted to learn more and I felt that another 4-month co-op would do just that. I wanted to learn as much as possible about undersea warfare and what it feels like to serve the Navy fleet every day.

Thank you for sharing your experience with us, Joey! Be on the lookout for our next co-op feature. If you would like to share your co-op experience (positive or not-as-expected), or have any questions about the co-op process, please email us at coopsandcareers@wit.edu.

As always, to make an appointment with your Co-op + Career Advisor call the front desk at 617.989.4101 or stop by the CO-OPS + CAREERS Office.

Summer 2019 Drop-In Hours: Wednesday and Thursday 2:00pm – 4:00pm while classes are in session.

How to secure your dream co-op

By: Austin Hoag

Austin Hoag is a Wentworth Junior studying Construction Management and serves as the CM Club Operations Manager. One of the many duties assigned to Austin as Operations Manager includes writing content for their website. Here is what he shared about his co-op search and areas where he was successful:

To secure your dream co-op, you will need…

  • A Polished Resume
    •  At this point, between being a student in the #1 Construction Management Program in the country among non-traditional students and having the credentials to be accepted into Wentworth, all students have the ability to create a competitive resume. If you haven’t already, I highly recommend sitting down with Janel Juba, Co-op + Career Advisor for Construction Management and Civil Engineering majors to create a resume employers will love. Besides, the hard part is done, now it is time to take advantage of and showcase your accomplishments!

Search image

  • A Nice Padfolio
    • While this one might seem small, having something more organized than a pile of papers such as a Wentworth branded padfolio while meeting possible employers can go a very long way. Remember that these people will depend on you to be a positive representative of their company, and appearance is a large part of that.  *If you completed Co-op Institute, you will have received a padfolio at the end of the course. If your free Co-op Institute padfolio has gone missing, CO-OPS + CAREERS always has a few on-hand to borrow.
  • Attend CO-OP + CAREER Fair
    • The job fair that is offered twice a year (fall/spring) is, without a doubt, the BEST way to meet employers. The people you meet at the booth offer a unique look into the company and can help to give you an idea of the company culture.
  • A solid idea of what you want out of your co-op
    • One of the first questions almost every employer will ask you is: “what kind of position you would want if you were hired?”. If you know what that is, it can also help you narrow down your searches.

What to bring for your in-person interview…

  • Copies of your resume
    • Although they most likely will already have your resume, one of the biggest mistakes you can make is forgetting to bring it. Having it printed on resume paper shows that you are organized, forward thinking, and excited about the opportunity to interview.
  • Padfolio and or Notepad
    • Taking notes during an interview is vital, not only does it make you look more engaged, but taking notes will help you write a meaningful follow up email. *Write a few questions you want to ask and talking points to prep for your interview that will keep you on track.
  • The right attitude
    • An important part of the interview process is gauging each other’s personalities and making a first impression. Having a positive attitude and tone of voice when answering questions and confident body language can make all the difference.

On your first day and during field walks…

  • Office shoes and steel toe boots
    • In construction, you never know where the day might take you, especially your first day. Even though you may have an office job, employers very well may take you on a site for a variety of reasons. Have your gear ready because you will want to be prepared!
  • Plenty of water/food
    • Again, it’s construction, you never will know what the day will bring. On hot days, almost nothing is more dangerous than not having enough water. Food is often forgotten when it’s your first day, you never know what site you will be on, what the demands are and what will be open around you. Trust me, I have been unprepared in this area before.

Construction image

  • A notepad
    • Before my first day, this tip was suggested to me by other employees. One of the most unprofessional things you can do is walk into a meeting empty handed. I was meeting with the president of a subcontractor on my last co-op and I witnessed someone get kicked out of the meeting by their president because they were ill-prepared.
  • Anything that you think you might need
    • If you have a car and think it might come in handy, just bring it. It is always better to have something and not need it than to need it and not have it.

This blog was originally posted here, on the Wentworth CM Club website.

Thank you for sharing your experience and expertise with us, Austin! If you would like to share your co-op experience (positive or not-as-expected), or have any questions about the co-op process, please email us at coopsandcareers@wit.edu.

As always, to make an appointment with your Co-op + Career Advisor call the front desk at 617.989.4101 or stop by the CO-OPS + CAREERS Office.

Summer 2019 Drop-In Hours: Wednesday and Thursday 2:00pm – 4:00pm while classes are in session.

Bridging the Generational Gap in the Workplace

By: Chris McIntyre

At each point in your career– especially on co-op– you will work with colleagues in a variety of age brackets. They’ll be different in almost every way, from communication style to attire to their views on what it means to be a professional. To be successful in any workplace it’s imperative to understand how to navigate these generational differences. Understanding this will lead to greater levels of collaboration and higher levels of productivity – as well as perhaps saving you from embarrassing faux pas.

First, a brief primer on generations (Keep in mind there are no official cut-off points):

Baby Boomer: Those born from 1946-1964

Gen X: Those born from 1965-1979

Gen Y/Millennial: Those born from 1980-2000.

Author Jean Twenge dubbed the next generational bracket (2000-Present) iGen due to growing up with smartphone technology. iGens, who the eldest of the generation are now college-age, have key differences than previous generations at the same age including:

  • Less religious
  • Much more comfortable with technology
  • A tendency to experience life events, such as getting a driver’s license, at a later age
  • Spending less time with friends in person, but always staying connected to them
  • Less likely to have a part-time work experience before entering college

That last point is key when thinking about applying to co-ops. Hiring managers, who probably are from a different generation, may not know a co-op will be some iGens’ first job. So, when putting together your resume, think about the transferable skills employers look for: communication, collaboration, time management, problem solving, etc. It’s important to highlight these skills whether you got them from a school activity, sport or student organization.

Female biting pencil

My work in Employer Relations allows me to interact with individuals spanning all generations. In addition to the importance of transferable skills, another consistent thing I hear is the importance of professional communication. iGens don’t use their smartphones as a telephone, something previous generations have a hard time understanding. Thus, it’s important to spend time working with your advisor to practice professional telephone communication if you’re not comfortable. Often your first-round interview will be a phone screen, so it is vital you feel comfortable.

Working with iPhone

Related to verbal communication, employers frequently emphasize the importance of professional written communication. iGens tend to write in a less formal structure and tone, while other generations are the opposite. So, when writing cover letters and e-mails ensure you are writing in a clear and professional tone (PS – your CO-OP + CAREER Advisor should be reviewing your cover letters and other professional communications).

Don’t overlook the importance of understanding other generations. While it will be necessary on the job, it could even be the difference between getting the job in the first place.

As always, to make an appointment with your Co-op + Career Advisor call the front desk at 617.989.4101 or stop by the CO-OPS + CAREERS Office.

Summer 2019 Drop-In Hours: Wednesday and Thursday 2:00pm – 4:00pm while classes are in session.