A developer who joins an energy trading desk can usually code. What they lack is the trade. Until they learn it, they cannot safely change the code that books trades, values them or settles them.

This guide is for their manager. It covers what to teach first, a plan for the first 90 days, questions that show what has stuck, and how to tell whether it worked. ETRM stands for energy trading and risk management: the system that holds the desk's trades. If the term is new, what an ETRM system does is the place to start.

Why it takes months

A good developer learns a new codebase in weeks. A trading desk takes longer, for four reasons.

The words are precise. Book, position, delta, curve, mark-to-market, nomination. Each has one exact meaning on the desk. A developer who guesses gets it nearly right, which is worse than wrong.

One trade touches every system. A trade booked at three in the afternoon becomes a position, a line in the next morning's profit and loss (P&L), a delivery schedule, an invoice and a report to the regulator. A change in one place shows up in another, days later.

The mistakes are quiet. A wrong sign, a missing hour on the day the clocks change, a price in pence where pounds were expected. The code runs and the tests pass. The P&L is wrong, and someone on the desk finds it at 07:30.

The teaching happens on the floor. Senior developers and traders explain the same trade to each new joiner. It works, slowly, and it costs their time.

What to teach first

Teach in the order the trade itself moves. Each step needs the one before it.

  1. The physical product. Power in Great Britain is traded in half-hours: 48 a day, 46 or 50 on the days the clocks change. The British gas day runs from 05:00 to 05:00, UK time. Megawatts are a rate; megawatt-hours are an amount. Gas is often priced in pence per therm. Physical foundations covers this.
  2. The trade and its lifecycle. What a trade record holds: the counterparty, product, delivery period, volume, price, and whether it is a buy or a sell. Then where it goes: capture, validation, confirmation, scheduling, settlement and invoicing.
  3. The position. The trades added up by delivery period, so the desk knows how much it is long or short. Position aggregation shows the sums.
  4. Curves and mark-to-market P&L. The forward curve gives today's price for each future period. A trade's mark-to-market value is the gap between that price and the trade's price, times the volume, with the sign set by buy or sell. Mark-to-market P&L works it through.
  5. Risk and limits. What the desk may hold, and where a bad trade is stopped. Risk management covers limits, value at risk and credit.
  6. The markets the desk trades. Day-ahead and intraday power, imbalance, the gas hub and nominations. Start with power trading and gas trading.
  7. Reporting. What the desk sends to the regulator, and which data it comes from. For EU markets, see the revised REMIT reporting.

Then the code's own traps, which belong to no one module. Test the days the clocks change. Hold money in decimals, never floating point. Make a rerun of last night's job give the same answer.

A 30/60/90-day plan

The plan gives each month one aim. Adjust the pace to the person, not the calendar.

Days 1 to 30: understand

  • Learn the words, with the desk's own examples.
  • Trace one real trade through every system, with a colleague who knows it. Write down each place it lands.
  • Read-only access to the trade and P&L data.
  • Work out the position and mark-to-market value for a handful of trades, first by hand, then in code. Compare the two.
  • Sit with the desk for one morning, through the 07:30 P&L.

Days 31 to 60: change things, with a reviewer

  • Fix small faults in reports, where a mistake is easy to see.
  • Write tests for a settlement or P&L job, including a clock-change day.
  • Investigate one break with the operations team, from the symptom back to the cause.
  • Explain one day's P&L move to a senior developer: how much came from new trades, and how much from the curve.

Days 61 to 90: own something small

  • Make a first approved change to trade or P&L code.
  • Shadow the support rota for a week.
  • Explain a day's P&L to the desk head, in the desk's words.
  • Take the same questions as on day one, and compare the answers.

Questions to check what has stuck

Ask these at the start, and again around day 90. The answers should get shorter and surer.

  • Where does a trade go after it is booked, and which system holds the official record?
  • What is our position in a product for next month, and how is it worked out?
  • Why did yesterday's P&L move? How much came from new trades, and how much from the curve?
  • What happens to half-hourly code on the last Sunday in March and the last Sunday in October?
  • Why is money held as a decimal, not a float?
  • If the curve job fails at 06:00, who notices, and what do they see at 07:30?
  • What does the desk report to the regulator, and from which data?
  • Which limit would stop a bad trade, and where is it checked?
  • What must the desk send to the gas or power system operator, and by when?

How to tell it worked

Training is hard to measure. These four signs are not.

  • The date of the first approved change to trade or P&L code. Compare it with the last person who joined.
  • Hours asked of senior people. Keep a rough log for two weeks at the start and two weeks near the end.
  • Rework from a misunderstanding. Count the faults traced to a misread trade, curve or settlement run.
  • The questions above, answered at the start and at the end, person by person.

Write the measures down before the person starts. Afterwards, everyone remembers the plan as having worked.

When to bring in help

The plan above needs a senior person's time each week. That is the hard part when several people join at once, or when the seniors are needed on the desk.

That is the case team training is for. Jordan Dimov teaches the team how the desk works, using your own trades and systems as the examples. He built trading platforms for the desks at Shell, Centrica and Limejump.