[p4wnc6]

Three questions about the role:

May developers work in suitably private conditions, or is it an open-plan / trading-floor environment?

Will these roles involve working with a non-standard Haskell compiler?

What level of Haskell experience are you looking for ... what are some milestone Haskell skills that could help someone quickly identify whether they are plausibly a good fit?

[coolsunglasses]

>Will these roles involve working with a non-standard Haskell compiler?

They have a pretty well known internal compiler for a strict dialect of Haskell.

>What level of Haskell experience are you looking for ... what are some milestone Haskell skills that could help someone quickly identify whether they are plausibly a good fit?

They're unlikely to answer this and I don't work there, but you should probably be able to reason about things like GHC's RTS as a baseline.

[tome]

It's an open plan trading floor.

It involves working with Mu, Standard Chartered's in-house compiler. Working with Mu feels very, very similar to just using GHC Haskell though.

I can't give any specific details about milestone skills, but if you've published libraries to Hackage that are used by people you've never heard of that's probably a good sign that it's worth applying.

[zerr]

> It's an open plan trading floor.

Do you find it challenging to "get in the zone"? i.e. there is all that fuss, noise, and you just sit quietly somewhere in the middle and enjoy programming? Do you have to wear headphones all day long?

[p4wnc6]

I worked in an environment like this before and found it unsustainable. The number of defects and mistakes from everyone in the open-plan area was significant and was a major cause for re-work. Even though the company was making money, it was clear that the noisy workspace was causing them to leave a ton of money on the table, because it was simply not possible for any engineer to create things of minimally acceptable quality in that environment.

There are also concerns for engineers with misophonia (extreme physiological aversion to ambient sounds). For these engineers, though they may be able to do the job exceptionally well, the physical workspace is needlessly prohibitive, bordering on discriminatory, and the idea of using headphones would not address the underlying problem.

I feel this is one of the biggest health issues facing software engineering as a profession (whether it is applied to quantitative trading or banking or making a WordPress site). Hopefully more developers will continue to express their uncompromising need for adequate privacy and quiet in their workspace, and companies will respond by restructuring workspaces to respect these unavoidable human needs.