Make your own free website on Tripod.com
LINKS
SUBSCRIBE



Powered by FeedBlitz

ARCHIVE
« June 2012 »
S M T W T F S
1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Thursday, 20 April 2006
Some thoughts about mock job interviews
At our board meeting on April 7th, Dr. Ford set aside time for students to participate in mock job interviews. Disappointingly, only one student participated. Or should I say took the opportunity to practice a job interview. I invited several students who were sitting in the reading room, just outside of the room in which we were meeting, to join us, but they chose not to.

I understand that being interviewed by several people, or even one person, isn't on a par with hanging out with friends or gaming on a computer, but it is one of the necessary evils you must suffer to get a job today. The fact is that the more often you can interview, the better your chances of coming off well in an interview and landing a job. Doesn't it make sense to suffer some practice interviews among friends and supportive mock interviewers than to stumble through a real job interview, suspecting that you probably blew it?

Let me offer an analogy. If you wanted to be invited to join a volleyball or softball team, wouldn't you practice some before the day you had to demonstrate your skills to the team manager or captain? Wouldn't you spend time trying to get skilled enough so you didn't look foolish on the day it counted? Job interviews are exactly the same. Practice some before the event and come off looking more polished, confident, and desirable as a prospective employee.

Except for the lack of students at the mock interviews, I thought the faculty and students showed more talent, enthisiasm, and energy than I've seen in a long time. You all are doing a great job in the TC program.

See you all next year in the afternoon of the board meeting for a mock interview and review of your portfolio. Both are tools needed to land that after-graduation job. :)

Posted by artelser at 8:31 AM MDT
Post Comment | View Comments (2) | Permalink
Wednesday, 19 April 2006
Senior Thesis Presentations
All are invited to the final presentations by this year's Senior Thesis students.

Presentations will take place on Thursday, May 04 from 3:30-5:30 in Library 212.

Following the presentations, TC students who have received STC awards or scholarships will be recognized.

Posted by jford29 at 3:55 PM MDT
Post Comment | Permalink
Thursday, 13 April 2006
Corp Board meeting feedback
Hi all-
Thanks again for such a productive meeting last week. I especially appreciate your feedback for our senior thesis students and students who are thinking about job search materials.

If you have any suggestions for next year's meeting (it helps to think of these things while they are fresh in your mind), please let us hear from you. I've already noted that instead of designating an hour specifically towards mock interviewing, (and subsequently scaring off students-- sorry), we'll set aside a 2-hour block of time for either portfolio review or mock interviewing or both.

Posted by jford29 at 10:44 AM MDT
Post Comment | View Comments (2) | Permalink
Tuesday, 17 January 2006
Happy 2006!
Happy 2006 everyone! May this year bring you knowledge, the benefits of hard work, and clear communication.

If you got a day planner (or the high-tech version, a palm pilot) for the holidays, I encourage you to get it out right now and mark the date of this year's corporate board meeting. Drumroll....this year our meeting will be on Friday, April 7th. I'll be planning the agenda over the next month or so, and I welcome your ideas.

Posted by jford29 at 3:01 PM MST
Post Comment | Permalink
Saturday, 19 November 2005
Re: Tech Writing and the Art of Laziness
Topic: TC 101
TC 101 Students-
As many of you wrote about in your reading response, Tim Casady's "Tech Writing and the Art of Laziness" highlights the importance of being an efficient technical communicator. While the term "lazy" is used, I don't see the technical writer in this story as lazy, instead I view him as practical, clever, and, efficient.

And, let's face it, in many of the workplaces we've heard about this semester where technical writers are involved in various demanding projects, it seems necessary to be practical, clever, and efficient to survive. With that in mind, I'd like to hear your thoughts regarding what technical writers can do to be efficient. What practices can they put into place to save time and save duplication of efforts (especially if they are working in a group)? If you learned from experience how to be a more efficient writer on a project, you may want to share that experience with us. I'll look forward to seeing your thoughts.

Posted by jford29 at 5:56 PM MST
Updated: Monday, 21 November 2005 8:06 PM MST
Post Comment | View Comments (6) | Permalink

Newer | Latest | Older