Skip to main content
Commonmark migration
Source Link

Take those tips with a grain of salt. They seem very situational specific and somewhat out of context. stating your job description and your title is NOT a bad thing. However this should not be the main focus. I believe that's what those hints were refering to.

example :

Software engineer - [company] - [from - to]

 

During this time I was responcible for X,Y,Z. In order to accomplish this I had to make use of the coding languages A,B,C. I mainly focused on my skills with B, However during this job the combining of my skill and knowledge of these languages lead to to creating a better product. My most interesting project I've done at [company] is to create a [bla bla] that works with [bla bla]. I made sure to communicate frequently which helped decrease risk and allowed us to respond quickly to any unforseen errors.

Right there I violated the first 2 donts already. However it was mainly focused on what you did there and how you applied it. Try writing it in such a way. Possibly try writing towards competencies. Where you explain how well you communicated and took initiative to ask questions.

Don't explain the results of your efforts, explain the efforts themselves.

Take those tips with a grain of salt. They seem very situational specific and somewhat out of context. stating your job description and your title is NOT a bad thing. However this should not be the main focus. I believe that's what those hints were refering to.

example :

Software engineer - [company] - [from - to]

 

During this time I was responcible for X,Y,Z. In order to accomplish this I had to make use of the coding languages A,B,C. I mainly focused on my skills with B, However during this job the combining of my skill and knowledge of these languages lead to to creating a better product. My most interesting project I've done at [company] is to create a [bla bla] that works with [bla bla]. I made sure to communicate frequently which helped decrease risk and allowed us to respond quickly to any unforseen errors.

Right there I violated the first 2 donts already. However it was mainly focused on what you did there and how you applied it. Try writing it in such a way. Possibly try writing towards competencies. Where you explain how well you communicated and took initiative to ask questions.

Don't explain the results of your efforts, explain the efforts themselves.

Take those tips with a grain of salt. They seem very situational specific and somewhat out of context. stating your job description and your title is NOT a bad thing. However this should not be the main focus. I believe that's what those hints were refering to.

example :

Software engineer - [company] - [from - to]

During this time I was responcible for X,Y,Z. In order to accomplish this I had to make use of the coding languages A,B,C. I mainly focused on my skills with B, However during this job the combining of my skill and knowledge of these languages lead to to creating a better product. My most interesting project I've done at [company] is to create a [bla bla] that works with [bla bla]. I made sure to communicate frequently which helped decrease risk and allowed us to respond quickly to any unforseen errors.

Right there I violated the first 2 donts already. However it was mainly focused on what you did there and how you applied it. Try writing it in such a way. Possibly try writing towards competencies. Where you explain how well you communicated and took initiative to ask questions.

Don't explain the results of your efforts, explain the efforts themselves.

Source Link
Migz
  • 4.1k
  • 4
  • 16
  • 26

Take those tips with a grain of salt. They seem very situational specific and somewhat out of context. stating your job description and your title is NOT a bad thing. However this should not be the main focus. I believe that's what those hints were refering to.

example :

Software engineer - [company] - [from - to]

During this time I was responcible for X,Y,Z. In order to accomplish this I had to make use of the coding languages A,B,C. I mainly focused on my skills with B, However during this job the combining of my skill and knowledge of these languages lead to to creating a better product. My most interesting project I've done at [company] is to create a [bla bla] that works with [bla bla]. I made sure to communicate frequently which helped decrease risk and allowed us to respond quickly to any unforseen errors.

Right there I violated the first 2 donts already. However it was mainly focused on what you did there and how you applied it. Try writing it in such a way. Possibly try writing towards competencies. Where you explain how well you communicated and took initiative to ask questions.

Don't explain the results of your efforts, explain the efforts themselves.