Haskell jobs with Standard Chartered, various locations

We have two open positions for senior Haskell (technically Mu, our in-house variant) developers at Standard Chartered Bank. These are slightly different roles: one is with my team (Core Strats), with 5 possible locations (Singapore, Poland, UK, France, New York). The other is in the wider team Core Strats belong to, with 2 possible locations (Singapore or UK). Both are developer positions.

You can learn more about our team and what we do by reading our experience report “Functional Programming in Financial Markets”, to be presented at ICFP next month: Functional Programming in Financial Markets (Experience Report) | Proceedings of the ACM on Programming Languages

The roles are eligible for a remote working arrangement from the country of employment, after an initial in-office period. We cover visa and relocation costs for successful applicants.

Note that one of the first steps of the application is a Valued Behaviours Assessment and it is quite important: our team won’t be able to see your application until you pass this assessment.

Application link for the role in the Market Risk Modelling team: Senior Quantitative Analyst, Market Risk Modelling (UK or Singapore based) Job Details | Standard Chartered Bank
Application link for the role in Core Strats: Senior Quantitative Developer (Singapore, Poland, UK, France, New York) Job Details | Standard Chartered Bank

For Singapore you can also find the Core Strats role in My Careers Future with a SGD salary range: MyCareersFuture Singapore

11 Likes

Just a reminder, SCB will be at ICFP next week. If you’re interested in how they use Haskell you should check out their presentation/paper and chat with them.

2 Likes

I’ve worked at standard chartered for two years before I quit recently. It’s a big company and I have not worked in the specific team. But I do know they’re regarded as a good engineering team.

If you have never worked in a bank before, I advise you to ask a lot of questions about:

  • bank culture
  • what teams/customers your role depends on
  • performance evaluation criteria
  • onboarding
  • budget of the team and expectations of the role (essentially the risk of your role)

It is worth noting that the bank is not an engineering company. That can have some subtle effects on every day work and decisions. IME the bank relies more on processes, hierarchy and separation of risk/concerns than organic decision making. Teams within the bank however sometimes achieve very different workflows and subcultures.

I think SCB (compared to fintech in general) is a little less of a volatile place. There are places with more mass layoffs and hire and fire tactics. But financial industry is always volatile.

10 Likes