Mixing
What level of competency does the term “Working Knowledge†describe?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
22
down vote
favorite
I started looking for jobs today and I encountered the term "working knowledge". I do not really understand what the term means and I am wondering what kind of tasks I would be expected to do with "working knowledge" of given software/language.
Specifically, the job post i saw asked for "working knowledge of Assembly language". I had an encounter with the Assembly language when I worked through the Raspberry Pi "Baking Pi" tutorial where the goal is to write very simple OS in assembly. However, I have never done any coding of my own in the language so I do not feel like I could do any useful work with my assembly knowledge.
job-search job-description
edited Mar 26 '14 at 8:47
Rhys
5,73623558
asked Mar 25 '14 at 18:04
BoZenKhaa
213126
add a comment |Â
up vote
22
down vote
favorite
I started looking for jobs today and I encountered the term "working knowledge". I do not really understand what the term means and I am wondering what kind of tasks I would be expected to do with "working knowledge" of given software/language.
Specifically, the job post i saw asked for "working knowledge of Assembly language". I had an encounter with the Assembly language when I worked through the Raspberry Pi "Baking Pi" tutorial where the goal is to write very simple OS in assembly. However, I have never done any coding of my own in the language so I do not feel like I could do any useful work with my assembly knowledge.
job-search job-description
edited Mar 26 '14 at 8:47
Rhys
5,73623558
asked Mar 25 '14 at 18:04
BoZenKhaa
213126
" I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
– Tom Au
Sep 20 '14 at 22:55
Also see workplace.stackexchange.com/q/48730/18555
– Pacerier
Jul 10 '15 at 9:25
add a comment |Â
up vote
22
down vote
favorite
up vote
22
down vote
favorite
I started looking for jobs today and I encountered the term "working knowledge". I do not really understand what the term means and I am wondering what kind of tasks I would be expected to do with "working knowledge" of given software/language.
Specifically, the job post i saw asked for "working knowledge of Assembly language". I had an encounter with the Assembly language when I worked through the Raspberry Pi "Baking Pi" tutorial where the goal is to write very simple OS in assembly. However, I have never done any coding of my own in the language so I do not feel like I could do any useful work with my assembly knowledge.
job-search job-description
edited Mar 26 '14 at 8:47
Rhys
5,73623558
asked Mar 25 '14 at 18:04
BoZenKhaa
213126
I started looking for jobs today and I encountered the term "working knowledge". I do not really understand what the term means and I am wondering what kind of tasks I would be expected to do with "working knowledge" of given software/language.
Specifically, the job post i saw asked for "working knowledge of Assembly language". I had an encounter with the Assembly language when I worked through the Raspberry Pi "Baking Pi" tutorial where the goal is to write very simple OS in assembly. However, I have never done any coding of my own in the language so I do not feel like I could do any useful work with my assembly knowledge.
job-search job-description
edited Mar 26 '14 at 8:47
Rhys
5,73623558
asked Mar 25 '14 at 18:04
BoZenKhaa
213126
edited Mar 26 '14 at 8:47
Rhys
5,73623558
edited Mar 26 '14 at 8:47
Rhys
5,73623558
edited Mar 26 '14 at 8:47
Rhys
5,73623558
5,73623558
asked Mar 25 '14 at 18:04
BoZenKhaa
213126
asked Mar 25 '14 at 18:04
BoZenKhaa
213126
asked Mar 25 '14 at 18:04
BoZenKhaa
213126
213126
" I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
– Tom Au
Sep 20 '14 at 22:55
Also see workplace.stackexchange.com/q/48730/18555
– Pacerier
Jul 10 '15 at 9:25
add a comment |Â
" I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
– Tom Au
Sep 20 '14 at 22:55
Also see workplace.stackexchange.com/q/48730/18555
– Pacerier
Jul 10 '15 at 9:25
" I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
– Tom Au
Sep 20 '14 at 22:55
" I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
– Tom Au
Sep 20 '14 at 22:55
Also see workplace.stackexchange.com/q/48730/18555
– Pacerier
Jul 10 '15 at 9:25
Also see workplace.stackexchange.com/q/48730/18555
– Pacerier
Jul 10 '15 at 9:25
add a comment |Â
4 Answers
4
active
oldest
votes
up vote
25
down vote
accepted
As a senior level engineer (28 years experience) I've sat in on many interviews; generally when we ask a candidate about "working knowledge" in, for example, a programming language, we want to know if he/she can sit down and write functional program in that language. You don't need to be an expert, but you need to have done some real work with it, or used it extensively in school if you're a recent graduate.
Using the assembly language example you gave in your question, I probably would not rate you as having working knowledge. You'd get points for being exposed to it vs. a candidate who had never seen it before, but I'd keep it at that level on my resume.
answered Mar 25 '14 at 18:21
user17881
39422
1
What about being able to fluently code in something using reference materials? I've coded less or more briefly in a lot of things, have theoretical and some practical knowledge of pretty much all the concepts out there, etc. etc. I feel like that wouldn't really be enough in most people's books, even if I personally know that I could get up and running with the stuff fairly fast. I suppose that I should do some things in the languages relevant on the market before looking for jobs.
– Llamageddon
Nov 2 '14 at 0:48
@Asmageddon, People always code with "reference material" like Stackoverflow and code manuals / wiki. You don't actually expect people to rote-memorize everything do you? Or do you mean something else when you say "reference material"?
– Pacerier
Jul 10 '15 at 8:32
@Pacerier That is what I meant, thank you :)
– Llamageddon
Jul 11 '15 at 2:13
add a comment |Â
up vote
22
down vote
"Working Knowledge" reflects a low-level competency in an area - you will be expected to work with the tool, but not necessarily to be an expert in that tool.
If you don't feel like you would be able to build a full product with the tool, BUT you feel like you could, with a little trial-and-error, reconstruct it from an example, you probably have 'working knowledge' of that tool.
As long as you can use that tool on a daily basis, even if you don't know how to do everything with that tool or even the 'best practices' of using that tool, you can say you have working knowledge, and back it up with your experience (I would say having some experience with it while working on another app is close enough to put on a resume - but the job requires you have a stronger working knowledge of the code, you should probably learn it a bit better before beginning work there).
Working Knowledge: 1.A knowledge of how to make something work without any deeper understanding of why it works, or of how to fix it if it breaks
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
3
As per conversation in the water cooler, here's a source to back it, too: en.wiktionary.org/wiki/working_knowledge
– CMW
Mar 25 '14 at 18:35
@CMW Do you mind if I include that in my answer?
– Zibbobz
Mar 25 '14 at 18:51
@Zibbobz go for it. You wrote basically what I'd write if I wrote an answer.
– Elysian Fields♦
Mar 25 '14 at 19:39
@Zibbobz what enderland said. I stole the link from him.
– CMW
Mar 25 '14 at 19:53
@Zibbobz, Doesn't your answer actually contradict the other answer above with 23 upvotes?
– Pacerier
Jul 10 '15 at 8:34
 |Â
show 1 more comment
up vote
4
down vote
If you told me you had working knowledge of X, I would expect that I could assign you tasks to do with X and you could carry them out. You might be a bit slow at first due to having to ask questions, look things up, etc, but you know enough to have the framework for acquiring more knowledge organically. Without working knowledge in X, I would expect to have to give you some sort of training before you could carry out tasks to do with X.
If you wouldn't be happy to be hired on the basis of your knowledge of assembly language and given assembly language tasks without much "extra support" getting up to speed with assembly, then you don't have working knowledge of it.
answered Mar 25 '14 at 21:49
Ben
1435
1
Well, I would be very happy to be hired on the basis of my limited knowledge of assembly language as I very much enjoyed using it and I feel like this would be a great opportunity for me to spend more time with the subject. Possibly I posses the working knowledge in question then? :-)
– BoZenKhaa
Mar 25 '14 at 22:01
2
Not "spend more time with the subject" - can you work somehow productively on it on your first day? If not, then it's not yet 'working knowledge'.
– Peteris
Mar 25 '14 at 22:10
Yeah, right. Thanks, I misunderstood.
– BoZenKhaa
Mar 25 '14 at 22:24
add a comment |Â
up vote
1
down vote
"I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
"Working knowledge" of something, means that given a task in it, you could "take the ball and run with it," producing a "substantially complete" assignment. You might need some supervision at the front end, or some correction/editing/feedback at the back end, but you could bear the main burden of the task.
That doesn't seem to describe you. At best, you might be viewed as an "advanced beginner" or potential trainee.
answered Sep 20 '14 at 23:01
Tom Au
31928
add a comment |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
25
down vote
accepted
As a senior level engineer (28 years experience) I've sat in on many interviews; generally when we ask a candidate about "working knowledge" in, for example, a programming language, we want to know if he/she can sit down and write functional program in that language. You don't need to be an expert, but you need to have done some real work with it, or used it extensively in school if you're a recent graduate.
Using the assembly language example you gave in your question, I probably would not rate you as having working knowledge. You'd get points for being exposed to it vs. a candidate who had never seen it before, but I'd keep it at that level on my resume.
answered Mar 25 '14 at 18:21
user17881
39422
1
What about being able to fluently code in something using reference materials? I've coded less or more briefly in a lot of things, have theoretical and some practical knowledge of pretty much all the concepts out there, etc. etc. I feel like that wouldn't really be enough in most people's books, even if I personally know that I could get up and running with the stuff fairly fast. I suppose that I should do some things in the languages relevant on the market before looking for jobs.
– Llamageddon
Nov 2 '14 at 0:48
@Asmageddon, People always code with "reference material" like Stackoverflow and code manuals / wiki. You don't actually expect people to rote-memorize everything do you? Or do you mean something else when you say "reference material"?
– Pacerier
Jul 10 '15 at 8:32
@Pacerier That is what I meant, thank you :)
– Llamageddon
Jul 11 '15 at 2:13
add a comment |Â
up vote
25
down vote
accepted
As a senior level engineer (28 years experience) I've sat in on many interviews; generally when we ask a candidate about "working knowledge" in, for example, a programming language, we want to know if he/she can sit down and write functional program in that language. You don't need to be an expert, but you need to have done some real work with it, or used it extensively in school if you're a recent graduate.
Using the assembly language example you gave in your question, I probably would not rate you as having working knowledge. You'd get points for being exposed to it vs. a candidate who had never seen it before, but I'd keep it at that level on my resume.
answered Mar 25 '14 at 18:21
user17881
39422
1
What about being able to fluently code in something using reference materials? I've coded less or more briefly in a lot of things, have theoretical and some practical knowledge of pretty much all the concepts out there, etc. etc. I feel like that wouldn't really be enough in most people's books, even if I personally know that I could get up and running with the stuff fairly fast. I suppose that I should do some things in the languages relevant on the market before looking for jobs.
– Llamageddon
Nov 2 '14 at 0:48
@Asmageddon, People always code with "reference material" like Stackoverflow and code manuals / wiki. You don't actually expect people to rote-memorize everything do you? Or do you mean something else when you say "reference material"?
– Pacerier
Jul 10 '15 at 8:32
@Pacerier That is what I meant, thank you :)
– Llamageddon
Jul 11 '15 at 2:13
add a comment |Â
up vote
25
down vote
accepted
up vote
25
down vote
accepted
As a senior level engineer (28 years experience) I've sat in on many interviews; generally when we ask a candidate about "working knowledge" in, for example, a programming language, we want to know if he/she can sit down and write functional program in that language. You don't need to be an expert, but you need to have done some real work with it, or used it extensively in school if you're a recent graduate.
Using the assembly language example you gave in your question, I probably would not rate you as having working knowledge. You'd get points for being exposed to it vs. a candidate who had never seen it before, but I'd keep it at that level on my resume.
answered Mar 25 '14 at 18:21
user17881
39422
As a senior level engineer (28 years experience) I've sat in on many interviews; generally when we ask a candidate about "working knowledge" in, for example, a programming language, we want to know if he/she can sit down and write functional program in that language. You don't need to be an expert, but you need to have done some real work with it, or used it extensively in school if you're a recent graduate.
Using the assembly language example you gave in your question, I probably would not rate you as having working knowledge. You'd get points for being exposed to it vs. a candidate who had never seen it before, but I'd keep it at that level on my resume.
answered Mar 25 '14 at 18:21
user17881
39422
answered Mar 25 '14 at 18:21
user17881
39422
answered Mar 25 '14 at 18:21
user17881
39422
answered Mar 25 '14 at 18:21
user17881
39422
39422
1
What about being able to fluently code in something using reference materials? I've coded less or more briefly in a lot of things, have theoretical and some practical knowledge of pretty much all the concepts out there, etc. etc. I feel like that wouldn't really be enough in most people's books, even if I personally know that I could get up and running with the stuff fairly fast. I suppose that I should do some things in the languages relevant on the market before looking for jobs.
– Llamageddon
Nov 2 '14 at 0:48
@Asmageddon, People always code with "reference material" like Stackoverflow and code manuals / wiki. You don't actually expect people to rote-memorize everything do you? Or do you mean something else when you say "reference material"?
– Pacerier
Jul 10 '15 at 8:32
@Pacerier That is what I meant, thank you :)
– Llamageddon
Jul 11 '15 at 2:13
add a comment |Â
1
What about being able to fluently code in something using reference materials? I've coded less or more briefly in a lot of things, have theoretical and some practical knowledge of pretty much all the concepts out there, etc. etc. I feel like that wouldn't really be enough in most people's books, even if I personally know that I could get up and running with the stuff fairly fast. I suppose that I should do some things in the languages relevant on the market before looking for jobs.
– Llamageddon
Nov 2 '14 at 0:48
@Asmageddon, People always code with "reference material" like Stackoverflow and code manuals / wiki. You don't actually expect people to rote-memorize everything do you? Or do you mean something else when you say "reference material"?
– Pacerier
Jul 10 '15 at 8:32
@Pacerier That is what I meant, thank you :)
– Llamageddon
Jul 11 '15 at 2:13
1
1
What about being able to fluently code in something using reference materials? I've coded less or more briefly in a lot of things, have theoretical and some practical knowledge of pretty much all the concepts out there, etc. etc. I feel like that wouldn't really be enough in most people's books, even if I personally know that I could get up and running with the stuff fairly fast. I suppose that I should do some things in the languages relevant on the market before looking for jobs.
– Llamageddon
Nov 2 '14 at 0:48
What about being able to fluently code in something using reference materials? I've coded less or more briefly in a lot of things, have theoretical and some practical knowledge of pretty much all the concepts out there, etc. etc. I feel like that wouldn't really be enough in most people's books, even if I personally know that I could get up and running with the stuff fairly fast. I suppose that I should do some things in the languages relevant on the market before looking for jobs.
– Llamageddon
Nov 2 '14 at 0:48
@Asmageddon, People always code with "reference material" like Stackoverflow and code manuals / wiki. You don't actually expect people to rote-memorize everything do you? Or do you mean something else when you say "reference material"?
– Pacerier
Jul 10 '15 at 8:32
@Asmageddon, People always code with "reference material" like Stackoverflow and code manuals / wiki. You don't actually expect people to rote-memorize everything do you? Or do you mean something else when you say "reference material"?
– Pacerier
Jul 10 '15 at 8:32
@Pacerier That is what I meant, thank you :)
– Llamageddon
Jul 11 '15 at 2:13
@Pacerier That is what I meant, thank you :)
– Llamageddon
Jul 11 '15 at 2:13
add a comment |Â
up vote
22
down vote
"Working Knowledge" reflects a low-level competency in an area - you will be expected to work with the tool, but not necessarily to be an expert in that tool.
If you don't feel like you would be able to build a full product with the tool, BUT you feel like you could, with a little trial-and-error, reconstruct it from an example, you probably have 'working knowledge' of that tool.
As long as you can use that tool on a daily basis, even if you don't know how to do everything with that tool or even the 'best practices' of using that tool, you can say you have working knowledge, and back it up with your experience (I would say having some experience with it while working on another app is close enough to put on a resume - but the job requires you have a stronger working knowledge of the code, you should probably learn it a bit better before beginning work there).
Working Knowledge: 1.A knowledge of how to make something work without any deeper understanding of why it works, or of how to fix it if it breaks
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
3
As per conversation in the water cooler, here's a source to back it, too: en.wiktionary.org/wiki/working_knowledge
– CMW
Mar 25 '14 at 18:35
@CMW Do you mind if I include that in my answer?
– Zibbobz
Mar 25 '14 at 18:51
@Zibbobz go for it. You wrote basically what I'd write if I wrote an answer.
– Elysian Fields♦
Mar 25 '14 at 19:39
@Zibbobz what enderland said. I stole the link from him.
– CMW
Mar 25 '14 at 19:53
@Zibbobz, Doesn't your answer actually contradict the other answer above with 23 upvotes?
– Pacerier
Jul 10 '15 at 8:34
 |Â
show 1 more comment
up vote
22
down vote
"Working Knowledge" reflects a low-level competency in an area - you will be expected to work with the tool, but not necessarily to be an expert in that tool.
If you don't feel like you would be able to build a full product with the tool, BUT you feel like you could, with a little trial-and-error, reconstruct it from an example, you probably have 'working knowledge' of that tool.
As long as you can use that tool on a daily basis, even if you don't know how to do everything with that tool or even the 'best practices' of using that tool, you can say you have working knowledge, and back it up with your experience (I would say having some experience with it while working on another app is close enough to put on a resume - but the job requires you have a stronger working knowledge of the code, you should probably learn it a bit better before beginning work there).
Working Knowledge: 1.A knowledge of how to make something work without any deeper understanding of why it works, or of how to fix it if it breaks
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
3
As per conversation in the water cooler, here's a source to back it, too: en.wiktionary.org/wiki/working_knowledge
– CMW
Mar 25 '14 at 18:35
@CMW Do you mind if I include that in my answer?
– Zibbobz
Mar 25 '14 at 18:51
@Zibbobz go for it. You wrote basically what I'd write if I wrote an answer.
– Elysian Fields♦
Mar 25 '14 at 19:39
@Zibbobz what enderland said. I stole the link from him.
– CMW
Mar 25 '14 at 19:53
@Zibbobz, Doesn't your answer actually contradict the other answer above with 23 upvotes?
– Pacerier
Jul 10 '15 at 8:34
 |Â
show 1 more comment
up vote
22
down vote
up vote
22
down vote
"Working Knowledge" reflects a low-level competency in an area - you will be expected to work with the tool, but not necessarily to be an expert in that tool.
If you don't feel like you would be able to build a full product with the tool, BUT you feel like you could, with a little trial-and-error, reconstruct it from an example, you probably have 'working knowledge' of that tool.
As long as you can use that tool on a daily basis, even if you don't know how to do everything with that tool or even the 'best practices' of using that tool, you can say you have working knowledge, and back it up with your experience (I would say having some experience with it while working on another app is close enough to put on a resume - but the job requires you have a stronger working knowledge of the code, you should probably learn it a bit better before beginning work there).
Working Knowledge: 1.A knowledge of how to make something work without any deeper understanding of why it works, or of how to fix it if it breaks
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
"Working Knowledge" reflects a low-level competency in an area - you will be expected to work with the tool, but not necessarily to be an expert in that tool.
If you don't feel like you would be able to build a full product with the tool, BUT you feel like you could, with a little trial-and-error, reconstruct it from an example, you probably have 'working knowledge' of that tool.
As long as you can use that tool on a daily basis, even if you don't know how to do everything with that tool or even the 'best practices' of using that tool, you can say you have working knowledge, and back it up with your experience (I would say having some experience with it while working on another app is close enough to put on a resume - but the job requires you have a stronger working knowledge of the code, you should probably learn it a bit better before beginning work there).
Working Knowledge: 1.A knowledge of how to make something work without any deeper understanding of why it works, or of how to fix it if it breaks
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
edited Mar 25 '14 at 19:41
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
answered Mar 25 '14 at 18:11
Zibbobz
6,68752453
6,68752453
3
As per conversation in the water cooler, here's a source to back it, too: en.wiktionary.org/wiki/working_knowledge
– CMW
Mar 25 '14 at 18:35
@CMW Do you mind if I include that in my answer?
– Zibbobz
Mar 25 '14 at 18:51
@Zibbobz go for it. You wrote basically what I'd write if I wrote an answer.
– Elysian Fields♦
Mar 25 '14 at 19:39
@Zibbobz what enderland said. I stole the link from him.
– CMW
Mar 25 '14 at 19:53
@Zibbobz, Doesn't your answer actually contradict the other answer above with 23 upvotes?
– Pacerier
Jul 10 '15 at 8:34
 |Â
show 1 more comment
3
As per conversation in the water cooler, here's a source to back it, too: en.wiktionary.org/wiki/working_knowledge
– CMW
Mar 25 '14 at 18:35
@CMW Do you mind if I include that in my answer?
– Zibbobz
Mar 25 '14 at 18:51
@Zibbobz go for it. You wrote basically what I'd write if I wrote an answer.
– Elysian Fields♦
Mar 25 '14 at 19:39
@Zibbobz what enderland said. I stole the link from him.
– CMW
Mar 25 '14 at 19:53
@Zibbobz, Doesn't your answer actually contradict the other answer above with 23 upvotes?
– Pacerier
Jul 10 '15 at 8:34
3
3
As per conversation in the water cooler, here's a source to back it, too: en.wiktionary.org/wiki/working_knowledge
– CMW
Mar 25 '14 at 18:35
As per conversation in the water cooler, here's a source to back it, too: en.wiktionary.org/wiki/working_knowledge
– CMW
Mar 25 '14 at 18:35
@CMW Do you mind if I include that in my answer?
– Zibbobz
Mar 25 '14 at 18:51
@CMW Do you mind if I include that in my answer?
– Zibbobz
Mar 25 '14 at 18:51
@Zibbobz go for it. You wrote basically what I'd write if I wrote an answer.
– Elysian Fields♦
Mar 25 '14 at 19:39
@Zibbobz go for it. You wrote basically what I'd write if I wrote an answer.
– Elysian Fields♦
Mar 25 '14 at 19:39
@Zibbobz what enderland said. I stole the link from him.
– CMW
Mar 25 '14 at 19:53
@Zibbobz what enderland said. I stole the link from him.
– CMW
Mar 25 '14 at 19:53
@Zibbobz, Doesn't your answer actually contradict the other answer above with 23 upvotes?
– Pacerier
Jul 10 '15 at 8:34
@Zibbobz, Doesn't your answer actually contradict the other answer above with 23 upvotes?
– Pacerier
Jul 10 '15 at 8:34
 |Â
show 1 more comment
up vote
4
down vote
If you told me you had working knowledge of X, I would expect that I could assign you tasks to do with X and you could carry them out. You might be a bit slow at first due to having to ask questions, look things up, etc, but you know enough to have the framework for acquiring more knowledge organically. Without working knowledge in X, I would expect to have to give you some sort of training before you could carry out tasks to do with X.
If you wouldn't be happy to be hired on the basis of your knowledge of assembly language and given assembly language tasks without much "extra support" getting up to speed with assembly, then you don't have working knowledge of it.
answered Mar 25 '14 at 21:49
Ben
1435
1
Well, I would be very happy to be hired on the basis of my limited knowledge of assembly language as I very much enjoyed using it and I feel like this would be a great opportunity for me to spend more time with the subject. Possibly I posses the working knowledge in question then? :-)
– BoZenKhaa
Mar 25 '14 at 22:01
2
Not "spend more time with the subject" - can you work somehow productively on it on your first day? If not, then it's not yet 'working knowledge'.
– Peteris
Mar 25 '14 at 22:10
Yeah, right. Thanks, I misunderstood.
– BoZenKhaa
Mar 25 '14 at 22:24
add a comment |Â
up vote
4
down vote
If you told me you had working knowledge of X, I would expect that I could assign you tasks to do with X and you could carry them out. You might be a bit slow at first due to having to ask questions, look things up, etc, but you know enough to have the framework for acquiring more knowledge organically. Without working knowledge in X, I would expect to have to give you some sort of training before you could carry out tasks to do with X.
If you wouldn't be happy to be hired on the basis of your knowledge of assembly language and given assembly language tasks without much "extra support" getting up to speed with assembly, then you don't have working knowledge of it.
answered Mar 25 '14 at 21:49
Ben
1435
1
Well, I would be very happy to be hired on the basis of my limited knowledge of assembly language as I very much enjoyed using it and I feel like this would be a great opportunity for me to spend more time with the subject. Possibly I posses the working knowledge in question then? :-)
– BoZenKhaa
Mar 25 '14 at 22:01
2
Not "spend more time with the subject" - can you work somehow productively on it on your first day? If not, then it's not yet 'working knowledge'.
– Peteris
Mar 25 '14 at 22:10
Yeah, right. Thanks, I misunderstood.
– BoZenKhaa
Mar 25 '14 at 22:24
add a comment |Â
up vote
4
down vote
up vote
4
down vote
If you told me you had working knowledge of X, I would expect that I could assign you tasks to do with X and you could carry them out. You might be a bit slow at first due to having to ask questions, look things up, etc, but you know enough to have the framework for acquiring more knowledge organically. Without working knowledge in X, I would expect to have to give you some sort of training before you could carry out tasks to do with X.
If you wouldn't be happy to be hired on the basis of your knowledge of assembly language and given assembly language tasks without much "extra support" getting up to speed with assembly, then you don't have working knowledge of it.
answered Mar 25 '14 at 21:49
Ben
1435
If you told me you had working knowledge of X, I would expect that I could assign you tasks to do with X and you could carry them out. You might be a bit slow at first due to having to ask questions, look things up, etc, but you know enough to have the framework for acquiring more knowledge organically. Without working knowledge in X, I would expect to have to give you some sort of training before you could carry out tasks to do with X.
If you wouldn't be happy to be hired on the basis of your knowledge of assembly language and given assembly language tasks without much "extra support" getting up to speed with assembly, then you don't have working knowledge of it.
answered Mar 25 '14 at 21:49
Ben
1435
edited Mar 25 '14 at 22:07
answered Mar 25 '14 at 21:49
Ben
1435
answered Mar 25 '14 at 21:49
Ben
1435
answered Mar 25 '14 at 21:49
Ben
1435
1435
1
Well, I would be very happy to be hired on the basis of my limited knowledge of assembly language as I very much enjoyed using it and I feel like this would be a great opportunity for me to spend more time with the subject. Possibly I posses the working knowledge in question then? :-)
– BoZenKhaa
Mar 25 '14 at 22:01
2
Not "spend more time with the subject" - can you work somehow productively on it on your first day? If not, then it's not yet 'working knowledge'.
– Peteris
Mar 25 '14 at 22:10
Yeah, right. Thanks, I misunderstood.
– BoZenKhaa
Mar 25 '14 at 22:24
add a comment |Â
1
Well, I would be very happy to be hired on the basis of my limited knowledge of assembly language as I very much enjoyed using it and I feel like this would be a great opportunity for me to spend more time with the subject. Possibly I posses the working knowledge in question then? :-)
– BoZenKhaa
Mar 25 '14 at 22:01
2
Not "spend more time with the subject" - can you work somehow productively on it on your first day? If not, then it's not yet 'working knowledge'.
– Peteris
Mar 25 '14 at 22:10
Yeah, right. Thanks, I misunderstood.
– BoZenKhaa
Mar 25 '14 at 22:24
1
1
Well, I would be very happy to be hired on the basis of my limited knowledge of assembly language as I very much enjoyed using it and I feel like this would be a great opportunity for me to spend more time with the subject. Possibly I posses the working knowledge in question then? :-)
– BoZenKhaa
Mar 25 '14 at 22:01
Well, I would be very happy to be hired on the basis of my limited knowledge of assembly language as I very much enjoyed using it and I feel like this would be a great opportunity for me to spend more time with the subject. Possibly I posses the working knowledge in question then? :-)
– BoZenKhaa
Mar 25 '14 at 22:01
2
2
Not "spend more time with the subject" - can you work somehow productively on it on your first day? If not, then it's not yet 'working knowledge'.
– Peteris
Mar 25 '14 at 22:10
Not "spend more time with the subject" - can you work somehow productively on it on your first day? If not, then it's not yet 'working knowledge'.
– Peteris
Mar 25 '14 at 22:10
Yeah, right. Thanks, I misunderstood.
– BoZenKhaa
Mar 25 '14 at 22:24
Yeah, right. Thanks, I misunderstood.
– BoZenKhaa
Mar 25 '14 at 22:24
add a comment |Â
up vote
1
down vote
"I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
"Working knowledge" of something, means that given a task in it, you could "take the ball and run with it," producing a "substantially complete" assignment. You might need some supervision at the front end, or some correction/editing/feedback at the back end, but you could bear the main burden of the task.
That doesn't seem to describe you. At best, you might be viewed as an "advanced beginner" or potential trainee.
answered Sep 20 '14 at 23:01
Tom Au
31928
add a comment |Â
up vote
1
down vote
"I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
"Working knowledge" of something, means that given a task in it, you could "take the ball and run with it," producing a "substantially complete" assignment. You might need some supervision at the front end, or some correction/editing/feedback at the back end, but you could bear the main burden of the task.
That doesn't seem to describe you. At best, you might be viewed as an "advanced beginner" or potential trainee.
answered Sep 20 '14 at 23:01
Tom Au
31928
add a comment |Â
up vote
1
down vote
up vote
1
down vote
"I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
"Working knowledge" of something, means that given a task in it, you could "take the ball and run with it," producing a "substantially complete" assignment. You might need some supervision at the front end, or some correction/editing/feedback at the back end, but you could bear the main burden of the task.
That doesn't seem to describe you. At best, you might be viewed as an "advanced beginner" or potential trainee.
answered Sep 20 '14 at 23:01
Tom Au
31928
"I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
"Working knowledge" of something, means that given a task in it, you could "take the ball and run with it," producing a "substantially complete" assignment. You might need some supervision at the front end, or some correction/editing/feedback at the back end, but you could bear the main burden of the task.
That doesn't seem to describe you. At best, you might be viewed as an "advanced beginner" or potential trainee.
answered Sep 20 '14 at 23:01
Tom Au
31928
answered Sep 20 '14 at 23:01
Tom Au
31928
answered Sep 20 '14 at 23:01
Tom Au
31928
answered Sep 20 '14 at 23:01
Tom Au
31928
31928
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f21316%2fwhat-level-of-competency-does-the-term-working-knowledge-describe%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
" I do not feel like I could do any useful work with my assembly knowledge." You do not have "working knowledge" of assembly.
– Tom Au
Sep 20 '14 at 22:55
Also see workplace.stackexchange.com/q/48730/18555
– Pacerier
Jul 10 '15 at 9:25