Author

Topic: Rialto.ai - Looking for a data engineer with flair for trading *** (Read 1227 times)

member
Activity: 64
Merit: 10
// Update //

We have received frequent question about non-European applications.

Unfortunately this time we have to give advantage to the European applicants.
The reason behind is, that the team is international and works remotely, but we have regular monthly WorkWeeks when we meet somewhere in Europe and it makes it much easier, faster and cost effective if a member is located closer to Europe.

Thank you for understanding.
Best
member
Activity: 64
Merit: 10
It is a full time position, meaning that the average is 40h/week. In practice of course it varies from week to week based on our sprints.. Please PM me for more information.
newbie
Activity: 3
Merit: 0
Is this meant to be full-time, per project or ... ?

Tnx in advance.
member
Activity: 64
Merit: 10
Hello guys,

Rialto.ai is looking to strengthen their international team (UK, Slovenia, Macedonia) with a Europe based data engineer.
Ideal candidate would have interest for trading, arbitrage, and market mechanisms, however it is not a must.

Your role would be to connect our analyst and market researcher with other executing engineers in the trading team.  
You would be responsible for the full stack of applications required to run the arbitrage and market making business.
Part of you tasks would require assistance in designing, developing, and maintaining our data pipeline.

Definitely you will have the opportunity to explore new technologies and better ways to connect the emerging cryptocurrency markets.

You would need:

  • Desire to work in an exciting field of cryptocurrencies;
  • Graduate or student in Computer Science, Computer Engineering or Information Systems;
  • Proficiency in C++, C# or Java;
  • Availability of at least 6 months;
  • Ability to travel monthly to our WorkWeeks (different locations across Europe);
  • Fluency in English.

For any additional questions feel free to post a comment or contact us on [email protected].

See the posting:
Jump to: