Hi.
I have been lurking on ServeTheHome for a couple of years now, but just did not have time to participate much until now.
I would like to introduce myself and the company I work with and then describe some of the opportunities available and the sorts of people we are looking to hire. Bottom line upfront - we are hiring remotely across a gamut of roles and can consider people in most locations. Full-time is ideal, but for very capable people we can be flexible - part-time or longer-term fixed-term contract (less than a few months is not very efficient for us).
Symmetry Investments is a post-startup alternative asset manager - c $8.9bn of assets under management, with around 230 people. Founded in 2013 (managing money since 2014), we have offices in London, HK, Singapore, and Jersey, with a US office under way.
I am responsible for technology across the firm, and co-direct research. My path to the role was unconventional, and our approach to technology is informed by the different path I took; my first contribution to public-domain software (open-source didn´t have that name then) was to Tom Jennings´ Fidonet BBS in 1989. I used to run a BBS of my own - Absolute Zero - and edited the "security-research" section on 01 for Amiga, a popular London bulletin board. You can read some of my more recent writings on Quora, and I have a Twitter account - @Laeeth.
Along with the obvious benefits of technological progress since the 8-bit days, I feel that we lost something. The BBC Micro at school came with a pretty good user-guide, including a schematic. You could hope to understand every part of the machine and with a basic knowledge of electronics and the technical data sheets on the chips you could even design and build your own computers (now we would say embedded devices). Today everything is so complex and there is layer upon layer of abstraction and that mindset of figuring things out isn´t generally how we approach hardware today, especially in the enterprise. Have a problem? Well in that case you surely need a solution, and since you are a serious enterprise then you must pick from one of the plethora of predigested enterprise solutions available for that purpose. You must be crazy to want to understand it or do it yourself - leave that to the experts.
Our experience has been that although a basic approach of favouring getting your hands dirty may not seem optimal, might even seem wasteful from a narrowly commercial perspective, that trends in enterprise technology have gone so far that the opposite is true. If you understand something then you can reason about it, change it, know what is easier than how it sounds and what is much harder. Or to put it into enterprise-speak (I studied economics), such an organisational capability creates adaptiveness and strategic optionality. Practical experience is also the source of innovation.
When I became more directly involved at Symmetry in 2017 we used perforce. I think Google use perforce, but they have a lot of tooling on top and we did not. So nobody read anybody else´s code - nobody even had access to it. I set up a Gitlab server myself because at the time we lacked capabilities (to work with git, with Gitlab, and even to build and manage Linux servers). That isn´t typically how somebody in the role I had at the time (one of the three people running Symmetry) would approach things but it was by far the best choice given the constraints.
That´s changed a bit, especially on the development side. We wrote our own domain specific language for reporting and integrating internal systems. We exploit the metaprogramming and compile time function execution capabilities of the D programming language to automatically wrap and register straight code written in D. So for the maths part of the standard library we loop through all the symbols in std.math from Phobos and register them. D has some libraries, but C++ has more. So we made an internship project to call all of C++ from our language using CERN´s cling and it basically just works - talk before the Compiler Research Group at Stanford IRIS-HEP is here, and Alexandru wrote a piece for the LLVM blog that came out just recently.
We have Andrei Alexandrescu working with us on the development side (he joined last year) and recently Amaury Sechet, author of the SDC experimental compiler, co-creator of Bitcoin Cash and technical lead of Bitcoin ABC started working with us. We are quite involved in the D language community and have open-sourced (and develop openly) quite a few internal projects.
We started hiring remotely from the moment I became involved, and the pandemic accelerated that - we have been forced-remote for now since Feb 2020. I would say that the development side has been remote-first for a while; and the rest of the company (trading, legal, compliance, accounting, operations, research, and HR) is moving towards remote-first. The employee handbook - like many other internal documentation projects - is now markdown in Gitlab. No big deal for a tech company, but this really is not the norm in institutional finance and we overcame many challenges to get here.
Where we have a gap is for what we used to call infrastructure, a term which covers a gamut of roles. Suppose you have a rogue DHCP server somewhere in the office. We don´t control the switch or have access to it. Quick - how would you track down where that is? It´s of course not difficult to figure out how to use wireshark or tcpdump, but figuring things out like that is a very different mindset from the bureaucratic enterprise finance technology mindset that seems to dominate in people we might hire from investment banks.
Or suppose we want to research server builds. What are our choices for 1U dual EPYC 7002 series with U2 flash? Or we would like 10GBaseT switches you can run Cumulus Linux on - what are the possibilities? Or we have people that know Linux, but nobody knows Cumulus yet. We would like to move to netops, and yet on the ops side of devops we are just beginning to learn.
[Some background is that we outsourced our desktop support, server support, and provision of managed servers to an industry-specialist managed service provider that we have now outgrown. It takes time to build new capabilities to take back control, and we are at the early stages of that].
I would say the distinct components of roles that might be of interest to readers of the forum and their friends are:
- frontline desktop support (mostly Windows, but share of less-technical Linux desktop users is growing)
- problem-solving for desktops - hmmm why is the latest Windows upgrade wiping hard drives including logs on some machines; why is Graham´s computer so slow
- front-line server support (we use SaltStack but our understanding and use of it is nascent)
- devops roles - working with very good developers to monitor + administer servers using config + code
- problem-solving for servers + network
- research for desktops, servers, network and physical office (how do we actually make our offices safe for example)
- administration: managing equipment registry; sending out hardware to people, etc
- any other problems that come up that need to be done that someone can uniquely do better than others
- client relationship managers (some people are very good at their job, and not very good with computers and require a higher-touch approach; or they may just have very little time)
- documentation and business analysis
- organisational design, management of all of the above
Many firms today create a box describing a role and look for people who can fit the box. You had better be able to do everything it says on the box -- and don´t you dare step outside of it. That is not how we have chosen to do things; we do not have hard and fast divisions between roles and we allow people to get varied experience although we do make _distinctions_.
Who would be my ideal sort of person? Well, everyone is different. But I would hire Rachel By the Bay in a flash - a serious hacker that likes helping people.
Credentials are interesting pieces of information, but they are only that. One chap I hired - a contributor to the D programming language - did not go to university; he did not even finish high school. Another was a baker in Spain. He studied technology, found the job market in 2008 difficult and so worked for his father´s bakery business until recently. But he was also heavily involved in the Linux Kernel Newbies project (documentation) and contributed some patches to the kernel itself. He would not have gotten past HR in many other financial firms, but I snapped him up - and he is doing an outstanding job on technical documentation with us. Mature eighteen year old that got into working with hardware to earn extra money by buying, fixing, and reselling computers when he was at school turned out to be a very good hire too.
This being said, I think we have pretty high standards - we just care about different things from some others: you should be able to figure difficult problems out and generally, you know, like and have a flair for working with computers: *mechanical sympathy*. We assess this as part of our selection process, but if you can point to work you have done that is public then it is easier to assess and make sure not to miss outstanding talent.
I said I was responsible for technology across the firm. I will be co-CEO shortly, so I have quite a lot else to do. But last year I set bonuses for the people we have in these roles, and funnily enough I bumped them up quite a lot higher than had been previously proposed. Why? Because although we were lucky enough to recognise the pandemic as the challenge it was as early as January 2020 there was an incredible amount of work to do to be ready for it in time, and without the hard work and creative problem-solving of people in these roles, maybe we would not have had a company at all. So I think there is a recognition of the importance of technology generally, and these roles specifically.
We pay pretty fairly initially and over time recognize accomplishment by paying well to very well. Our mindset is relational rather than transactional - we do not have a mindset of narrow short-term optimization. In the past years I have found that approaching a goal indirectly - by moving towards what you are drawn to - can be much more profitable than short-time calculation and optimization.
The longer-term stakes are high, but we try to keep the short-term pressure as low as possible, although we might not on every occasion succeed, particularly when it comes to supporting a trader who has a large amount of risk and is being let down by a failing computer. Even in those conditions, most people are pretty reasonable here - you don´t get much shouting or general interpersonal obnoxiousness. Many roles we are filling now are not like the supporting stressed-trader role though - researching and building new choices does not have a short-term time-element aspect at all.
Let me know any questions. Email me lisharc at symmetryinvestments dot com and cc jthompson at symmetryinvestments dot com if you would like to apply. As well as a bio, please send links to publicly-accessible work you have done (code, designs, blogging, social-media etc) as well as a note describing why you are interested in working with us, and what you think you could bring.
Thanks.
Laeeth.
I have been lurking on ServeTheHome for a couple of years now, but just did not have time to participate much until now.
I would like to introduce myself and the company I work with and then describe some of the opportunities available and the sorts of people we are looking to hire. Bottom line upfront - we are hiring remotely across a gamut of roles and can consider people in most locations. Full-time is ideal, but for very capable people we can be flexible - part-time or longer-term fixed-term contract (less than a few months is not very efficient for us).
Symmetry Investments is a post-startup alternative asset manager - c $8.9bn of assets under management, with around 230 people. Founded in 2013 (managing money since 2014), we have offices in London, HK, Singapore, and Jersey, with a US office under way.
I am responsible for technology across the firm, and co-direct research. My path to the role was unconventional, and our approach to technology is informed by the different path I took; my first contribution to public-domain software (open-source didn´t have that name then) was to Tom Jennings´ Fidonet BBS in 1989. I used to run a BBS of my own - Absolute Zero - and edited the "security-research" section on 01 for Amiga, a popular London bulletin board. You can read some of my more recent writings on Quora, and I have a Twitter account - @Laeeth.
Along with the obvious benefits of technological progress since the 8-bit days, I feel that we lost something. The BBC Micro at school came with a pretty good user-guide, including a schematic. You could hope to understand every part of the machine and with a basic knowledge of electronics and the technical data sheets on the chips you could even design and build your own computers (now we would say embedded devices). Today everything is so complex and there is layer upon layer of abstraction and that mindset of figuring things out isn´t generally how we approach hardware today, especially in the enterprise. Have a problem? Well in that case you surely need a solution, and since you are a serious enterprise then you must pick from one of the plethora of predigested enterprise solutions available for that purpose. You must be crazy to want to understand it or do it yourself - leave that to the experts.
Our experience has been that although a basic approach of favouring getting your hands dirty may not seem optimal, might even seem wasteful from a narrowly commercial perspective, that trends in enterprise technology have gone so far that the opposite is true. If you understand something then you can reason about it, change it, know what is easier than how it sounds and what is much harder. Or to put it into enterprise-speak (I studied economics), such an organisational capability creates adaptiveness and strategic optionality. Practical experience is also the source of innovation.
When I became more directly involved at Symmetry in 2017 we used perforce. I think Google use perforce, but they have a lot of tooling on top and we did not. So nobody read anybody else´s code - nobody even had access to it. I set up a Gitlab server myself because at the time we lacked capabilities (to work with git, with Gitlab, and even to build and manage Linux servers). That isn´t typically how somebody in the role I had at the time (one of the three people running Symmetry) would approach things but it was by far the best choice given the constraints.
That´s changed a bit, especially on the development side. We wrote our own domain specific language for reporting and integrating internal systems. We exploit the metaprogramming and compile time function execution capabilities of the D programming language to automatically wrap and register straight code written in D. So for the maths part of the standard library we loop through all the symbols in std.math from Phobos and register them. D has some libraries, but C++ has more. So we made an internship project to call all of C++ from our language using CERN´s cling and it basically just works - talk before the Compiler Research Group at Stanford IRIS-HEP is here, and Alexandru wrote a piece for the LLVM blog that came out just recently.
We have Andrei Alexandrescu working with us on the development side (he joined last year) and recently Amaury Sechet, author of the SDC experimental compiler, co-creator of Bitcoin Cash and technical lead of Bitcoin ABC started working with us. We are quite involved in the D language community and have open-sourced (and develop openly) quite a few internal projects.
We started hiring remotely from the moment I became involved, and the pandemic accelerated that - we have been forced-remote for now since Feb 2020. I would say that the development side has been remote-first for a while; and the rest of the company (trading, legal, compliance, accounting, operations, research, and HR) is moving towards remote-first. The employee handbook - like many other internal documentation projects - is now markdown in Gitlab. No big deal for a tech company, but this really is not the norm in institutional finance and we overcame many challenges to get here.
Where we have a gap is for what we used to call infrastructure, a term which covers a gamut of roles. Suppose you have a rogue DHCP server somewhere in the office. We don´t control the switch or have access to it. Quick - how would you track down where that is? It´s of course not difficult to figure out how to use wireshark or tcpdump, but figuring things out like that is a very different mindset from the bureaucratic enterprise finance technology mindset that seems to dominate in people we might hire from investment banks.
Or suppose we want to research server builds. What are our choices for 1U dual EPYC 7002 series with U2 flash? Or we would like 10GBaseT switches you can run Cumulus Linux on - what are the possibilities? Or we have people that know Linux, but nobody knows Cumulus yet. We would like to move to netops, and yet on the ops side of devops we are just beginning to learn.
[Some background is that we outsourced our desktop support, server support, and provision of managed servers to an industry-specialist managed service provider that we have now outgrown. It takes time to build new capabilities to take back control, and we are at the early stages of that].
I would say the distinct components of roles that might be of interest to readers of the forum and their friends are:
- frontline desktop support (mostly Windows, but share of less-technical Linux desktop users is growing)
- problem-solving for desktops - hmmm why is the latest Windows upgrade wiping hard drives including logs on some machines; why is Graham´s computer so slow
- front-line server support (we use SaltStack but our understanding and use of it is nascent)
- devops roles - working with very good developers to monitor + administer servers using config + code
- problem-solving for servers + network
- research for desktops, servers, network and physical office (how do we actually make our offices safe for example)
- administration: managing equipment registry; sending out hardware to people, etc
- any other problems that come up that need to be done that someone can uniquely do better than others
- client relationship managers (some people are very good at their job, and not very good with computers and require a higher-touch approach; or they may just have very little time)
- documentation and business analysis
- organisational design, management of all of the above
Many firms today create a box describing a role and look for people who can fit the box. You had better be able to do everything it says on the box -- and don´t you dare step outside of it. That is not how we have chosen to do things; we do not have hard and fast divisions between roles and we allow people to get varied experience although we do make _distinctions_.
Who would be my ideal sort of person? Well, everyone is different. But I would hire Rachel By the Bay in a flash - a serious hacker that likes helping people.
Credentials are interesting pieces of information, but they are only that. One chap I hired - a contributor to the D programming language - did not go to university; he did not even finish high school. Another was a baker in Spain. He studied technology, found the job market in 2008 difficult and so worked for his father´s bakery business until recently. But he was also heavily involved in the Linux Kernel Newbies project (documentation) and contributed some patches to the kernel itself. He would not have gotten past HR in many other financial firms, but I snapped him up - and he is doing an outstanding job on technical documentation with us. Mature eighteen year old that got into working with hardware to earn extra money by buying, fixing, and reselling computers when he was at school turned out to be a very good hire too.
This being said, I think we have pretty high standards - we just care about different things from some others: you should be able to figure difficult problems out and generally, you know, like and have a flair for working with computers: *mechanical sympathy*. We assess this as part of our selection process, but if you can point to work you have done that is public then it is easier to assess and make sure not to miss outstanding talent.
I said I was responsible for technology across the firm. I will be co-CEO shortly, so I have quite a lot else to do. But last year I set bonuses for the people we have in these roles, and funnily enough I bumped them up quite a lot higher than had been previously proposed. Why? Because although we were lucky enough to recognise the pandemic as the challenge it was as early as January 2020 there was an incredible amount of work to do to be ready for it in time, and without the hard work and creative problem-solving of people in these roles, maybe we would not have had a company at all. So I think there is a recognition of the importance of technology generally, and these roles specifically.
We pay pretty fairly initially and over time recognize accomplishment by paying well to very well. Our mindset is relational rather than transactional - we do not have a mindset of narrow short-term optimization. In the past years I have found that approaching a goal indirectly - by moving towards what you are drawn to - can be much more profitable than short-time calculation and optimization.
The longer-term stakes are high, but we try to keep the short-term pressure as low as possible, although we might not on every occasion succeed, particularly when it comes to supporting a trader who has a large amount of risk and is being let down by a failing computer. Even in those conditions, most people are pretty reasonable here - you don´t get much shouting or general interpersonal obnoxiousness. Many roles we are filling now are not like the supporting stressed-trader role though - researching and building new choices does not have a short-term time-element aspect at all.
Let me know any questions. Email me lisharc at symmetryinvestments dot com and cc jthompson at symmetryinvestments dot com if you would like to apply. As well as a bio, please send links to publicly-accessible work you have done (code, designs, blogging, social-media etc) as well as a note describing why you are interested in working with us, and what you think you could bring.
Thanks.
Laeeth.