2 ms·
> "I know C++ in an out". I know what you mean, but this was a bad example. People who really know c++ are having to turn jobs down right now. Fintech is all o
by matwood 9y ago
> "I know C++ in an out".
I know what you mean, but this was a bad example. People who really know c++ are having to turn jobs down right now. Fintech is all over my c++ acquaintances.
Your advice about clear economic terms is spot on for resumes at any age. You have to link to numbers and then try to link to dollars.
"Developed a Python API for reporting." -- boring
"Developed a Python API that handled X amount of data, with Y amount of request/s and delivered Z reports/month that in turn saved/made the company $U/year." -- this checks the tech boxes and the managers/owners box of dollars delivered.
- fsloth 9y ago"... this was a bad example. People who really know c++ are having to turn jobs down right now. Fintech is all over my c++ acquaintances." Yeah, maybe some easier language would have been a better example of dangerously shallow knowledge base. The basic theme was to give a financial valuation to a knowledge base - in your example, I presume a software engineer who had financial experience and could explain his contribution in financial terms would still have an edge in negotiating a compensation over the one who didn't :) ?
- matwood 9y agoNot just negotiating compensation, but they could actually be more valuable to the company. The engineer who is always wondering 'what am I contributing to the bottom line' will make decisions that typically are more company focused. A bit sarcastic example ;) is as an engineer thinking about work to do or argue to get done. Do they rewrite some existing functionality in the latest js framework of the day or add a new feature that may lead to new sales?