What you will need:
At least 3 years of proven commercial development experience
Willingness to work with a functional language for most of the time
Ability to work in a distributed team
Strong analytical skills, experience with debugging complex systems
An good standard of English with strong written, verbal, and presentation skills, including experience presenting to clients
Must have Requirements:
Good knowledge of functional language paradigm (immutability, composition, pure functions)
Knowledge of Vanilla JS (event listeners, DOM manipulation)
Knowledge of HTML5/CSS (flexbox, tailwind, PostCSS)
Knowledge of HTTP/REST
Nice To Have
Experience with building and designing REST API services from scratch
Experience with building scalable distributed systems
Experience with Elixir and Phoenix Framework
Experience with Webpack
Experience with GO lang
Hands-on experience with Docker
Knowledge of test automation tools (Cypress, Puppeteer)
Knowledge of deployment processes, CICD
Fundamentals of Cloud Computing and AWS
Knowledge of some SEO principles
Knowledge of graphics software such as Adobe Suite, Photoshop etc.
Interest in usability, UX, UI design
Currently, we are looking for Elixir Developers for a San Francisco startup specializing in Machine Intelligence and Data Analytics. You’ll be working on a state of the art data mining platform. The project is currently in development for more than a year, and it’s about to be deployed to the first customers. The team comprises 5-6 people, including stakeholders from the United States. The communication is solely in English.
Timeshifting is not required as most of the team is in +1/-1 CET timezone. The team is very agile, works in sprints, and is very much into value proposition design. The iterations are relatively short, and end users verify the application frequently.
We don’t require people with commercial Elixir experience. A strong desire to learn the language and professional experience with other programming language is sufficient.
The current focus of the team is on frontend development rather than backend; this might change over time but want our new team members to be ok with FE development, not just BE.