At ShopGun, we want to make your everyday better. More specifically, we're on a mission to help you, and all other people, get the products you actually need. We help about 1 million people every month and +500K people every week. We work with a core principle of putting people first in everything we do; we build products for people by people. Learn more about us.
Are you passionate about DevOps and wants to learn more and challenge not only yourself but also existing and future infrastructure decisions in an equally passionate company? If so, we're looking for you to become part of our team and bring your ideas to life. You’ll be joining our team of engineers, working closely with our other DevOps Engineer to maintain and improve upon our infrastructure, and together you will have the freedom to shape the foundation of our product.
You'll also be in close interaction with our other engineers to ensure they have the tools needed to easily deploy and manage their projects. These are written in many different languages such as Erlang, Go, Python, Node and PHP, so there's plenty to dig into.
If Amazon Web Services, Docker and Kubernetes are technologies that you find interesting, you'll have plenty of opportunities to explore. If you have fresh ideas, it's even better - we appreciate working towards efficient and modern infrastructure, and sharing and making your opinion heard is key to achieving this.
If you want to get an idea about how our current infrastructure is built, you can read up on it in the following articles:
At ShopGun, we value our experts. That's why we want you to not only give your best to improve the product but also yourself. We expect you to do your best to keep up to date on the technologies you use in your daily work and search out new avenues to take it to the next level.
It's important that you always have a focus on security and scalability, as we are in constant movement and need stable infrastructure to support this. Part of your job will also involve responding to incidents related to security and infrastructure to ensure low downtime - and learn from each incident in order to prevent similar problems in the future.
We expect that you're:
Though it's not required, we'd love that you're:
Got questions? Feel free to reach out to me, Sarah (Head of Engineering), so that we can clear anything up.
I look forward to hearing from you!