Workplace Culture – WITS Happening

April 15, 2020eckmank No Comments

Co-op Stories: Julia Gravano

By: Julia Gravano

Julia Gravano is a Wentworth junior studying Construction Management with a Concentration in Facilities Management and a minor in Business Management. She completed her first mandatory co-op semester this past spring with J. Calnan & Associates, Inc. and shared her experience with CO-OPS + CAREERS:

With J. Calnan & Associates in New York, NY., I served as a Project Coordinator. This position provides support for project management teams throughout the construction process. Through close partnership with team members, as well as clients and subcontractors, the assistant project manager helps to ensure all job-related documentation is up to date. This position works with project managers to monitor the status, details, and finances of each assigned project.

What is a typical day like at your co-op with J. Calnan & Associates, Inc.?

Every day is a different day! One day I could be helping with pre-construction which entails me becoming familiar with the drawings and calling subcontractors who may want to bid on projects. Other days, I am assisting on existing projects dealing with RFI’s, submittals, and miscellaneous project management tasks. In addition, I will walk through potential jobsites that our company may be looking to take on with our Project Manager and Estimator. I look forward to each day because they may seem similar, but I always learn something new. My co-workers and I try to eat at new local restaurants each Friday as well to take a breather from the office.

What is something that you are working on that has inspired you?

The biggest project I have been a part of since the beginning of my co-op is 446 Broadway. It is an entire building totaling of 6 floors (including a cellar). This building is identified as a New York Landmark Building. I have been able to partake in preconstruction and construction activities this far. This has allowed me to forge close relationships with both the Preconstruction and Project Management sectors of our NY branch. I have learned about the different facets a project must undergo when it is identified as a landmark. This project will allow me to see the transformation of a deteriorating old building to becoming new tenant and retail space. I take pride in of all the projects that I touch upon working at J. Calnan. I am grateful that they have taken me in as a co-op with open arms and see my potential by giving me responsibility.

I am also proud to say that I am part of such a compassionate and flexible company that cares about its employees and clients. During this time of Covid-19, JC&A has been proactive about keeping its employees safe and up to date on protocols both in the office and in the field. Though the NY department is smaller the Quincy HQ, we are able to strongly communicate and coordinate accordingly as we work from home.

What did you learn from your first optional co-op that have helped you in this role?

I have learned to have more attention to detail from my first co-op. It provided me with my first experience of interior fit out construction as well as project management experience. My first co-op also allowed me to learn about the dynamic and complicated relationships that owners, architects, and construction managers may have on fast paced projects. Furthermore, I believe my job experience allowed me to be open about asking questions about why things are done and how things are done. I took advantage of the subcontractors and co-workers that loved to explain and talk about what we do on a daily basis.

What advice do you have for female students interested in the Construction Industry?

The biggest piece of advice that I have for females is to not be afraid to ask questions and to be yourself. The thing that I found most challenging is making sure that my voice is heard and proving that it matters. I am not afraid to ask any question whether it be obvious or not. It shows how interested you are and how you are applying knowledge that you have learned on the job or at school. Be a sponge and soak it all in, but most importantly don’t forget to have fun. I am such a high stress person and the biggest thing that I am still learning is to make your moments enjoyable and ones to remember.

What is the biggest lesson you’ve learned through your co-op?

The biggest lesson I have learned is that knowledge is important, but your network it ultimately equal to your net worth. The industry is small wherever you may go, and it is all about who you know. I have found both of my co-ops back home in New York. Without my involvement in industry events and constantly meeting people, I believe that I would not have had the luxury of living at home for co-ops. In general, it is nice and important to hear other industry people’s stories and advice. Be personable, make friends, and forge relationships that will last throughout your career.

Thank you for sharing your experience with us, Julia! 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.

To make an appointment with your CO-OP + CAREER Advisor call the front desk at 617.989.4101 or visit our website for more information about scheduling virtually.

January 22, 2020eckmank No Comments

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?

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.

January 15, 2020eckmank No Comments

Co-op Stories: Jakub Bzura

By: Yunjia Hou

This story was originally published by Wentworth Institute of Technology News. Read the original post: https://wit.edu/news/mechanical-engineering-student-troubleshoots-tesla-on-co-op

Jakub Bzura looks at a Tesla on the road a little differently than most.

“My instinct is to check the panel gaps and look for serial numbers to see if I remember any of them,” he says.

Bzura, a senior Mechanical Engineering student, conducted his first co-op with Tesla in Fremont, California this past spring and he is currently on his second co-op at the Tesla in Reno, Nevada.

As a quality engineer in Fremont, Bzura was asked to find, analyze, and reduce the deviations of different parts of a car that might significantly influence the assembly.

In Reno, he is a battery pack manufacturing engineer, working on designing manufacturing lines.

“I enjoyed quality engineering, but I wanted to try different things,” he says.

At the beginning of his co-op at Tesla, Bzura was challenged by the ambiguous nature of his role. He was given a lot of space to work creatively but sometimes was unsure whether he went about his work in the way the company anticipated.

“At Tesla, people are not necessary going to tell you how to do things. They give you a problem and they want a solution. How you get from A to Z and anything in between, is really up to you,” he says.

Bzura was immediately placed into hands-on projects. He says that he learned from colleagues that “there is no problem too big.”

“A lot of teams that feel like they are understaffed and unequipped can really do amazing things when they put their mind into it,” he says. “That’s quite evident in Tesla.”

With Tesla’s mission to accelerate the world’s transition to sustainable energy, Bzura says working on his projects is “definitely rewarding.”

“When you devote enough time and energy to something it becomes a part of you. When you bring it to completion and you see it’s making a difference in the bigger picture, it feels good,” he says.

Bzura said he never imagined before he could get an offer from Tesla. “It was an awesome day,” he said.

He believed his previous internship experience and the resume improved by his Wentworth co-op advisor helped a lot. During the Tesla interview, he was asked very detailed and technical questions including about different material properties that are associated with the job position.

“They are looking for specific levels of responsibility,” he says. “People who carried through the entire project and stuck to a problem eventually solved it.”

Thank you for sharing your experience with us, Jakub! 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.

July 31, 2019eckmank No Comments

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:

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.

July 1, 2019eckmank No Comments

Adjusting to the Workplace Part 2: Young Alumni Panel

The Real Truth About Adjusting to the Workplace from Recent Wentworth Alumni

By Ria Kalinowski

As part of the 2019 Summer Leopard Lunch & Learn Series, CO-OPS + CAREERS invited four young alumni to campus to give advice about adjusting to the workplace. Our moderator was Janel Juba, Co-op + Career Advisor. The alumni were as follows:

Hayley Patton, 2016 Biomedical Engineering Graduate. Currently working at ZOLL Medical as a Design Quality Assurance Engineer and completed one co-op at the manufacturing center at ZOLL.
Will Ma, 2018 Computer Information Systems Graduate. Works as an IT Service Desk Analyst at Criteo. Also, the CEO and co-founder of “STEAM Boston”. Completed co-ops at Dell/EMC, Brightcove, and EF Education First.
Kasey Cordeiro, 2018 Electrical Engineering Graduate currently working at Starry. Completed two co-ops at Raytheon and worked full-time for them as well post-graduation.
Alyssa Payette, 2016 Biomedical Engineering Graduate working as a clinical applications analyst at Mass General Hospital. Completed one co-op there as well.

Professional Relationships

The alumni shared advice about building professional relationships in the workplace. Two main points that came up were the importance of being confident, so people begin to trust you and figuring out what to share and what not to share:

Hayley: Make sure you have those little boundaries, don’t be too personal, but don’t also be a clam.

Alyssa: In the last 3 years, I got the opportunity to serve in a few different management roles, so I can actually speak to the other side of it as well. So initially kind of like what Hayley was saying, it was a little touch and go trying to find what to share and what not to share. Afraid of it being off putting, you kind of want to blend with the teams you are on. So, you definitely want to share to identify those things you have in common. It can be tricky when you’re worried about crossing lines.

Will: Some advice is to try not to be too personal. Make sure to not cross the line.

Another way that these alumni managed professional relationships, especially with their manager, was by speaking up and asking questions. Having open lines of communication with your manager is important so that your expectations align:

Kasey: Definitely speak up if something is not working for you or if something could work better. I find that a good manager will be open to that kind of feedback. They want your productivity to be as high as it can be and they want you to be comfortable in your work space.

Alyssa: And you have to remember that your managers are trying to accomplish the same goals as you so if you are struggling, my best piece of advice, which I have done, is to set up a meeting to discuss your professional relationship.

Hayley: I’m the type of person who asks a ton of questions…when I first started I was going to [my manager] at least 3 or 4 times a day asking where’s this, how do I do this? But he was super helpful. He also provides information on where to find information on the questions you have. So he also kind of pushes you to find it yourself.

Company Culture

These alumni gained a lot of knowledge about their company’s culture through research, the interview process, and observation:

Will: Basically the first week they can give you an understanding of how the culture is, so what kind of clothes they wear, is it really casual or more professional, is it a 9-5 culture or is it more like a work hard play hard type of culture – there are a lot of factors you can learn from that first week…and also the interview too, when you have an interview one of the questions you should ask is how is the company culture.

Kasey: I actually used WITworks, and on there [saw that] Starry goes to the Career Fair… so I looked at [WITworks] and it said something like company culture or in their dress code maybe and so I looked through those and saw it said very casual… and so I used those to play my interview strategy where I was sort of half business causal but more on the casual side… I think it helps the transition a lot. And then paying attention to how they acted in the interview, and how casual it was, and the way they interacted with each other, that was my strategy.

Alyssa: Like Will said, definitely in your interview ask about the culture, because sometimes you don’t meet with everybody when you go in for an interview… so definitely find out what the specific group you are working with has as far as culture, and then speak up, ask questions, pay attention to your surrounds when you go in for an interview.

Learning from Failures

Making mistakes are an inevitable part of adjusting to a new workplace. The alumni shared how they were able to overcome or learn from these experiences:

Hayley: So I do a lot of testing, and it has to be super attention to detail… one time I was testing one of our new AED products, and I had put in a code for the Wi-Fi, because our device communicates over the internet to the hospital… and it just so happened that the number I put in was [wrong]… you have to make sure that no matter how many times you’ve run through this or how many times you’ve done it, you have to treat it like your first time.

Will: So what I did was I basically wiped out a whole computer, and the employee wasn’t happy… we didn’t really do that much research, and so after the computer was wiped, I had to create a backup plan- how can I prevent this mistake from all the 20 other employees in the whole company from deleting someone’s files, so I made some documentation, and talked about some steps you can take to solve this bug on the computer, and actually a lot of employees are looking at this documentation to this day… overcoming failures makes you grow and turns you into a better employee and turns you into a better person.

To read more about adjusting to the workplace, click here.

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. And be sure to check back next week for Part 2 of Adjusting to the Workplace.

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

June 26, 2019eckmank No Comments

Adjusting to the Workplace Part 1: Advice from an Advisor

By Ria Kalinowski

There are many differences between attending school and starting work at a co-op or job. It can be a bit of a culture shock to make the transition. The schedule is different and expectations are new, so it will take time to make the adjustment. To prepare further, click here to listen to Wentworth Alumni talk about their experience and what advice they have for adjusting to the workplace.

Communication

During your first week, check in with your supervisor about how they like to be communicated with. Maybe they like you to keep a running list of questions and go over them in a weekly meeting. Maybe they would prefer you to pop by their desk whenever something comes up. Maybe they use Slack or Skype for Business. If you have questions or need to call out sick, learn how to ask and when to do it.

Speaking of asking questions, don’t be afraid to do just that! If something comes up that you don’t know or need clarification on, do some research first, and then ask. A good practice is to show that you’ve done the research and are looking for information that can’t be found elsewhere.

Something critical to ask about is expectations. One major aspect of work that is different from school is that at work, you do not receive feedback in the same way. At school, grades are given frequently and without solicitation. You can compare your progress with how you did in past semesters and with how you are doing compared with others. At work, feedback can range from daily check-ins, to weekly meetings, or yearly evaluations. It may be vague or infrequent. When you first start interacting with your supervisor, work with them to set goals that are concrete and measurable, so you know what is expected.

If you aren’t receiving regular feedback from your supervisor, check in with them after the first few weeks to ask how they think you are doing. Ask for suggestions for improvements. It’s better to ask for redirection rather than continue down the wrong path.

2. Relationships

Another big difference between work and school are the people you interact with. In school, you are surrounded by your peers and often, you can pick the professors you learn from. At work, there may be several different generations you are asked to collaborate with and present to. You will have to manage relationships with people you may not get along with or agree with and sometimes, those people may be in a position of power. It’s important to behave as civilly and professionally as possible, as these are people you will see every day. You may also need references from them in the future!

One of the main relationships that you will engage in is the one with your supervisor. During your interactions with them, you may receive negative feedback or constructive criticism. It’s important to take this feedback professionally. Keep in mind that not all supervisors receive extensive management training. While this is a time to be developing your interpersonal skills, your supervisor may be working on their own skills as well. Knowing your strengths and weaknesses while gaining an understanding of the strengths and weaknesses of your supervisor and what motivates them will help you navigate that relationship.

There may be people you adore spending time with at work, as well! It’s awesome to find people at work to be friends. Try not to complain about other work people to them as you never know what can get back to others.

This is a good time to start building a network of professionals to mentor you and help you learn about the industry and professionalism. Mentors can help you navigate company norms, understand hierarchy, and coach you to move up in your career.

3. Accountability

Much of your time at school is spent working independently. At work, often you are part of a team working towards a shared end goal. It’s important that you pull your weight, meet deadlines, and communicate with your teammates. Along with being accountable to a team, you are accountable for showing up every day. One of the biggest issues that leads to co-op termination is students not showing up or consistently showing up late.

Take notes in meetings (not on your phone as this can be misconstrued) and ask for more work when you finish a project. It might even be a good idea to have a list of smaller projects that are not time sensitive to dive into if you finish other work early.

While it’s important to work hard and not sit idle, it’s also important, in a full-time job, to take time off to recharge. Vacations aren’t scheduled for you like they are during school so make sure you take care of your mental health.

4. Success!

The key to being successful so that your job is secure, and might even lead to a promotion, is to make yourself indispensable. Be positive, professional, and proactive!

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.

June 12, 2019eckmank No Comments

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!

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.

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.

May 1, 2019eckmank No Comments

Co-op Stories: Sophia Seltenreich

Sophia Seltenreich is a Wentworth Junior studying Business Management with a minor in International Business. Sophia recently completed her first mandatory co-op with Yesware in Downtown Boston where she worked as a Content Strategy Co-op, which was a hybrid position of content marketing and market analysis. In this role, her tasks included developing cadence and curating content on social channels, establishing perspectives/thought leadership & analyzing data in the area of sales to write about on Yesware’s blog, tracking KPIs for Yesware and competitors to measure growth and success, designing graphics for website and social platforms, and customer outreach for data insights and review generation. Here’s what she shared with us about her experience:

What was it like to work at a start-up like Yesware?

It’s incredible! Every day is so lively and so different. You have a lot of flexibility and independence, but also a lot of responsibility. Given the ever-changing start-up environment, you have to be adaptable and ready to pivot at any time. Personally, I love that aspect of the start-up environment. I also love the work I’m doing because even though I’m a co-op, everyone in the company is so interconnected and reliant on each other that even small things like writing a blog post make a difference!

Sophia Seltenreich Headshot (Photo courtesy of Yesware)

Speaking more to the company culture, Yesware was voted Boston’s Top Place to Work two years in a row (2017/2018). Everyone at the company is treated exceptionally well, and as a co-op, I was treated no different than a full-time employee. Some office perks include: free catered lunch every day, pet-friendly office space – which means people often bring in their dogs, weekly yoga sessions, monthly massages, board game nights, a nap room, a fully stocked kitchen (including vegan ice-cream & oatmilk), and great people! I cannot speak enough to the character and integrity that each person at Yesware embodies. For example, every two months, all the execs participate in an AMA (Ask Me Anything), exhibiting complete transparency and authenticity, taking the time to answer everyone’s questions. Another example, when an employee makes a successful hiring referral, instead of getting a cash bonus, they make a $5,000 donation to a charity of their choosing. Our People Team also plans and hosts several community events throughout the year, like a Galentine’s Day celebration with She+ Geeks Out & the Big Sister Association of Boston. Getting to work with these kinds of genuine people is the best environment to learn and grow in, and it shows me how passionate people are about the work they do and the communities they’re a part of.

(Photo courtesy of Yesware)

How did you choose to work at a start-up?

I received a competing co-op offer for social management at Liberty Mutual, the antithesis of a start-up company. While working at a fortune 100 company can provide stability and safety, I wasn’t looking to sit at a cubicle and do the same set tasks every day (even if it meant getting a lower wage).

What was a typical day like for you on co-op?

As I said before, every day can be different! A fairly typical day starts off with me scheduling Twitter, Facebook, and LinkedIn posts (after I’ve made myself some breakfast & tea) and going through new emails. After that, I work on sprint goals such as drafting new blog pieces, creating review campaigns, conducting customer outreach for feedback, sorting through data in Pardot, designing graphics in canva etc. Then (free) lunch comes along! After lunch, marketing has a daily stand-up at 1:30pm where we usually discuss the tasks we’re working on (and everyone’s progress as we re-watch Game of Thrones). The latter half of the day consists of me listening to podcasts and finishing whatever goal I set for myself in the morning.

(Photo courtesy of Yesware)

What advice do you have for students who are interested in working for a start-up?

Advice for those seeking start-up jobs: be flexible, and highly adaptable! Take pride in your work, but don’t get too attached to it- changes can be made, projects can be dropped, and work can be scrapped. Be a self-starter, take the initiative on connections and projects you think would help your team or their processes.

What did you learn from your first co-op that you will take with you to your second?

I learned that I had to apply to 40+ positions before I found one I truly resonated with. Don’t be afraid to turn companies down just because they’re the first to offer you a job.

Thank you for sharing your experience with us, Sophia! Be on the lookout for our next co-op feature. If you would like to share your search process, 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 during Summer 2019 Drop-In Hours: Wednesday and Thursday 2:00pm – 4:00pm while classes are in session.

April 10, 2019eckmank No Comments

Co-op Stories: Sarah Higgins, Computer Science

Sarah Higgins is a current Wentworth student majoring in Computer Science. Here’s what Sarah shared with us about her co-op experience:

Where was your co-op? What was your job title? & What interested you in this company/the role?

My first co-op was with Jibo as a Build Tools Software Engineer. I only knew that I liked writing code and problem solving, and I knew there were teams at the company that would provide me with opportunities to get better at both. I lucked out with Jibo because I was not only reassured of my choice to go back to school for Computer Science, but my mentor and the people I got to work with were incredible.

My second co-op was with Validity. Although very different from Jibo, I knew that they were looking for a software engineer to complete tasks similar to what I had worked on at Jibo, so I applied and luckily got the job. I also intentionally wanted to take on a role in a different type of work culture environment to see if it would help me figure out what I like more in a company environment for when I graduate.

What got you interested in Software Engineering?

I took a Computer Science course while I was majoring in Mechanical Engineering and loved it!! The puzzles and problems we got to solve, learning about logic gates, and basic programs written in Java came easy to me.

I have been a hairstylist for the past 10 years and I knew that I always wanted to go back to school, but it’d have to be worth the investment. A few of my friends are mechanical engineers and after talking with them about what their jobs are like, I thought I’d like it and wanted to give it a try. After learning that it takes almost a semester’s worth of time to see what feels like an ounce of progress, I realized I hated it. Coming from an industry where the longest I’m with a client is about 3 hours, that wasn’t going to cut it. Solving problems in as little as 30 seconds with writing programs and logic was far more fun, so I switched my major and dove in to a new found passion.

What did you need to focus on inside or outside of the classroom to be successful as a candidate?

Time management. While I was at school Monday – Friday seeking co-ops, I’d allot an hour each day to specifically apply for co-ops, which meant also writing a lot of cover letters. For my first co-op, I think I sent out almost 45 applications. I heard back from 5 companies for interviews, and I received 2 offers. One was in Providence, and the other was Jibo here in Downtown Boston. Because Jibo was a shorter commute and the company product seemed way cooler, I accepted that one.

For my second co-op, I only had to apply to about 10 companies before I heard from Validity. The second time around is much easier, as everyone told me. Once you’ve gained professional experience, it’s not as stressful applying.

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

My typical day at both Validity and Jibo were very similar. I’d arrive at 9am every day and we’d have a daily stand-up. Stand-up is a brief 5-10 minute meeting in which everyone on your specific software engineering team will say what they have accomplished since the last stand-up, currently working on, when they anticipate to have that completed by, and anything blocking progress from happening.

I’d then continue working on whatever project my mentor had assigned to me. It never took me more than a week or two to complete a project he would give me. My mentor would check in with me frequently via Slack or by coming to my desk to see if I was stuck on anything, and always gave me feedback on whatever I was working on.

I’d be a part of meetings throughout the day, too. Even though I was a co-op, I was treated like every other full-time working member of the team. If the project that I was a part of required me to get more information from other members on the team or the manager, I’d be a part of the meeting to make sure I had everything to go forward.

Every two weeks, we’d have Sprint meetings. Sprint meetings in software engineering allow for more long-term planning, typically two weeks away from where you’re at. We assign projects and tickets to each member of the team and hopefully by the next sprint, all tasks are completed. They almost never were though because Jibo was a start-up, and start-ups demand that everyone take on more than what falls into their realm of responsibility sometimes. That’s okay though, because it was always fun and felt great to know that I could be responsible for more work than the team expected from me!

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

At Jibo, I was a part of the Build Tools team. Build tools I’ve learned are an important and valued discipline in Software Engineering because it gets the products built, deployed, shipped, and its version number is incremented and ready for the next build. A lot of software exists to help make that process easier, and only require a script from the programmer to tell the build what to do. At Validity, I wrote the company’s first automated build script on my own, because I did a lot of work similar to it at Jibo.

At Jibo however, we needed to automate the entire process, which was incredibly complicating. Because Jibo was a robot built with custom hardware that was being turned into its own platform, my mentor and I were responsible for creating the entire build process to communicate with the robot. A software service would not be able to do that. Learning all about what went into a “starting-from-scratch” automation process to deploy software was a life changing experience that made me appreciate the industry side of software building because while writing code, you need to make sure that all of the libraries you choose will work together smoothly.

That project specifically took almost a month for us to complete. I realized how special that was while I was writing my build script at Validity, because it took less than a week’s time. It felt pretty incredible to know that I not only knew all of the behind the scenes build process, but I was able to get it done on my own and thoroughly explain it to someone else properly. I eventually became someone who was a go-to for questions about build software like Jenkins and CircleCI at Validity because of that, which felt amazing!

What was the biggest lesson you learned on co-op?

The biggest and most valuable lesson that I learned is that I can do it, and that I am capable. That might seem like a ridiculous answer, but it’s true. I was terrified going to my first co-op at Jibo, especially since the only “professional” experience I had ever had was in a completely different industry. I had to start over and be a beginner all over again in an industry I knew almost nothing about. I was lucky enough to have an incredible mentor who was also a phenomenal teacher and incredibly patient with me when I needed things explained more than once, but he always gave me all of the credit for whatever I’d figured out. By the end of my co-op, I was given tasks with hardly any instructions and at Validity, it was a lot of the same. It felt amazing being relied on and becoming someone who people could eventually ask questions to about their own work.

What advice do you have for students interested in software engineering?

Dive in and go for it! I was a hairstylist who was frustrated to be stuck in one place because my clientelle was built and established and you can’t bring them with you if you want to pick up and move to a different town, never mind a different state. Software engineering provides open doors almost everywhere, especially in bustling, big cities where there are a lot of companies working on really cool things!

Jibo was a social robot who would talk to us and say things like “Hi, I’m glad you’re here. If you weren’t, I would be talking to myself right now”, and he was able to do that because of the software that my mentor and I had pushed up to him ourselves. Everything that he’d say or do was because of the work we put into it. At Validity, I alongside another software engineering co-op, collaborated on creating and building a brand new website for their customers to keep track of their email accounts, in addition to many other projects like my build script.

Even though the two companies were vastly different, I got to work on projects with similar libraries and languages to allow me to further develop my own skills to carry with me wherever I’d end up next. Right now, I am taking advantage of all of the Python skills I learned at both co-ops in two of my classes. Prior to my co-ops, I had never worked with Python before.

My point is, do it. Just do it. There’s no better feeling in the world than solving a problem on your own, you feel like a wizard sitting at the computer. Seriously. If you want to learn how to write code, go for it. It will be hard, but it’s so worth it. I love who I see when I look at myself in the mirror now, knowing that I am about to graduate with a new found career path and passion, and I did it all for myself. Everybody deserves to know what that feels like. Do it!

Thank you for sharing your experience with us, Sarah! Be on the lookout for our next co-op feature. If you would like to share your search process, 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 during Spring 2019 Drop-In Hours: Monday, Tuesday, and Wednesday 1:30pm – 4:00pm while classes are in session.

February 6, 2019eckmank No Comments

Informational Interviewing Tips

By: Kristen Eckman

One of the best ways to find out what an industry, company, or position is really like is to talk with individuals in the career you are considering. It is also an excellent way to expand your network and prepare for future job searches.

What is an informational interview?

An informational interview is a highly focused information gathering session with a networking contact designed to help you choose or refine your career path by giving you the “insider” point of view.
Through the process, you will gain a better sense of the real life experiences, challenges and opportunities, specific and perhaps hidden demands, as well as the drawbacks and limitations of the career field.
An informational interview can be in-person, over the phone, or via Skype (or another video platform). You should dress professionally and be prepared with a list of questions.

How to Informational Interview :

Identify someone to interview

Consider family, friends, professors, advisors, alumni, and contacts from LinkedIn already in your network.
Get correct spelling and pronunciation of the contact’s name. Know their job title and whether they prefer a salutation.
If you are on co-op, consider conducting an informational interview with your supervisor and/or ask them for potential leads.

Contact that person

Reach out to the contact via email (see end of page for email templates).
State the reason you are reaching out and how you learned about their work.
Request a short (20-30 minute) in-person, phone, or Skype interview.
- If the meeting is in-person, you should go to them.

Schedule the interview

Prepare yourself to be flexible. Consider when it is convenient for them to meet with you.
Professionals prefer that you suggest a few dates and times to meet. It takes the work away from them and makes the decision easier.

Confirm your appointment

Be sure you agree on a date, time, and format for your meeting. A brief note of confirmation will serve as a helpful reminder to you both.

Research the individual and career field

Research and read about the career field, the company, and the individual before you meet. This experience should not be a starting point for your career research, but supplement what you have already learned.
Your interview should focus on the individual and their experience; it is not a time for you to talk about yourself. Should the interviewee ask, be prepared to share a bit about your experience.

Prepare a list of relevant questions (and your resume)

You are the interviewer, so be prepared.
- Find example questions at end of page.
Bring an up-to-date copy of your resume to share only if the interviewee asks for one.

Be on time for your meeting!

Arrive 10-15 early if you are meeting in-person OR be sure your landline/internet connection is properly working. Be ready-to-go 15 minutes before the interview.
Be sure you are professionally dressed, equal to or exceeding the level of dress required at the interviewee’s place of work.

Follow-up with a thank you

Always follow-up with a short note thanking the interviewee for their time. They may be a critical part of your network in the future. NOTE: consider how you will continue to stay in contact in the future.

Don’t Forget To…

Take control of follow-up. Don’t leave the response open to the individual you have contacted. Let them know when you will reach back out, if you haven’t heard from them by the designated time.
Mirror the behavior of the professional you are interviewing.
Don’t forget your professional introduction. They will inevitably ask you to tell them about yourself at some point, so be ready with that important information.
Keep records of your contacts. Consider keeping a journal or creating a spreadsheet to track the names, contact information, and notes from your interviews. It is also helpful to keep the dates of contact and follow-up.
Maintain contact with the individuals you interview, but realize that some contacts might not be a good fit for the relationships you are trying to cultivate right now (or perhaps, ever). Label as: forget, hold, keep.
Connect on LinkedIn. Remember to always send a personalized message with your invitation.

Sample Questions

Who would you consider the leaders of this industry (companies or individuals)?
How do you see this industry changing in the next 5-10 years?
What is a typical day/week like for you?
What challenges do you face in your position?
What is the most enjoyable part of your job?
Why did you choose to work at your current company?
What was your preparation for work in this field?
How did you get into this field? What special skills did you have before entering it?
Are there any skills you wished you had before starting the job?
What educational preparation would you recommend for a new hire in this field?
What experiences/skills do you expect new hires to have for this position?
How would you describe the culture of your organization?
What values does your company highly regard?
How do you know you are successful in what you do?
How does your company develop leaders?
With your current perspective, what additional skills would you have developed while at school to prepare you for this role?
What do you like the most and the least about your job?
What are the greatest rewards of your work?
What are the greatest frustrations? How do you deal with them?
What professional associations are beneficial to this job?
Is there anyone else you suggest I contact?
May I remain in contact with you?

Sample Email Language

Utilize the sample emails below as a guide to contacting your first interviewees.

(No prior connection)

Subject: WIT student seeking industry knowledge

Dear Mr./Ms. Last Name,

I am a sophomore at Wentworth Institute of Technology studying Biomedical Engineering. I found your name through the LinkedIn WIT alumni page. As a sophomore seeking my first co-op, I am hoping to learn from current professionals in the field. In viewing your LinkedIn page, I feel like I could gain valuable insight from what you have to share about your experience.

I wondered if we might be able to set a time for a quick 20-30 minute meeting where I could ask you some questions that will help me prepare for the co-op search ahead of me. We could meet in person, or speak over the phone/SKYPE.

I look forward to hearing from you.

Sincerely,

Your first and last name

(From referral)

Subject: WIT student referred by Professor Christiano

Dear Mr./Ms. Last Name,

I am a sophomore studying Facilities Planning and Management at Wentworth Institute of Technology. Professor Christiano encouraged me to contact you. I would like to learn more about the field of Facilities Planning and Management before I begin my co-op search. I am particularly interested to learn about your own experience at (insert name of company).

I hope to meet with you at your convenience. Please email me with times and dates that are compatible with your schedule. I look forward to hearing from you.

Thank you for your time.

Sincerely,

Your first and last name

Spring 2019 WITwear Hours: Mon–Wed 4PM–8PM, Thurs 5PM–8 PM, Fri 10AM– 12:30PM

Make an appointment with your Co-op + Career Advisor by calling the front desk at 617 989 4101.