We built DICE for fans. We’ve gone from being a tiny six-person company in London to a 90+ person (and growing) company that is now launching around the world.
DICE is obsessed with design and technology and on a mission to be the world’s best platform to discover and buy tickets to amazing live experiences. The best artists all work closely with us to make sure their tickets go to their fans, not scalpers or touts.
WHAT WE'RE LOOKING FOR
We’re looking for Backend Engineers with strong technical skills and potential. You’re a team player who can collaborate with people in various roles and levels of technical ability, and understand the delicate balance between moving fast & iteration against building tested, resilient code.
You may not have much experience with Elixir, but you are excited by learning new technology and have a desire to grow in this area, then this the opportunity you've been waiting for!
Our backend apps are written mostly in Elixir and Go. They feed various information to our award-winning apps with GraphQL and REST API and handle millions of transactions for our ticket sales in a reliable manner.
Our code is hosted in GitHub which we use for creating pull requests and carrying out code reviews. Our pipelines are managed by Travis CI and each commit will build a Docker container. We spin up short term Kubernetes clusters with the new feature branch of the app you are working on and all the other various services so that our QA team can test your new feature in the entire stack. Once passed code gets merged and pushed to the production cluster.
We are always open to making changes and improvements to our workflow and code base for the benefit of the team and product.
HOW WE WORK
As a Backend Engineer at DICE, you’ll work in cross-functional, collaborative teams alongside Mobile App Engineers, Frontend Engineers, Product Managers, Product Designers, User Researchers, DevOps, QA Testers and Growth Managers. You’ll also be working on projects with people outside on the Product team, including Creative, Fan Support, Accounts & Venues. You will also get chances to head down to tackle some interesting technical problems such as scalability, reliability, security and internal tools.
As we grow, we’re planning to transition into squads and disciplines, while keeping the teams flat. Each squad will have a dedicated goal and each discipline will keep horizontal relationships.
You and your team will be responsible for an overall company goal, rather than building a specific feature - you'll have a direct impact on both what we build, and how we build it.
As a Product team, we meet every two weeks to discuss hurdles we’re facing across the company and work together to overcome these. As a discipline regularly to discuss tools and techniques to update out codebase and improve processes, as well as put our heads together about best approaches when faced with a new technical challenge.