Patent Application
20140129465
The hiring process for qualified employees is becoming increasingly competitive. In addition, qualified candidates often do not actively apply for new positions. Therefore, it can be a challenge for a company to recruit qualified candidates for open positions.
The hiring process can be difficult and time consuming. Typically, a company posts a job opening and waits for candidates to apply. The job opening could be posted, for example, on-line, in a newspaper, etc. A person within the company, such as a hiring manager, typically receives submissions from candidates interested in the position, manually reviews and organizes the candidates, conducts interviews, and ultimately makes job offers. This process of posting job openings, receiving candidate submissions, manually reviewing, screening, and organizing the candidates, can be time consuming and difficult, particularly when there are many applicants for a position, or when there are many positions to fill.
Furthermore, it is often the case that qualified candidates do not actively apply for new positions. Therefore, even if a company posts a job opening, qualified candidates may not be aware of the job opening.
Therefore, there exists ample opportunity for improvement in technologies related to managing candidates for job openings.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
For example, a talent acquisition pipeline (talent pipeline) can be provided for managing candidates for a job opening (a job position or position). The talent acquisition pipeline comprises a plurality of stages. Information can be displayed along with the talent acquisition pipeline, including a count of candidates associated with the stages and/or target values associated with the stages. Candidates can be moved between stages (e.g., by a user, such as a recruiter, sourcer, or hiring manager). Stage-specific actions can be selected to perform various actions related to the candidates for a selected stage.
As another example, a method can be provided for managing candidates using a talent acquisition pipeline. The method comprises displaying, to a user, a talent pipeline, where the talent pipeline comprises a plurality of stages, receiving, from the user, a selection of a stage from the displayed plurality of stages of the talent pipeline, in response to the selection of the stage, displaying, to the user, a list of candidates, where the list of candidates are associated with the selected stage, and receiving, from the user, an action to move a selected candidate from the list of candidates to a different stage of the plurality of stages.
As another example, a method can be provided for managing candidates using a talent acquisition pipeline. The method comprises displaying, to a user, a talent pipeline, where the talent pipeline comprises a plurality of stages, receiving, from the user, a selection of a stage from the displayed plurality of stages of the talent pipeline, in response to the selection of the stage, displaying, to the user, a list of candidates, where the list of candidates are associated with the selected stage, and in response to the selection of the stage, displaying, to the user, a user interface element for performing a stage-specific action for the displayed list of candidates, where the stage-specific action is associated with the selected stage.
As another example, a user interface can be provided for managing candidates using a talent acquisition pipeline. The user interface comprises a first user interface area displaying the talent pipeline, where the talent pipeline comprises a plurality of stages, and where displaying the talent pipeline comprises displaying the plurality of stages. The user interface also comprises a second user interface area displaying a list of candidates. When a stage of the displayed plurality of stages is selected, the second user interface area displays a list of candidates that are associated with the selected stage, and user interface elements are displayed for performing stage-specific actions for the list of candidates.
As described herein, a variety of other features and advantages can be incorporated into the technologies as desired.
The following description is directed to techniques and solutions for managing candidates (talents) using a talent acquisition pipeline (talent pipeline). A talent acquisition pipeline divides the process of identifying and hiring (including, for example, sourcing) candidates into a plurality of stages. The talent acquisition pipeline can display information associated with one or more stages of the pipeline. For example, the talent acquisition pipeline can display a current count of candidates associated with one or more of the stages. The talent acquisition pipeline can also display a target number (e.g., a goal) of candidates for one or more of the stages.
Stages of the talent acquisition pipeline can be selected. For example, a user of a graphical user interface can select on a stage of the pipeline (e.g., by clicking, tapping, or otherwise selecting the stage, or by using another type of user interface control). Selecting the stage of the pipeline displays candidates associated with (e.g., assigned to) the selected stage. For example, displaying the candidates associated with a selected stage can comprise displaying a list of candidates and their associated details (e.g., name, current job information, skills and experience, match information, stage-specific actions that can be performed for the candidate, etc.).
Actions can be performed using the talent acquisition pipeline and associated candidate information. For example, a user interface can display the talent acquisition pipeline and a list of candidates along with stage-specific actions. The stage-specific actions can be selected by a user to perform actions that are relevant to the selected stage and the list of candidates. For example, if the selected stage is a “Long List” stage, then the list of candidates can be displayed along with stage-specific actions to contact the candidates (e.g., call, email, etc.), to move candidates to the “Short List” stage, to move candidates to the “Applicants” stage, to delete candidates from the pipeline, to move candidates back to the “Search Results” stage, etc.
Candidates can be moved between stages. For example, a user can select a candidate from a list of candidates and move the selected candidate to a different stage. The user can move the candidate by dragging and dropping the candidate (a drag-and-drop action) from the list to a different stage of the displayed pipeline using a graphical user interface. The user can also move the selected candidate using another type of user interface control (e.g., by selecting the user and selecting a move button or move selection from a drop-down list).
In any of the examples herein, a talent acquisition pipeline can be provided for managing candidates for job openings. The talent acquisition pipeline comprises a plurality of stages that group candidates (e.g., during the hiring process). The talent acquisition pipeline provides for quick and efficient visualization of the status of candidates for a job opening. The talent acquisition pipeline also provides for efficient selection of candidates, moving candidates between stages, performing actions related to the candidates (e.g., sending communications, moving between stages, etc.).
The “Long List” stage of the talent acquisition pipeline 100 groups candidates that have been identified for further action. For example, a recruiter or sourcer can review the candidates in the Search Results stage. Those candidates that the recruiter or sourcer would like to investigate further can be moved to the Long List. For example, a recruiter or sourcer can research candidates in the Long List and/or contact (e.g., call and/or email) candidates in the Long List to determine whether they are interested in the position. The candidates can also be selected automatically (e.g., based on qualifications) for movement from the Search Results stage to the Long List stage.
The “Short List” stage of the talent acquisition pipeline 100 groups candidates, for example, that have been pre-qualified (e.g., by the recruiter), candidates that have indicated interest in the position, and/or candidates that are otherwise of particular interest (e.g., are well matched to the position). For example, a recruiter can research and/or contact candidates in the Long List. Based on the research and/or contact, the recruiter can move candidates to the Short List. The candidates in the Short List can be candidates that are being seriously considered for the position. For example, a recruiter can contact candidates in the Short List and request that the candidates apply for the position.
In some implementations, a “Reviewed” stage is included in the talent acquisition pipeline 100 after the Short List stage. For example, the Reviewed stage can group candidates that have gone through additional review after being moved to the Long List or Short List. Candidates in the Reviewed stage can be considered qualified (e.g., pre-qualified) to apply for the position.
The “Applicants” stage of the talent acquisition pipeline 100 groups candidates that have applied for the job. For example, a candidate that is in the Short List or Long List stage can be contacted about the job opening. In response, the candidate can apply for the position (e.g., verbally apply and/or submit an application). For example, the candidate can complete a web-based job application form. Once the candidate has applied, the candidate can be moved to the Applicants stage. Alternatively, an individual that is not in the Short List or Long List stage may apply for the job. For example, the individual may see a job posting (e.g., on an internal or external web site) and apply.
The “Interviewed” stage of the talent acquisition pipeline 100 groups candidates that have interviewed for the position. For example, a candidate that is in the Applicants stage can be contacted by a recruiter to schedule an interview. Once the interview has been requested, scheduled, and/or conducted, the candidate can be moved to the Interviewed stage.
The “Offered” stage of the talent acquisition pipeline 100 groups candidates that have been made a job offer. For example, a candidate in the Interviewed stage can be selected and a job offer can be sent to the candidate. Once the job offer has been made and/or accepted, the candidate can be moved to the Offered stage.
The “Hired” stage of the talent acquisition pipeline 100 groups candidates that have been hired. For example, a candidate that is in the Offered stage can accept the job offer. Once accepted, the candidate can be moved to the Hired stage.
A talent acquisition pipeline can have more stages, fewer stages, and/or different stages than the stages depicted in
From the example pipeline 200, a user can see (e.g., via a graphical user interface that visually depicts the pipeline 200 and the number of candidates in each stage) the status of the job search. For example, from the example pipeline 200, a user (e.g., recruiter, sourcer, manager, or someone else that uses the pipeline) can see that 327 candidates were identified (e.g., from an automated search of on-line profile information), that 32 of the candidates were moved to the Long List stage (e.g., were reviewed and determined to be a good fit for the position), that 12 candidates (e.g., candidates from the Long List and/or from the Search Results) were moved to the Short List (e.g., based on additional research and/or communication with the candidate), that 4 candidates (e.g., from the Search Results, Long List, Short List, and/or an outside source) applied for the position, and that 3 candidates interviewed for the position. In this way, the user of the example pipeline 200 can quickly and efficiently evaluate the status of filling the position, what additional action is needed (e.g., evaluate the interview results and make an offer), and how long it might take to complete the process and hire a candidate.
In some implementations, a candidate can only be associated with one stage at a time for a given job opening.
Target values can be set for one or more stages of a talent acquisition pipeline. The target values indicate a target number (e.g., a goal or desired number) of candidates for the corresponding stage. In some implementations, the target value is the recommended number of candidates for the particular stage to fill the job opening within a specified amount of time. The target values can vary depending on a number of factors, including the type of job, the desired time to fill the job, etc. For example, to fill a marketing associate job opening within 60 days, specific target values can be set for the recommended number of candidates for various pipeline stages.
A talent acquisition pipeline can be used for a job opening to be filled by one candidate or by a plurality of candidates. For example, a job opening can be created for a group of two or more candidates (e.g., for a call center team), with a single talent acquisition pipeline grouping all the candidates.
In any of the examples herein, a user interface can be provided for managing candidates using a talent acquisition pipeline. The user interface can be presented, for example, as a local application and/or as a remote (e.g., web-based or online) application or service.
In the user interface 400, the Long List stage of the talent acquisition pipeline 412 has been selected 414 by a user. In response to the selection 414 of the Long List stage, a second user interface area 420 is displayed. The second user interface area 420 contains a list of candidates that are associated with the selected Long List stage. In the example user interface 400, the Long List has five candidates. Therefore, when the Long List stage is selected, the five candidates are listed in the second user interface area 420.
The list of candidates depicted in the second user interface area 420 includes candidate information (name, position, etc.), skills and experience (e.g., a summary of job experience and/or other skills), a match indication, and actions. The match indication can indicate how closely the candidate matches the job opening. The match indication can be displayed, for example, as a number of stars (e.g., out of a possible five stars), as a percentage, etc. One or more match indications can be displayed. For example, a match indicator can be displayed for matching a target profile and/or a match indicator can be displayed ranking top performers among the candidates.
The actions displayed with the list of candidates in the second user interface area 420 can include stage-specific actions for managing the candidates depending on which pipeline stage of the talent acquisition pipeline 412 is selected. In the example user interface 400, the Long List stage is selected 414. Based on the selected Long List stage, the actions can comprise stage-specific actions, such as an action to contact a selected candidate (e.g., call or email the candidate to determine whether the candidate is interested in the position or would like to submit an application), an action to move a selected candidate to the Short List (e.g., based on further research or review, or based on communication with the candidate), an action to move a selected candidate back to the Search Results stage, and an action to remove the candidate from the pipeline (e.g., due to the candidate indicating a lack of interest in the position). The actions can be performed by a user selecting a user interface element, such as a drop-down list, buttons, or other user interface elements.
Stage-specific actions are provided depending on the selected stage of the target acquisition pipeline. For example, stage-specific actions for a Search Results stage can include: move candidate to Long List, move candidate to Short List, and remove candidate. Stage-specifications for a Long List stage can include: move candidate to Search Results, move candidate to Short List, move candidate to Applicants, contact candidate, and remove candidate. Stage-specifications for a Short List stage can include: move candidate to Search Results, move candidate to Long List, move candidate to Applicants, contact candidate, and remove candidate. Stage-specifications for an Applicants stage can include: move candidate to Short List, move candidate to Interviewed (e.g., schedule or conduct interview), and remove candidate. Stage-specifications for an Interviewed stage can include: move candidate to Offered (e.g., make offer to candidate), and remove candidate. Stage-specifications for an Offered stage can include: move candidate to Hired, and remove candidate
Some stage-specific actions are applicable to more than one stage, and other stage-specific actions are only available when a specific stage is selected. For example, in some implementations, a send offer stage-specific action is only available to candidates associated with an Interviewed stage (e.g., when the Interviewed stage is selected). In some implementations, a schedule interview stage-specific action is only available to candidates associated with an Applicants stage (e.g., when the Applicants stage is selected). In some implementations, a hired stage-specific action is only available to candidates associated with an Offered stage (e.g., when the Offered stage is selected).
Candidates can also be moved between stages in other ways. For example, a user of the user interface 400 can select a candidate from the list displayed in the second user interface area 420 and move the selected candidate to a different stage of the talent acquisition pipeline 412. The movement can be accomplished using a drag-and-drop action. For example, the user can select the candidate and drag the candidate to a different stage (e.g., drag candidate Randy Dickinson from the second user interface area 420 to the Short List stage of the talent acquisition pipeline 412 depicted in the first user interface area 410).
In any of the examples herein, methods can be provided for managing candidates using a talent acquisition pipeline.
At 710, a talent acquisition pipeline is displayed (e.g., displayed to a user). The talent acquisition pipeline comprises a plurality of stages. In some implementations, the talent pipeline comprises a plurality of the stages depicted in
At 720, a selection of a stage is received (e.g., from the user) from the displayed stages of the talent acquisition pipeline. For example, the stages can be displayed with associated information, such as counts of candidates associated with one or more of the stages and/or target values associated with one or more of the stages.
At 730, a list of candidates associated with the selected stage is displayed. For example, displaying the list of candidates can comprise displaying candidate information such as: name, position, skills and experience, match score(s), etc. Actions, such as stage-specific actions, can also be displayed and/or received. For example, actions to move a candidate from the displayed list of candidates can be received (e.g., a drag-and-drop action and/or an action selected from a user interface element such as a button or drop-down list).
At 740, an action to move a selected candidate (from the displayed list of candidates) to a different stage (from the currently selected stage) is received. Once the candidate has been moved, the talent acquisition pipeline can display, for example, updated counts of candidates in each of the stages.
At 810, a talent acquisition pipeline is displayed (e.g., displayed to a user). The talent acquisition comprises a plurality of stages. In some implementations, the talent pipeline comprises a plurality of the stages depicted in
At 820, a selection of a stage is received (e.g., from the user) from the displayed stages of the talent acquisition pipeline. For example, the stages can be displayed with associated information, such as counts of candidates associated with one or more of the stages and/or target values associated with one or more of the stages.
At 830, a list of candidates associated with the selected stage is displayed (e.g., to the user). For example, displaying the list of candidates can comprise displaying candidate information such as: name, position, skills and experience, match score(s), etc. Actions, such as stage-specific actions, can also be displayed and/or received. For example, actions to move a candidate from the displayed list of candidates can be received (e.g., a drag-and-drop action and/or an action selected from a user interface element such as a button or drop-down list).
At 840, a user interface element is displayed (e.g., to the user) for performing a stage-specific action for the displayed list of candidates. The stage-specific action is an action that is associated with the selected stage (e.g., it is an action that can be performed for candidates associated with the selected stage). The stage-specific action could be an action that is only associated with the selected stage (and not available for use with other stages). For example, the stage-specific action could be a make offer stage-specific action for a selected Interviewed stage. The stage-specific action could also be an action that is present in more than one stage. For example, the stage-specific action could be a “move to applicants” stage specific action where the selected stage is either a Long List stage or a Short List stage.
With reference to
A computing system may have additional features. For example, the computing system 900 includes storage 940, one or more input devices 950, one or more output devices 960, and one or more communication connections 970. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computing system 900. Typically, operating system software (not shown) provides an operating environment for other software executing in the computing system 900, and coordinates activities of the components of the computing system 900.
The tangible storage 940 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, DVDs, or any other medium which can be used to store information in a non-transitory way and which can be accessed within the computing system 900. The storage 940 stores instructions for the software 980 implementing one or more innovations described herein.
The input device(s) 950 may be a touch input device such as a keyboard, mouse, pen, or trackball, a voice input device, a scanning device, or another device that provides input to the computing system 900. For video encoding, the input device(s) 950 may be a camera, video card, TV tuner card, or similar device that accepts video input in analog or digital form, or a CD-ROM or CD-RW that reads video samples into the computing system 900. The output device(s) 960 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing system 900.
The communication connection(s) 970 enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, audio or video input or output, or other data in a modulated data signal. A modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media can use an electrical, optical, RF, or other carrier.
The innovations can be described in the general context of computer-executable instructions, such as those included in program modules, being executed in a computing system on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Computer-executable instructions for program modules may be executed within a local or distributed computing system.
The terms “system” and “device” are used interchangeably herein. Unless the context clearly indicates otherwise, neither term implies any limitation on a type of computing system or computing device. In general, a computing system or computing device can be local or distributed, and can include any combination of special-purpose hardware and/or general-purpose hardware with software implementing the functionality described herein.
For the sake of presentation, the detailed description uses terms like “determine” and “use” to describe computer operations in a computing system. These terms are high-level abstractions for operations performed by a computer, and should not be confused with acts performed by a human being. The actual computer operations corresponding to these terms vary depending on implementation.
The cloud computing services 1010 are utilized by various types of computing devices (e.g., client computing devices), such as computing devices 1020, 1022, and 1024. For example, the computing devices (e.g., 1020, 1022, and 1024) can be computers (e.g., desktop or laptop computers), mobile devices (e.g., tablet computers or smart phones), or other types of computing devices. For example, the computing devices (e.g., 1020, 1022, and 1024) can utilize the cloud computing services 1010 to perform computing operators (e.g., data processing, data storage, and the like).
Although the operations of some of the disclosed methods are described in a particular, sequential order for convenient presentation, it should be understood that this manner of description encompasses rearrangement, unless a particular ordering is required by specific language set forth below. For example, operations described sequentially may in some cases be rearranged or performed concurrently. Moreover, for the sake of simplicity, the attached figures may not show the various ways in which the disclosed methods can be used in conjunction with other methods.
Any of the disclosed methods can be implemented as computer-executable instructions or a computer program product stored on one or more computer-readable storage media and executed on a computing device (e.g., any available computing device, including smart phones or other mobile devices that include computing hardware). Computer-readable storage media are any available tangible media that can be accessed within a computing environment (e.g., non-transitory computer-readable media, such as one or more optical media discs such as DVD or CD, volatile memory components (such as DRAM or SRAM), or nonvolatile memory components (such as flash memory or hard drives)). By way of example and with reference to
Any of the computer-executable instructions for implementing the disclosed techniques as well as any data created and used during implementation of the disclosed embodiments can be stored on one or more computer-readable storage media (e.g., non-transitory computer-readable media). The computer-executable instructions can be part of, for example, a dedicated software application or a software application that is accessed or downloaded via a web browser or other software application (such as a remote computing application). Such software can be executed, for example, on a single local computer (e.g., any suitable commercially available computer) or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a client-server network (such as a cloud computing network), or other such network) using one or more network computers.
For clarity, only certain selected aspects of the software-based implementations are described. Other details that are well known in the art are omitted. For example, it should be understood that the disclosed technology is not limited to any specific computer language or program. For instance, the disclosed technology can be implemented by software written in C++, Java, Perl, JavaScript, Adobe Flash, or any other suitable programming language. Likewise, the disclosed technology is not limited to any particular computer or type of hardware. Certain details of suitable computers and hardware are well known and need not be set forth in detail in this disclosure.
Furthermore, any of the software-based embodiments (comprising, for example, computer-executable instructions for causing a computer to perform any of the disclosed methods) can be uploaded, downloaded, or remotely accessed through a suitable communication means. Such suitable communication means include, for example, the Internet, the World Wide Web, an intranet, software applications, cable (including fiber optic cable), magnetic communications, electromagnetic communications (including RF, microwave, and infrared communications), electronic communications, or other such communication means.
The disclosed methods, apparatus, and systems should not be construed as limiting in any way. Instead, the present disclosure is directed toward all novel and nonobvious features and aspects of the various disclosed embodiments, alone and in various combinations and sub combinations with one another. The disclosed methods, apparatus, and systems are not limited to any specific aspect or feature or combination thereof, nor do the disclosed embodiments require that any one or more specific advantages be present or problems be solved.
The technologies from any example can be combined with the technologies described in any one or more of the other examples. In view of the many possible embodiments to which the principles of the disclosed technology may be applied, it should be recognized that the illustrated embodiments are examples of the disclosed technology and should not be taken as a limitation on the scope of the disclosed technology. Rather, the scope of the disclosed technology includes what is covered by the following claims. We therefore claim as our invention all that comes within the scope and spirit of the claims.
