You’ve just closed the last issue of a major project. It’s shipped! Congrats.
You start writing your internal blog post about how you “shipped X using Y technology”, but why should people care that your project shipped? Why was it a good use of your time to solve that problem?
When talking about your accomplishments (to your manager, in a public post, in a self evaluation, etc.) focus less on what you shipped and more on why you shipped what you did. Did your work unlock new business? Did it save money by making things more efficient? Did it help the organization avoid legal issues by complying to regulations? Did it fix a bug that 100s of customers complained about?
If you can, support your why with graphs, data, and testimonials. The evidence makes your story stronger.
Remem…
You’ve just closed the last issue of a major project. It’s shipped! Congrats.
You start writing your internal blog post about how you “shipped X using Y technology”, but why should people care that your project shipped? Why was it a good use of your time to solve that problem?
When talking about your accomplishments (to your manager, in a public post, in a self evaluation, etc.) focus less on what you shipped and more on why you shipped what you did. Did your work unlock new business? Did it save money by making things more efficient? Did it help the organization avoid legal issues by complying to regulations? Did it fix a bug that 100s of customers complained about?
If you can, support your why with graphs, data, and testimonials. The evidence makes your story stronger.
Remember, as an engineer it’s not what you do, but what your work does.