Discover your dream Career
For Recruiters

JPMorgan has got a new way of evaluating tech staff in its investment bank

If you're a developer in JPMorgan's corporate and investment bank (CIB), you may be feeling a little apprehensive today. Insiders say the bank is trialling a partnership with BlueOptima, a third party company that measures the efficiency of 'software resources.'

JPMorgan declined to comment on the pilot project, which insiders say was announced internally in a memo from head of CIB technology Mike Grimaldi this week. "It will deliver management metrics around individual developer productivity and contributions," says one JPM insider. "There's a very lively debate around it on our internal Symphony chatroom."

JPMorgan isn't the first and won't be the last bank to assess the efficiency of its coding staff. BlueOptima says it works with nine out of 16 of the top universal banks, and Credit Suisse famously displayed a chart showing that a few highly productive teams were responsible for a lot of its code at its 2017 investor day. This is presumably the kind of analysis that BlueOptima can provide. 

Some JPMorgan technologists see upside in having their individual performance tracked and benchmarked against colleagues and the industry. BlueOptima boasts that its system, "empowers developers to demonstrate the value they have delivered," which sounds promising. However, one developer at JPMorgan said the fear is that it will be used to determine bonuses and cut pay. "BlueOptima are selling objectivity around something that's subjective and management are buying into it in the hope that it will make their budgets go further."

After years of increasing technology budgets, 2020 looks like the year when banks everywhere make a concerted effort to make their technology spend more efficient. Morgan Stanley laid off a large chunk of its most senior technologists at the end of 2019 and most U.S. banks are now determined to derive more value from their tech investments. Speaking at last year's investor day, Daniel Pinto, the head of JPMorgan's corporate and investment bank said he wanted to transform technology by creating standardized products that can be reused, rather than "building everything from zero to one hundred every single time.” JPMorgan CFO Jennifer Piepszak reiterated the bank's intention of "realizing efficiencies from investments in tech" during last week's investor call.

What appeals to a bank does not always appeal to employees though. One developer in the CIB said BlueOptima a continuation of the "SEE (Software Engineering Efficiency) project" and that it purports to allow the objective quantification of developers' billable coding effort (BCE) based on a moment-in-time analysis of committed source code.  The danger, as perceived by BlueOptima sceptics, is that the new tool will degrade the subjective opinions of coders working on the system and will penalize anyone commiting less than an average amount of "meaningful" code. 

"Our understanding is that comments, empty lines and duplicate code won't be counted as meaningful," said one developer at the bank. "For example, if a developer spends his time removing unused code to reduce technology debt, or if someone does some performance optimization and runs local simulations but the code is not part of a production report, then it seems they will be unfairly penalized compared to someone who continuously churns out code, regardless of what that code is being used for." 

Although BlueOptima says it works with eight 'healthtech giants,' big technology companies like Google and Microsoft use peer assessment and managers' opinions as a way of evaluating developers' performance. "This system ignores the creativity and uniqueness of software developers," says one JPMorgan technologist of BlueOptima. "This is why the big tech firms are more reliant on peer feedback to assess staff and to set expectations."

Photo by William Warby on Unsplash

Have a confidential story, tip, or comment you’d like to share? Contact: sbutcher@efinancialcareers.com in the first instance. Whatsapp/Signal/Telegram also available.

Bear with us if you leave a comment at the bottom of this article: all our comments are moderated by human beings. Sometimes these humans might be asleep, or away from their desks, so it may take a while for your comment to appear. Eventually it will – unless it’s offensive or libelous (in which case it won’t.)

author-card-avatar
AUTHORSarah Butcher Global Editor
  • sc
    schm0e
    25 January 2020

    Bring in the robots already. This is beneath human dignity.

  • Mr
    Mr. T
    24 January 2020

    I first saw this type of 'coder metrics' in the 80's. It proved to be a very blunt tool at the time. Counting lines of code or changes to code without understanding what the code does, or how well it does it, or how easy or difficult it will be to maintain is meaningless.
    On one system, I wrote dozens of core routines that everyone else could call from their programs, so it looked like I wrote 50% of the system and then my 'lines of code' productivity dropped. But that's because subsequent programs consisted of calling many of the prewritten routines. As a team we completed the development before the scheduled date and our traders were very happy that ongoing additions and enhancements were implemented so quickly. That's missed if you're just looking at code lines written/changed.

  • sc
    schm0e
    23 January 2020

    Bring on the robots already. This is beneath human dignity.

  • Se
    Seeing Red
    23 January 2020

    Having worked with Blue Optima for 6 months there are large holes in the 'evaluation' algorithms that obviously not highlighted until you get knee deep into it. It is best used for relative comparison against people performing a similar role, i.e. within the same program. What is unable to do is highlight that developer X on program 123 is producing better more efficient code than developer Y on program 456.

    Blue Optima does not analyze code in the same way that a product like SonarQube does, it seems to be a relatively straight forward algorithm (that is hidden and remains unexplained) which is no great surprise when it doesnt provide information on how efficient the code that individuals are checking in

Sign up to our Newsletter!

Get advice to help you manage and drive your career.

Boost your career

Find thousands of job opportunities by signing up to eFinancialCareers today.
Recommended Jobs
Falcon Brook Search
Quantitative Developer Python C++
Falcon Brook Search
London, United Kingdom
Anson McCade
Software Engineer - High Performance Computing
Anson McCade
London, United Kingdom
Bruin
Portfolio Manager
Bruin
London, United Kingdom
Vertus Partners
Quant Analyst - Front Office - London
Vertus Partners
London, United Kingdom
Stephen Bell Associates
Investment Risk Officer, Private Credit - Alternative Asset Manager
Stephen Bell Associates
London, United Kingdom

Sign up to our Newsletter!

Get advice to help you manage and drive your career.