IA Summit 2010 - Career Workshop - April 8, 2010 -Phoenix, AZ
by Russ Unger on Apr 09, 2010
- 2,579 views
http://2010.iasummit.org/talks/9703 ...
http://2010.iasummit.org/talks/9703
The Career Workshop for Information Architects and other User Experience
Professionals is a half-day event that teaches attendees how to optimize their
career search. Attendees will learn the skills needed in today’s market, and
will get the opportunity to network and share ideas.
Divided into four information-packed sessions, the workshop will include
discussions, and individual and team exercises:
1. Career Listings, Career Sites and Agencies
Looking at recent career listings to understand what employers are looking for
Communicating what IA’s do to recruiters
Applying lessons learned to cover letters and interview conversations
2. Resumes
Examining sample resumes
Tips for designing an IA-oriented resume that stands out
3. Portfolios
Understanding what makes a great portfolio
Determining the best method to display it
4. Interviewing
Examining what interviewers want to hear
Presenting yourself through your portfolio
Communication tips for before, during and after the interview
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 21
- Downloads
- 0
- Comments
- 0
- Embed Views
- Views on SlideShare
- 2,525
- Total Views
- 2,579
are an interesting beast: there are a number of ways you can create them
from a style and information perspective. How you do it is up to you.
A typical title page consists of the following elements:
Client company name
Client company logo (if you have permission to use it)
Project title
Document type (proposal)
Version of proposal
S ubmission date
Your company name
Proposal authors
Project reference number
Cost
Confidentiality
the terms, you are ready to begin working. So when additional modifications
are requested, you need to review them very carefully. This ensures your
costs still make sense and that there is a clear understanding on both sides
about the modifications and at what stage the project is restarting (if necessary).
You should also always provide an appropriate explanation of why the
revision constitutes a full new version in the revision history.
Licensed work - you give up compiled files; no source
Licensed work - you give up compiled files; no source
Licensed work - you give up compiled files; no source