Blog

Filter by:

Limit to posts where the date of the blog post:
Date range
Limit to posts where the date of the blog post:
Limit to posts where the title matches:
Limit to posts tagged with one or more of:
Limit to posts where the audience is one or more of:

As the fall term approaches, it’s almost time to finish your co-op term or get ready for a co-op placement interview. To help you get ready, the Writing and Communication Centre (WCC) teamed up with Co-op Connection this week to give you a few resume writing tips. We’ve also included undergraduate writing programming that would not only be helpful for getting started on your resumes, but also for your cover letters and work term reports.

As the spring term draws to a close, the fall term is drawing nearer. If you are enrolled in co-op at university,  it may be the dreaded recruitment term. On top of juggling courses, assignments, essays and exams, you have to find a job. You have to submit what seems like 200 cover letters and resumes, and attend multiple nerve-racking interviews, just with the hopes of landing a good job with decent pay, in a decent location and with decent responsibilities. Although the recruitment term is stressful and overwhelming, it is a great opportunity to refocus your goals and aspirations.

Tuesday, December 8, 2015

End of Term Blues

There’s this weird bittersweet feeling we tend to get when something is coming to an end. It doesn’t matter whether the ending is a good or bad thing: it’s just somewhat sad every single time! This isn’t a question of reverse-schadenfreude either. I have no answer for you. I’m sure there’s research on the web that can explain this but to avoid having to create a Works Cited list, here’s how I've always dealt with change.

Going to school for the first time was wild

I did a co-op term as a technical writer at a high tech company here in Waterloo.

The job of a technical writer varies from company to company, but essentially it involves writing text that allows customers to understand how to use technology. In my case I was documenting software changes, and the process went something like this: