Firstly, let us give you some generic advice to help you finding your trainning:

• Seeking a trainning can be long and hard times, especially when your application is rejected or receive no response. Take courage!
• The training you choose has impacts on your future jobs. Take your time to get the good one.
• When it is time to plan your training to validate a diploma, it means you already learnt and practiced enough to work in a company. Trust yourself!
• Never say you can do and learn everything. You may be able to do a lot, but not knowing there are limits is a kind of incompetence (Dunning-Kruger effect). Be humble.
• People are proud of their company and job. But pride is not vanity. Flatter them with moderation. Do not praise too much when sending your application.
• You can achieve fulfillment in your job when you and your company share the same values. Seek the good company.
• Show your skills. If you've got side projects, a blog, a GitHub account, let your recruiter know. Acts are better than words.

Why is a practical training with us different ?

In order to produce high quality software it is required to be at the state of the art, both for features reason and for security compliance. There is no legacy code to maintain, but you will be able to learn everyday and be encouraged to learn in order to be source of proposals.

You will not practice software development but software engineering.

You will improve you understanding of what makes a good software design and will probably statisfy yourself that il helps to code evolution and reuse. No "quick and dirty".

You will be introduced to "best practices" in software production.

You will undoubtedly be surprised to know how a well made software is easy and fun to test (believe us!). So you will learn how to write unit tests/ integration tests et to become confident in your code running in production.

What are the constraints to take account of ?

Firstly, you need to know that our will to build sowftware by the book leads us to have higher expectations in our recruitment process than most companies.

About technologies. We do not use the most common technologies on the market. The "top" programming languages are mainly at this position because they are easy to learn and use (at least for basic use cases, so a quick learning curve eases the language adoption) rather than the language design quality, the features, the productivity impact or the inherent quality brought to the software. So, be advised your experience afterwards will not be on the most popular technologies.

The internships we may propose are mainly in Scala and may include libraries and frameworks like akka, akka-http, akka-streams, cats, cats-effect, fs2, ... We obviously do not expect you know these technologies especially because they use advanced functional programming concept that are rarely learnt in the academic program. Nonetheless, for this internship to be of mutual benefit, we expect the candidates to already master the basic concepts of the Scala language. We would recommend, for the developer aiming to join us or to improve his skills, the book "Functional Programming in Scala", by Paul Chiusano and Runar Bjarnason, edited by Manning, which is considered as a reference by the community and is more or less our minimal requirements.

For the same reason. Since skills development may be slow, we favour trainning periods of more than 2 months. Nonetheless, a candidate mastering the above mentioned book may help us to change our mind.

Finally, an other things to consider is that once you tasted quality software production, it may be hard to go back to "average" software production.

Ready to join us? Send us your resume and a letter of motivation, by email. Add the dates for the periods and the total time with us at the company.

We try to give an answer to every request. If you do not get any response, send us another email!