Raw mkt data tech skill is better than soft mkt data even though it’s further away from “the money”:
- standard — Exchange mkt data format won’t change a lot. Feels like an industry standard
- the future — most OTC products are moving to electronic trading and will have market data to process
- more necessary than many modules in a trading system. However ….. I guess only a few systems need to deal with raw market data. Most down stream systems only deal with the soft market data.
Q1: If you compare 5 typical market data gateway dev  jobs, can you identify a few key tech skills shared by at least half the jobs, but not a widely used “generic” skill like math, hash table, polymorphism etc?
Q2: if there is at least one, how important is it to a given job? One of the important required skills, or a make-or-break survival skill?
My view — I feel there is not a shared core skill set. I venture to say there’s not a single answer to Q1.
In contrast, look at quant developers. They all need skills in c++/excel, BlackScholes, bond math, swaps, …
In contrast, also look at dedicated database developers. They all need non-trivial SQL, schema design. Many need stored procs. Tuning is needed if large tables
Now look at market data gateway for OPRA. Two firms’ job requirements will share some common tech skills like throughput (TPS) optimization, fast storage.
If latency and TPS requirements aren’t stringent, then I feel the portable skill set is an empty set.
 There are also many positions whose primary duty is market data but not raw market data, not large volume, not latency sensitive. The skill set is even more different. Some don’t need development skill on market data — they only configure some components.