See annotations in the file. Basically, the idea here is that instead of using our own account management system, we will rely on an account that the user already has. This can be something like Google Accounts, OpenID, Facebook, Twitter, etc.

This has the benefit of allowing the user to use their existing account information. Additionally, it is usually fairly tricky to get security right, so this design allows us to leverage the work that someone like Google has done.



This is the creation page. This is a pretty free-form layout engine. The user can decide which elements to put on the page, just by dragging over elements from the left. This is a very usable interface since it uses direct manipulation of the elements. The user creates many different pages, things like "leadership," "experience" or "education," to reflect the different sections of a traditional resume. However, the user also has the flexibility to choose different page names, if appropriate.

If a user does not want to customize the layout as directly, he can use an "Auto-Arrange" button, which will line up the elements.

This interface has the disadvantage of being difficult to implement.



This is the shared product. A recruiter can look at the different page, different elements (videos display videos, etc). There are icons on the right for contacting the user throughout various channels (mail, telephone, Facebook). Recruiters can also save their favorites. This can either be a bookmark (using the browser) or a list of favorites stored on the back end.

Overall, this design will be fairly learnable, since the user is manipulating objects directly (on the resume creation). To improve the visibility of the direct manipulability of the elements, they appear as scraps of paper that can be dragged on to the canvas. Additionally, the direct manipulation has good error recovery, enhanced by undo/redo (for example, undoing accidental deletions). The efficiency is not quite as strong, since users will have to position the elements manually (or use a limited auto-arranger). If a user has many positions to enter, for instance, it may become a tedious task.

The visibility is fairly good: the elements are arranged as categories, and the active category is highlighted. We encourage users to limit their design to one "screen-full," to make it easy for the recruiter to use.

This design may not be realistic since some of the pieces (the direct manipulation and saving of elements, for example) may be too ambitious to finish in a reasonable amount of time.

  • No labels