Difference between revisions of "Career Endeavors"

From CNM Wiki
Jump to: navigation, search
(Job search as a waterfall)
 
(57 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[File:Careerprise td.png|200px|thumb|[[Careerprise]]'s trade mark]][[File:Educaship-pipeline.png|400px|thumb|right|[[WorldOpp Pipeline]]]][[Career Projects]] is the second [[presentation]] in the [[Introduction to Careers]] lecture. The lecture itself is the fourth in [[WorldOpp Orientation]]. Consequently, the ''[[WorldOpp Orientation|Orientation]]'' is the first stage of [[WorldOpp Pipeline]].
+
[[File:Cnm-digital.png|400px|thumb|right|[[CNMCyber suite]]s]]The [[Career Endeavors]] (hereinafter, the ''Lesson'') is the [[lesson]] of [[CNMCyber]] that introduces its participants to [[career project]]s and related topics. The ''Lesson'' belongs to the '''[[Introduction to Careers]]''' session of [[EmployableU Concepts]].
  
This wikipage presents its full script and those test questions that are related to that presentation.  
+
The ''Lesson'' is made up of five [[lectio]]s. At [[CNMCyber]], the word, [[lectio]], is used for a lesson part.
  
  
==Script==
+
==Summaries==
The video of the presentation is published at https://youtu.be/lT20y2GMJws (12:39). Here is its full text.
+
===Predecessor===
 +
:The predecessor lesson is [[Employability Essentials]].
 +
 
 +
===Outline===
 +
:{|class="wikitable" width=100% style="text-align:center;"
 +
|+[[Career Endeavors]]
 +
|width=25%|[[Lectio]]s
 +
!#!!Referred topics
 +
|-
 +
![[What Career Endeavor Is]]
 +
|1||[[Career project]], [[career endeavor]], [[career operations]]
 +
|-
 +
![[Career Waterfalls]]
 +
|2||[[Career waterfall]]
 +
|-
 +
![[Agile Career Projects]]
 +
|3||[[Agile career project]], [[Agile methodology]]
 +
|-
 +
![[Job Search Map]]
 +
|4||[[Agile job-search map]]
 +
|-
 +
![[Job Search Pivots]]
 +
|5||[[Startup pivot]], [[effectiveness]], [[efficiency]]
 +
|}
 +
 
 +
===Successor===
 +
:The successor lesson is [[Employment Credentials]].
 +
 
 +
==2019 Career Projects presentation==
 +
The video of the presentation is published on https://youtu.be/CVwp6WAAiYo (7:33). Here is its full text.
  
 
===Overview===
 
===Overview===
:Welcome to ''Career Projects''. In this brief presentation, we are going to define [[project]]s and take a look at two methods that [[employment candidate]]s can use in order to land their promising jobs. Let's go.
+
:Welcome to ''Career Projects''. In this brief presentation, we are going to define [[project]]s and take a look at two major methods that [[employment candidate]]s can use in order to land their promising jobs.
  
 
===What a project is===
 
===What a project is===
:[[File:Solution-project.png|400px|thumb|[[Problem]], [[solution]], and [[project]]]]What may [[employment candidate]]s borrow from [[business administration]] in order to advance their [[career]]s? [[Project]]s are an obvious choice.
+
:[[File:Solution-project.png|400px|thumb|[[Problem]], [[solution]], and [[project]]]]Let's start with a question. What may [[employment candidate]]s borrow from [[business administration]] practices in order to advance their [[career]]s? [[Project]]s are an obvious choice.
 +
 
 +
:[[Enterprise]]s tend to run two types of operations -- ones are ongoing, established, repetitive, and the others aim to create something new.
 +
 
 +
:Is your [[employment]] established or desired? If desired, we can state that you are in a [[project]] of landing your job.
  
:[[Enterprise]]s tend to run two types of operations -- one is ongoing, established, repetitive, and the other aim to create something new. Is [[employment]] desired? If so, we can state that you are in a [[project]] of landing your job.
+
:To understand projects better, let's take a look at the available illustration.
  
:To understand projects better, let's take a look at the available illustration. There are two statuses -- one on the upper left is as it is and another on the upper right is to be. The difference between these two is called a [[problem]] to be solved. There should be some [[solution]], but usually that [[solution]] needs to be yet identified.
+
:There are two statuses -- one on the upper left is as it is and another on the upper right is to be. The difference between these two is called a [[problem]] to be solved. There should be some [[solution]], but usually that [[solution]] needs to be yet identified.
  
:Many [[project]]s are nesting. Solving a [[problem]] is a [[project]], but creating a [[solution]] or even development of an idea for the solution are by the definition [[project]]s too. To indicate that they are parts of a bigger [[project]]s, they can be called [[project phase]]s. And all of them include one or more [[process]]es, which can be considered as the smallest project.
+
:Many [[project]]s are nesting. Solving a [[problem]] is a [[project]], but creating a [[solution]] or even development of an idea for the solution are by the definition [[project]]s too. To indicate that they are parts of a bigger [[project]]s, they can be called [[project phase]]s. And all of them include one or more [[process]]es, which can be considered as the smallest of projects.
  
 
===What a process is===
 
===What a process is===
 
:[[File:Process.png|400px|thumb|[[Process]]]]To dig into [[project]]s deeper, let's take a quick look at the model of a [[process]].
 
:[[File:Process.png|400px|thumb|[[Process]]]]To dig into [[project]]s deeper, let's take a quick look at the model of a [[process]].
  
:A [[process]] is a sequence of activities undertaken in order to achieve particular results. [[Systems engineer]]s may also define a [[process]] as converting [[input]]s into [[output]]s using some tools and techniques while being influenced by enterprise factors.
+
:A [[process]] is a sequence of activities undertaken in order to achieve particular results. [[Systems engineer]]s may also define a [[process]] as converting [[input]]s into [[output]]s using some assets such as data, tools, and techniques while being influenced by enterprise factors.
  
:Does it sound complicated? If you collected all available information and need to create an idea of a solution, your time would be an input, information would be your tool, decision-making methods would be your techniques, legal and ethical considerations can be your factors, and an idea would be your output.
+
:Does it sound complicated? If you need to create an idea of a solution, your time would be an input, all collected available information, as well as your decision-making skills would be your assets, legal and ethical considerations can be your factors, and an idea would be your output.
  
 
===Project administration===
 
===Project administration===
Line 32: Line 65:
 
:[[File:Career-waterfall.png|400px|thumb|[[Career waterfall]]]] A traditional model is called the [[career waterfall]]. Many [[career counselor]]s may recommend this route.
 
:[[File:Career-waterfall.png|400px|thumb|[[Career waterfall]]]] A traditional model is called the [[career waterfall]]. Many [[career counselor]]s may recommend this route.
  
:[[Waterfall model|Waterfall]] refers to a sequential process where progress is seen as flowing steadily downwards through the phases. These phases may vary, but often consist of, a, discovering one's [[vocation]], bee, suggesting one's target [[occupation]], see, identifying [[work-related competence]] needed for a particular position, dee, development of one's [[KSA]]s, ee, development one's [[employment credential]]s, eff, job search, gee, adjustments to the job market, and, aitch, landing one's job in the target [[occupation]].
+
:[[Waterfall model|Waterfall]] refers to a sequential process where progress is seen as flowing steadily downwards through the phases.
 +
 
 +
:These phases may vary, but, when they come to careers, they often consist of, a, discovering one's [[vocation]], bee, suggesting one's target [[occupation]], see, identifying [[work-related competence]] needed for a particular position, dee, development of one's [[KSA]]s, ee, development one's [[employment credential]]s, eff, job search, and, eventually, landing one's job in the target [[occupation]].
  
===Meet Lisa===
+
===Lisa in Waterfall===
:Let's add some real life example; just the name is changed to preserve the privacy. Meet Lisa, who used to believe that management was her vocation. Her parents believed in that too. She attended a college for 4 years to earn an [[academic credential]] in operations management with concentration in managerial accounting, but no one wanted to hire her because of her lack of [[work experience]]. She started working as a sales representative and eventually stays in that [[occupation]] till now. She doesn't regret about her 4 years in a college, and says that it was fun, but she has never managed any operations using managerial accounting in her career.
+
:Let's add some real life example; just the name is changed to preserve the privacy. Meet Lisa, who used to believe that management was her vocation. She also felt sympathy to accounting. Her parents believed in that too. She attended a college for 4 years to earn an [[academic credential]] in operations management with concentration in managerial accounting, but no one wanted to hire her because of her lack of [[work experience]]. She started working as a sales representative and eventually stays in that [[occupation]] the most of her professional life. She doesn't regret about her 4 years in a college, and says that it was fun, but she has never managed any operations using managerial accounting in her career.
  
 
:That example is not everyone's case, and some waterfall projects can be successful, but there is no way that everything in that many-years project would go as planned and a great chunk of time -- and often money -- wouldn't be wasted.
 
:That example is not everyone's case, and some waterfall projects can be successful, but there is no way that everything in that many-years project would go as planned and a great chunk of time -- and often money -- wouldn't be wasted.
  
 
===Agile job search===
 
===Agile job search===
:[[File:Iteration-backlog.png|400px|thumb|right|[[Iterative development]]]][[File:Scrum.png|400px|thumb|right|[[Sprint]]]][[Agile methodology|Agile]] is another [[methodology]] of administering [[project]]s. An [[Agile project]] is usually completed in several [[iteration]]s. In different models these development cycles can also be called [[sprint]]s and scrums. The results of each iteration shall be used to setup objectives for other iterations. So, instead of one huge and costly project without clear understanding of its outcome, the [[Agile methodology]] offers many smaller trials and, sometimes, fails in order to clarify objectives while on the way.
+
:[[File:Iteration-backlog.png|400px|thumb|right|[[Iterative development]]]][[Agile methodology|Agile]] is another [[methodology]] of administering [[project]]s. An [[Agile project]] is usually completed in several [[iteration]]s. In different models these development cycles can also be called [[sprint]]s and scrums.
 +
 
 +
:The results of each iteration shall be used to setup objectives for other iterations. So, instead of one huge and costly project without clear understanding of its outcome, the [[Agile methodology]] offers many smaller trials and, sometimes, fails in order to clarify objectives while on the way.
 +
 
 +
===Lisa in Agile===
 +
:[[File:Scrum.png|400px|thumb|right|[[Sprint]]]]Let's imagine that Lisa from the example above used [[Agile methodology|Agile]]. She had some [[vocation]] for management and accounting. Not to start from scratch, she also had some [[knowledge, skills, and abilities]]. She probably knew at least 50% of basic [[bookkeeping]] from her first semester in her college.
 +
 
 +
:In the tax season, she could have started looking for a job of an entry-level [[bookkeeper]]. If it is not the tax season, she could [[volunteer]] as a [[manager]] and or [[bookkeeper]], so she would test whether those fit her [[vocation]]. She will put her hands on something she dreamed about and have a feeling whether she wants to continue or do something that in the [[Agile methodology]] is called "pivot."
 +
 
 +
:At any rate, in 4 years, Lisa would have a 4-year degree, 3 years of experience and an actual job.
 +
 
 +
:The most important feature of the [[Agile methodology|Agile]] is that a big project is chunked in many smaller ones and results in one can define objectives for another.
 +
 
 +
===Summary===
 +
:This concludes the ''Career Projects'' presentation. We have defined [[project]]s and taken a look at the [[career waterfall]] and [[Agile methodology]]. If you haven't done yet so, you are now welcome to move to the ''Job Search Map''.
 +
 
 +
==2019 Job Search Map presentation==
 +
The video of the presentation is published on https://youtu.be/U1UxuoMqSg4 (4:23). Here is its full text.
 +
 
 +
===Overview===
 +
:Welcome to ''Job Search Map''. In this brief presentation, we are going to review the [[Agile job-search map]] and take a look at how employment candidates can use that in order to land their promising jobs. Let's go.
  
 
===Agile career project===
 
===Agile career project===
:[[File:Career-administration.png|400px|thumb|[[Agile career-administration model]]]]The goal of the [[Agile career-administration model]] is to navigate [[employment candidate]]s. We can see the talent level is on the top, the career service one in the middle, and the job vacancy level is on the bottom.
+
:[[File:Career-administration.png|400px|thumb|[[Agile job-search map]]]]The goal of the [[Agile job-search map]] is to navigate [[employment candidate]]s in their job search. We can see the talent level is on the top, the career service one in the middle, and the job vacancy level is on the bottom.
 
 
:Let's go over this [[Agile career-administration model|model]] using Lisa's example. She had some [[vocation]] and thought that she would be paid well and would do that for a long time. Not to start from scratch, she also had some [[knowledge, skills, and abilities]] known as [[KSA]]s. There is no single path. However, if she knew like 50% of basic [[bookkeeping]] from her first semester in her college, she could have started looking for a job of an entry-level [[bookkeeper]] in the tax season. Even if she worked as a [[volunteer]], she would test whether [[bookkeeping]] fits his [[vocation]]. If she liked it, she could switch her major to accounting or anything else. In 4 years, Lisa would have a 4-year degree, 3 years of experience and an actual job.
 
  
:Employment suggestions is the place which can match you to your target job. These target jobs have some requirements, which can be expressed as [[KSA]]s.  
+
:This map has two hubs in its career service level. Employment suggestions is the place which is needed to match three things -- [[vocation]], existing [[knowledge, skills, and abilities]], and available positions on the [[job market]]. The existing [[knowledge, skills, and abilities]] are assessed through their analysis, which is marked as KSA analysis.
  
:A particular bookkeeping job pretty much always has its requirements -- its defines what their [[bookkeeper]] needs to known, what be skilled at, and what be able to do. Let say, [[Educaship Alliance LLC]] hires someone who needs to know [[debit]]s and [[credit]]s, as well to be able to do [[income statement]]s and [[balance sheet]]s. These [[KSA]]s should be compared with those [[KSA]]s which Lisa already has and the gaps can be found. Let's assume that Lisa knows and is able everything that the employer looks for, besides [[income statement]]s. To fill in this void is his gap project. Lisa can start to concentrate on [[income statement]]s in order to add it to his "toolbox."
+
:The target position comes with its KSA requirements that shall be compared against existing [[knowledge, skills, and abilities]] in order to identify gaps, and, consequently, formulate gap projects.
  
:Usually someone needs to credential you in order to get a job, and any recruiter will look for your credentials. You cannot say you know everything in a particular field, someone needs to prove it. Sometimes some employment credentials include academic degrees, some are not. When [[employment credential]]s are setup, it can lead to a job interview, which can be considered as a credential too.  
+
:For instance, [[Educaship Alliance LLC]] hires [[bookkeeper]]s who needs to know [[debit]]s and [[credit]]s, as well to be able to do [[income statement]]s and [[balance sheet]]s. Let's assume that someone has everything, but [[income statement]]s. To complete the gap project, this someone can review [[income statement]]s in order to add it to his or her skill set.
  
:Back to the example, [[Educaship Alliance LLC]] may give Lisa some [[work sample test]] -- let say, accomplish an [[income statement]]. If Lisa does so, she may land the job. Then, he will put his hands on and have a feeling whether he wants to continue or do something that in [[Agile methodology]] is called "pivot."
+
:[[Employment credential]]s is another hub. Someone or something needs to credential you in order to get a job. Usually, minimum requirements need to be met in order to get a [[job interview]]. A few credentials can be earned during the interview as well.
  
:The most important feature of the [[Agile career-administration model]] is that a big project is chunked in many smaller ones and results in one can define objectives for another.
+
:The most important feature of the [[Agile job-search map]] is that a big project is chunked in many smaller ones and results in one can define objectives for another. For instance, the landed job may redefine one's [[vocation]], [[employment credential]]s feed employment suggestions, and so on.
  
===Effectiveness versus efficiency===
+
===Effectiveness vs efficiency===
:Let's get back to the [[Agile career-administration model|Agile model]]. We can see that the endeavors on the left lay in the effectiveness zone, while the one on the right do in the efficiency zone. With regard to [[career]]s, [[effectiveness]] refers to targeting right jobs and [[efficiency]] refers to landing jobs faster. The left side of this illustration is about choosing the direction to go and the right side is about actually going.
+
:The [[Agile job-search map|Agile map]] prompts that the endeavors on the left lay in the effectiveness zone, while the one on the right do in the efficiency zone. With regard to [[career]]s, [[effectiveness]] refers to targeting right jobs and [[efficiency]] refers to landing jobs faster. The left side of this illustration is about choosing the direction to go and the right side is about actually going.
  
 
:[[File:Efficiency-effectiveness.png|400px|thumb|[[Efficiency]] vs [[effectiveness]]]]Now, let's go to another illustration. This matrix displays what may happen if you go fast in a wrong direction. You are just investing your time and effort into your career "death."
 
:[[File:Efficiency-effectiveness.png|400px|thumb|[[Efficiency]] vs [[effectiveness]]]]Now, let's go to another illustration. This matrix displays what may happen if you go fast in a wrong direction. You are just investing your time and effort into your career "death."
Line 65: Line 118:
  
 
===Summary===
 
===Summary===
:This concludes the ''Career Projects'' presentation. We have defined [[project]]s and taken a look at the [[career waterfall]]. We have also used the [[Agile career-administration model]] to go over endeavors that [[employment candidate]]s may undertake in order to land their jobs. The special stress was made on the difference between [[efficiency]] and [[effectiveness]] in [[career administration]]. If you haven't done yet so, you are now welcome to move to [[Job Search Map]].
+
:This concludes the ''Job Search Map'' presentation. We have reviewed the [[Agile job-search map]] and taken a look at those endeavors that [[employment candidate]]s may undertake in order to land their jobs. The special stress was made on the difference between [[efficiency]] and [[effectiveness]] in [[career administration]]. If you haven't done yet so, you are now welcome to move to [[Employment Credentials]].
 
 
==Quiz questions==
 
:Every statement below is split into one true and one false question in the actual exam.
 
 
 
==See also==
 
*[[Job Search Map]]. The third [[presentation]] in [[Introduction to Careers]].
 
*[[Career Essentials]]. The first [[presentation]] in [[Introduction to Careers]].
 
  
 
[[Category: Orientation Curriculum]][[Category:Presentations]]
 
[[Category: Orientation Curriculum]][[Category:Presentations]]

Latest revision as of 19:29, 29 October 2023

The Career Endeavors (hereinafter, the Lesson) is the lesson of CNMCyber that introduces its participants to career projects and related topics. The Lesson belongs to the Introduction to Careers session of EmployableU Concepts.

The Lesson is made up of five lectios. At CNMCyber, the word, lectio, is used for a lesson part.


Summaries

Predecessor

The predecessor lesson is Employability Essentials.

Outline

Career Endeavors
Lectios # Referred topics
What Career Endeavor Is 1 Career project, career endeavor, career operations
Career Waterfalls 2 Career waterfall
Agile Career Projects 3 Agile career project, Agile methodology
Job Search Map 4 Agile job-search map
Job Search Pivots 5 Startup pivot, effectiveness, efficiency

Successor

The successor lesson is Employment Credentials.

2019 Career Projects presentation

The video of the presentation is published on https://youtu.be/CVwp6WAAiYo (7:33). Here is its full text.

Overview

Welcome to Career Projects. In this brief presentation, we are going to define projects and take a look at two major methods that employment candidates can use in order to land their promising jobs.

What a project is

Let's start with a question. What may employment candidates borrow from business administration practices in order to advance their careers? Projects are an obvious choice.
Enterprises tend to run two types of operations -- ones are ongoing, established, repetitive, and the others aim to create something new.
Is your employment established or desired? If desired, we can state that you are in a project of landing your job.
To understand projects better, let's take a look at the available illustration.
There are two statuses -- one on the upper left is as it is and another on the upper right is to be. The difference between these two is called a problem to be solved. There should be some solution, but usually that solution needs to be yet identified.
Many projects are nesting. Solving a problem is a project, but creating a solution or even development of an idea for the solution are by the definition projects too. To indicate that they are parts of a bigger projects, they can be called project phases. And all of them include one or more processes, which can be considered as the smallest of projects.

What a process is

To dig into projects deeper, let's take a quick look at the model of a process.
A process is a sequence of activities undertaken in order to achieve particular results. Systems engineers may also define a process as converting inputs into outputs using some assets such as data, tools, and techniques while being influenced by enterprise factors.
Does it sound complicated? If you need to create an idea of a solution, your time would be an input, all collected available information, as well as your decision-making skills would be your assets, legal and ethical considerations can be your factors, and an idea would be your output.

Project administration

Administering projects particularly includes sequencing processes, and project phases that are required in order to accomplish a project. There are several approaches and, in this presentation, we will consider two major ones.

Job search as a waterfall

A traditional model is called the career waterfall. Many career counselors may recommend this route.
Waterfall refers to a sequential process where progress is seen as flowing steadily downwards through the phases.
These phases may vary, but, when they come to careers, they often consist of, a, discovering one's vocation, bee, suggesting one's target occupation, see, identifying work-related competence needed for a particular position, dee, development of one's KSAs, ee, development one's employment credentials, eff, job search, and, eventually, landing one's job in the target occupation.

Lisa in Waterfall

Let's add some real life example; just the name is changed to preserve the privacy. Meet Lisa, who used to believe that management was her vocation. She also felt sympathy to accounting. Her parents believed in that too. She attended a college for 4 years to earn an academic credential in operations management with concentration in managerial accounting, but no one wanted to hire her because of her lack of work experience. She started working as a sales representative and eventually stays in that occupation the most of her professional life. She doesn't regret about her 4 years in a college, and says that it was fun, but she has never managed any operations using managerial accounting in her career.
That example is not everyone's case, and some waterfall projects can be successful, but there is no way that everything in that many-years project would go as planned and a great chunk of time -- and often money -- wouldn't be wasted.

Agile job search

Agile is another methodology of administering projects. An Agile project is usually completed in several iterations. In different models these development cycles can also be called sprints and scrums.
The results of each iteration shall be used to setup objectives for other iterations. So, instead of one huge and costly project without clear understanding of its outcome, the Agile methodology offers many smaller trials and, sometimes, fails in order to clarify objectives while on the way.

Lisa in Agile

Let's imagine that Lisa from the example above used Agile. She had some vocation for management and accounting. Not to start from scratch, she also had some knowledge, skills, and abilities. She probably knew at least 50% of basic bookkeeping from her first semester in her college.
In the tax season, she could have started looking for a job of an entry-level bookkeeper. If it is not the tax season, she could volunteer as a manager and or bookkeeper, so she would test whether those fit her vocation. She will put her hands on something she dreamed about and have a feeling whether she wants to continue or do something that in the Agile methodology is called "pivot."
At any rate, in 4 years, Lisa would have a 4-year degree, 3 years of experience and an actual job.
The most important feature of the Agile is that a big project is chunked in many smaller ones and results in one can define objectives for another.

Summary

This concludes the Career Projects presentation. We have defined projects and taken a look at the career waterfall and Agile methodology. If you haven't done yet so, you are now welcome to move to the Job Search Map.

2019 Job Search Map presentation

The video of the presentation is published on https://youtu.be/U1UxuoMqSg4 (4:23). Here is its full text.

Overview

Welcome to Job Search Map. In this brief presentation, we are going to review the Agile job-search map and take a look at how employment candidates can use that in order to land their promising jobs. Let's go.

Agile career project

The goal of the Agile job-search map is to navigate employment candidates in their job search. We can see the talent level is on the top, the career service one in the middle, and the job vacancy level is on the bottom.
This map has two hubs in its career service level. Employment suggestions is the place which is needed to match three things -- vocation, existing knowledge, skills, and abilities, and available positions on the job market. The existing knowledge, skills, and abilities are assessed through their analysis, which is marked as KSA analysis.
The target position comes with its KSA requirements that shall be compared against existing knowledge, skills, and abilities in order to identify gaps, and, consequently, formulate gap projects.
For instance, Educaship Alliance LLC hires bookkeepers who needs to know debits and credits, as well to be able to do income statements and balance sheets. Let's assume that someone has everything, but income statements. To complete the gap project, this someone can review income statements in order to add it to his or her skill set.
Employment credentials is another hub. Someone or something needs to credential you in order to get a job. Usually, minimum requirements need to be met in order to get a job interview. A few credentials can be earned during the interview as well.
The most important feature of the Agile job-search map is that a big project is chunked in many smaller ones and results in one can define objectives for another. For instance, the landed job may redefine one's vocation, employment credentials feed employment suggestions, and so on.

Effectiveness vs efficiency

The Agile map prompts that the endeavors on the left lay in the effectiveness zone, while the one on the right do in the efficiency zone. With regard to careers, effectiveness refers to targeting right jobs and efficiency refers to landing jobs faster. The left side of this illustration is about choosing the direction to go and the right side is about actually going.
Now, let's go to another illustration. This matrix displays what may happen if you go fast in a wrong direction. You are just investing your time and effort into your career "death."
At the same time, most of professional workforce service providers concentrate on efficiency -- résumés, interviewing skills, and so on. Of course, it is helpful to those job seekers who know their direction. There is a chance that the others play a Russian roulette, which is a lethal game of chance -- the options are to stay alive or die.

Summary

This concludes the Job Search Map presentation. We have reviewed the Agile job-search map and taken a look at those endeavors that employment candidates may undertake in order to land their jobs. The special stress was made on the difference between efficiency and effectiveness in career administration. If you haven't done yet so, you are now welcome to move to Employment Credentials.