This disclosure relates generally to the technical fields of communications and, in one example embodiment, to a method and system of job search in a geo-spatial environment.
Job search engines are websites that facilitate job hunting. The job search engines may allow users to store resumes on the site and/or submit the resumes to potential employers. Similarly, employers may post job listings and/or search for potential employees on the job search engines. The job search engine may encompass a variety of occupations and/or job types or serve a niche market, such as engineering, legal services, insurance, social work, and/or teaching. In addition, the job search engines may cater to a specific geographic region, level of education, and/or skill level.
The job search engines may include separate interfaces for candidates and employers. The candidates may be allowed to perform functions such as browsing and/or searching for job listings, posting, editing, and/or updating of resumes and/or cover letters, updating user profiles and preferences, contacting potential employers. submitting resumes and/or cover letters to the potential employers, etc. The employers may post, edit, and/or update job listings, access posted resumes and/or cover letters, search resumes for matches with job listings, contact candidates, etc.
The job search engines may be implemented by traditional job boards. For example, a job board may provide job search capabilities for the candidates and the employers to find desired positions and the potential employees, respectively. Alternatively, the job search engines may be implemented to search across multiple job boards. Other job search engines may index directly from the employers' websites, thus bypassing traditional job boards altogether and/or allowing the candidates to find new positions that may not be advertised on the traditional job boards.
Despite the development of specialized and/or indexed job search engines, the candidates and/or the employers may still have difficulty finding an ideal match for a position. In other words, the candidates may not adequately find ideal positions using typical search parameters offered by the job search engines. For example, the candidates may seek positions within a certain commute distance and/or time from home. The ideal commute distance and/or time for a candidate may be based on a number of factors, such as traffic conditions, mode of transportation, cost of transportation, willingness to devote time to commuting, etc. However, current job search methods may be limited to returning results from a particular city, region, and/or state. As a result, the candidates may have difficulty using the job search engines to find positions that alleviate problems associated with commuting to work.
A method and system of job search in a geo-spatial environment are disclosed. In one aspect, a method of conducting a job search includes obtaining candidate data (e.g., name, resume, cover letter, experience level, education level, and/or employment preference, etc.) corresponding to a job search profile, determining a location associated with the job search profile (e.g., may be a non-residential location) based on the candidate data, storing the job search profile in a candidate repository, processing a search request from a user associated with the job search profile, obtaining a search radius associated with the location (e.g., may be a distance from the location and/or a commute time from the location) from the user, obtaining at least one employer profile based on the search radius, and displaying the employer profile to the user on a geo-spatial map.
The method may further include obtaining a search parameter from the user, and obtaining the employer profile based on the search radius and the search parameter (e.g., job category, job type, keyword, salary range, experience level, and/or education level, etc.).
In another aspect, a community network includes a candidate repository including a plurality of job search profiles, an employer repository including a plurality of employer profiles (e.g., may include employer name, employer description, location, education level, experience level, job title, job description, compensation, and/or candidate preference, etc.), a geo-spatial repository including a plurality of locations on a geo-spatial map, and a job management module configured to determine a first of the locations associated with one of the job search profiles (e.g., may include name, resume, cover letter, experience level, education level, and/or employment preference, etc.), process a search request from a first user associated with the one of the job search profiles, obtain a first search radius associated with the first of the locations (e.g., may be a distance from the location and/or a commute time from the first of the locations) from the first user, obtain the employer profiles based on the first search radius, and display the employer profiles to the first user on the geo-spatial map.
The job management module may be further configured to obtain a first search parameter (e.g., may include job category, job type, keyword, salary range, experience level, and/or education level, etc.) from the first user, and obtain the employer profiles based on the first search radius and the first search parameter.
In addition, the job management module may be configured to determine a second of the locations associated with one of the employer profiles, process a search request from a second user associated with the one of the employer profiles, obtain a second search radius associated with the second of the locations from the second user, obtain the job search profiles based on the second search radius, and display the job search profiles to the second user on the geo-spatial map. The job management module may also be configured to obtain a second search parameter from the second user, and obtain the job search profiles based on the second search radius and the second search parameter.
In yet another aspect, a method of conducting a job candidate search includes obtaining employer data (e.g., may include employer name, employer description, location, education level, experience level, job title, job description, compensation, and/or candidate preference, etc.) corresponding to an employer profile, determining a location associated with the employer profile based on the employer data, storing the employer profile in an employer repository, processing a search request from a user associated with the employer profile, obtaining a search radius associated with the location (e.g., may be a distance from the location and/or a commute time from the first of the locations) from the user, obtaining at least one of the job search profile based on the search radius, and displaying the job search profile to the user on a geo-spatial map.
The method may further include obtaining a search parameter (e.g., may include job category, job type, keyword, salary range, experience level, and/or education level) from the user, and obtaining the job search profile based on the search radius and the search parameter.
The methods, systems, and apparatuses disclosed herein may be implemented in any means for achieving various aspects, and may be executed in a form of a machine-readable medium embodying a set of instructions that, when executed by a machine, cause the machine to perform any of the operations disclosed herein. Other features will be apparent from the accompanying drawings and from the detailed description that follows.
Example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.
A method and system of job search in a geo-spatial environment are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It will be evident, however to one skilled in the art that the various embodiments may be practiced without these specific details.
In one embodiment, a method of conducting a job search includes obtaining candidate data (e.g., using the candidate repository 114 of
In another embodiment, a community network (e.g., the community network 102 of
The community network 102 also includes a job management module (e.g., the job management module 108 of
In yet another embodiment, a method of conducting a job candidate search includes obtaining employer data (e.g., the employer name 402, the location 404, the education 406, and/or experience 408, etc.) corresponding to an employer profile (e.g., the employer profile 400 of
The community network 102 may be a network formed by an association of the members 106A-N in the community 104. The community 104 may refer to a group of members 106A-N located in a specific geographic region. The members 106A-N may include individuals (e.g., employers, candidates, etc.) searching for desired positions and/or potential employees. The members 106A-N may be connected with each other through the community network 102. In one or more embodiments, the member 106 of the community network 102 performing any one of a job search and a candidate search is referred as a user (e.g., candidate, employer).
The job management module 108 may enable a job search and/or a candidate search based on a search parameter and/or a search radius (e.g., the search radius 204 of
In one example embodiment, the search request may be a request made by the member 106 (e.g., anyone of the employer and candidate) based on the search parameters (e.g., job category, job type, and/or experience, etc.) and/or the search radius 204. For example, the search radius 204 may be a geographical distance through which a location of the candidate and the employer are separated. In another example embodiment, the search radius 204 may be a commute time from a location specified by the candidate.
The geo-spatial repository 110 may be a database including location information associated with the members 106A-N of the community 104. The employer repository 112 may be a database including the employer profiles 400. The candidate repository 114 may be a database including the job search profiles 300.
In the example embodiment illustrated in
In accordance with one or more embodiments, the job search profiles 300 (e.g., may include name, resume, cover letter, experience level, education level, and/or employment preference, etc.) may be stored in the candidate repository 114 and the employer profiles 400 may be stored in the employer repository 112. The geo-spatial repository 110 may include a number of locations (e.g., associated with the job search profiles 300 and employer profiles 400) on the geo-spatial map 200.
In one example embodiment, the job management module 108 may be configured to determine a first location associated with a job search profile 300 and process a search request from a first user (e.g., candidate) associated with the job search profile 300. The job management module 108 may be further configured to obtain a first search radius 204 (e.g., may be a distance from the first location and/or a commute time from the first location) associated with the first location from the first user.
In addition, the job management module 108 may be configured to obtain the employer profiles 400 (e.g., may include employer name, employer description, location, education level, experience level, job title, job description, compensation, and/or candidate preference, etc.) based on the first search radius 204 and display the employer profiles 400 to the first user on the geo-spatial map 200. The job management module 108 may be yet configured to obtain a first search parameter (e.g., may include job category, job type, keyword, salary, experience level, and/or education level, etc.) from the first user and obtain the employer profiles 400 based on the first search radius 204 and the first search parameter.
In another example embodiment, the job management module 108 may be configured to determine a second location associated with an employer profile 400 and process a search request (e.g., may include search radius 204) from a second user (e.g., employer) associated with the employer profile 400. The job management module 108 may also be configured to obtain a second search radius 204 associated with the second location from the second user.
In addition, the job management module 108 may be configured to obtain job search profiles 300 (e.g., may include name, resume, cover letter, experience level, education level, and/or employment preference, etc.) based on the second search radius 204 and display the job search profiles 300 to the second user on the geo-spatial map 200. Further, the job management module 108 may be configured to obtain a second search parameter from the second user and obtain the job search profiles 300 based on the second search radius 204 and the second search parameter.
The geo-spatial map 200 may graphically display member data (e.g., name and/or address) associated with the members 106A-N (e.g., may include candidates, employers, job consultants, etc.). For example, the member data may include candidate data corresponding to a job search profile 300 and/or employer data corresponding to the employer profile 400. The welcome message 202 may display a unique identifier (e.g., first name, last name, user name, code, etc.) of the user associated with the webpage. In other words, the welcome message 202 may be displayed to the user upon logging into the webpage.
The search radius 204 may be a distance and/or a travel time obtained from the user associated with the job search profile 300. The user may perform an employer profiles search within the search radius 204. In one example embodiment, the search radius 204 may be associated with a location obtained from the user. The user profile block 206 may display profile information associated with the user (e.g., job seeker), performing a job search within the search radius 204. For example, the profile information may include name, address and/or location associated with the user. The search option 208 may enable the user to search the employer profiles 400 within a specified radius (e.g., the search radius 204 of
The narrow search by category option 210 may enable the user to perform a narrow search associated with the employer profiles 400 within the search radius 204 based on a job category (e.g., finance, information technology, legal, marketing, etc.). The narrow search by keyword(s) option 212 may enable the user to search employer profiles within the search radius 204 using keywords (e.g., doctor, project manager, patent analyst, junior software engineer, etc.) associated with the job category.
The change your location option 214 may enable the user to search employer profiles 400 associated with other locations on the geo-spatial map 200. In one example embodiment, the user may specify a different search radius 204 while changing the location associated with the job search. The create a new job search profile option 216 may enable the user to create, modify and/or update profile information and/or preferences in order to obtain desired employers within the search radius 204 associated with the location. The employer profile block 218 may display profile information associated with the employer located within the search radius 204.
In the example embodiment illustrated in
The user profile block 206 displays name of the user “John Q. Public” and address “1488 Oak Hill Drive, Cupertino, Calif., United States”. For example, John Q. Public may search employers (e.g., recruiting financial analyst) within a search radius of 0.6 mile using the search option 208. In addition, John Q. Public may narrow down the job search by specifying category as “Finance” and keyword as “Analyst”. In one example embodiment, John Q. Public is searching for employer recruiting Financial Analyst within the search radius 204 associated with location obtained from the user on a geo-spatial map 200.
The employer profile block 218 displays search radius 204 “0.5 mile”. designation “Financial Analyst” and name and address of the employer “ABC Investments, 1000 Oak Hill Drive, Cupertino, Calif., United States” based on the search request of John Q. Public. As illustrated in the example embodiment of
For example, a location (e.g., may include a non-residential location) associated with the job search profile 300 may be determined based on the candidate data. A search request from the user associated with the job search profile 300 may be processed (e.g., using the job management module 108 of
The employer profile 400 may be obtained (e.g., through employer repository 112 of
The search option 220 may enable the user (e.g., employer) to search candidate profiles within a threshold search radius (e.g., 0.25 miles, 0.5 miles, 0.75 miles, etc.). The create a new employer profile option 222 may enable the user (e.g., the employer) to perform functions like posting, updating and/or editing job listings in the employer profiles 400 (e.g., to find potential employees). The profile block 224 may display profile information associated with the candidate based on a search request of the user. For example, the profile information may include name, address, profession, etc.
In the example embodiment illustrated in
The profile block 224 displays distance of separation “0.3 mile”, name of candidate “Joe Jones”, occupation “Plumber” and address “1200 Oak Hill Drive, Cupertino, Calif., United States”. As illustrated in the example embodiment of
In one example embodiment, John Q. Public searches employer profiles (e.g., using the search parameters) associated with the location (Oak Hill Drive) within a specified search radius 204 and/or commute time from John Q. Public's location (e.g., as illustrated in
The welcome message 226 may display a unique identifier (e.g., name, user name, slogan, logo, code, etc.) of entity (e.g., company, business, organization, etc.) associated with the webpage. For example, the entity may be a user (e.g., employer) searching candidates associated with the job search profile 300 within a specified radius on the geo-spatial map 200. The employer profile block 228 may display profile details (e.g., name, address, and/or other information) associated with the entity conducting the candidate search.
The candidate profile block 230 may display profile information (e.g., may include name, address, profession, distance of separation, etc.) associated with the candidate corresponding to the search request of the entity (e.g., user). The search option 232 may enable the entity to search for the candidates associated with the job search profiles 300 within a specified radius associated with the location.
In the example embodiment illustrated in
For example, Apple, Inc. may search for sales executives within a search radius of 0.5 miles using the search option 232. Apple, Inc. may narrow down the search candidate search by specifying category as “Sales” and keyword as “Manager”. In one example embodiment, Apple, Inc. is searching for the sales executive within 0.5 miles from the location of the entity.
The candidate profile block 230 displays distance from the location “0.25 mile”, name of candidate “Mary Smith, Sales Executive”, address “123 Main St., Cupertino, Calif., United States” located 0.25 mile away from the location associated with Apple, Inc. If the desired job search profile(s) 300 is not obtained within the search radius 204 of 0.5 mile, the entity may search for the desired job search profiles 300 in other locations on the geo-spatial map 200 using the change your location option 214. In addition, Apple, Inc. may create, modify, and/or update the profile using the create a new employer profile option 222.
In accordance with one or more embodiments, a location associated with the employer profile 400 may be determined (e.g., using the job management module 108 of
The block diagram may display a name of a candidate in the name block 302, a location information in the location block 304, an education level in the education block 306, an experience level associated with the candidate in the experience block 308. The resume block 310 may display details which include summary or listing of relevant job experience and/or education usually displayed for the purpose of searching jobs (e.g., through community network 102 of
In the example embodiment illustrated in
The block diagram may display a name of an employer in the employer name block 402, location information in the location block 404, qualification details required in the education block 406, an experience level in the experience block 408. The job title block 410 may display a type of occupation and/or requirement associated with the employer profile. For example, the type of occupation may include work time, type of field such as marketing, software, patent, etc. The job description block 412 may display a summary of a job, including the nature of work performed (e.g., duties and/or responsibilities), working conditions, key duration roles and/or level (e.g., skill, effort, etc.).
The compensation block 414 may display a list of compensations (e.g., base salary, shot-term incentives, long-term incentives, employee benefits, perquisites, relocation charges, etc.) associated with the job. The employer description block 416 may include background, history and/or details associated with an entity (e.g., patron, company, business, organization, etc.). The candidate preferences block 418 may enable the employers to specify preferences (e.g., may include nature of job, field, job location, salary, etc.) corresponding to the employer profile 400. Candidates (e.g., job seekers) may search desired position (e.g., desired job) based on the preferences specified in the candidate preferences block 418. In one example embodiment, the candidate preferences block 418 may include preferences such as age, expertise level, location, commitment level, willingness to work in night shifts, proficiency levels, etc.
In the example embodiment illustrated in
In operation 506, the job search profile 300 is stored in a candidate repository (e.g., the candidate repository 114 of
In operation 512, search parameters are obtained from the candidate. For example, the search parameter may include a job category, job type, keyword, salary range, experience level, and/or education level, etc. In operation 514, employer profiles 400 are obtained based on the search radius 204 and the search parameters. For example, the employer profiles 400 may be displayed within the search radius 204 on the geo-spatial map 200 (e.g., corresponding to the search parameters and the search radius 204 specified by the candidate).
In operation 516, the employer profiles 400 are displayed on the geo-spatial map 200 (e.g., using the job management module 108 of
In operation 604, a location of the employer profile 400 is determined (e.g., using the geo-spatial repository 110 and the employer repository 112 of
In operation 612, the search parameters are obtained. For example, the search parameters may include a job category, job type, keyword, salary range, experience level, and/or education level, etc. In operation 614, the job search profiles 300 are obtained (e.g., using the job management module 108 of
In operation 616, the job search profiles 300 are displayed on a geo-spatial map (e.g., the geo-spatial map 200 of
The diagrammatic system view 700 may indicate a personal computer and/or a data processing system in which one or more operations disclosed herein may be performed. The processor 702 may be a microprocessor, a state machine, an application-specific integrated circuit, a field programmable gate array, etc. (e.g., Intel® Pentium® processor). The main memory 704 may be a dynamic random access memory and/or a primary memory of a computer system. The static memory 706 may be a hard drive, a flash drive, and/or other memory information associated with the data processing system.
The bus 708 may be an interconnection between various circuits and/or structures of the data processing system. The video display 710 may provide graphical representation of information on the data processing system. The alpha-numeric input device 712 may be a keypad, a keyboard and/or any other input device of text (e.g., a special device to aid the physically challenged). The cursor control device 714 may be a pointing device such as a mouse.
The drive unit 716 may be the hard drive, a storage system, and/or other longer term storage subsystem. The signal generation device 718 may be a bios and/or a functional operating system of the data processing system. The network interface device 720 may be a device that may perform interface functions such as code conversion, protocol conversion and/or buffering required for communication to and from a network.
The machine readable medium 722 may provide instructions on which any of the methods disclosed herein may be performed. The instructions 724 may provide source code and/or data code to the processor 702 to enable any one or more operations disclosed herein.
In operation 804, a location associated with the job search profile 300 may be determined (e.g., using the geo-spatial repository 10 of
In operation 810, a search radius (e.g., the search radius 204 of
In operation 906, the employer profile 400 may be stored in an employer repository (e.g., the employer repository 112 of
Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. For example, the various devices, modules, analyzers, generators, etc. described herein may be enabled and operated using hardware circuitry (e.g., CMOS based logic circuitry), firmware, software and/or any combination of hardware, firmware, and/or software (e.g., embodied in a machine readable medium). For example, the various electrical structure and methods may be embodied using transistors, logic gates, and electrical circuits (e.g., Application Specific Integrated Circuitry (ASIC) and/or in Digital Signal Processor (DSP) circuitry). For example, the job management module 108, and other modules of
In addition, it will be appreciated that the various operations, processes, and methods disclosed herein may be embodied in a machine-readable medium and/or a machine accessible medium compatible with a data processing system (e.g., a computer system), and may be performed in any order. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.