Senior Golang Engineer

Why work for General Marketplaces (GM)?

Ricardo, tutti.ch & anibis.ch are services with a positive impact on the world. Reducing waste by giving unused items a new home is a cornerstone of sustainability. Today there are already over four million people using Ricardo, tutti & anibis but we are not done yet. We are working hard on making it easy for everyone to participate.

We have modern tech-stack and interesting challenges ahead. We know that keeping up with technology is no easy feat, which is why we have dedicated training and conference budgets for every engineer.

What is GM Engineering?

You will be part of GM Engineering specifically on the tutti & anibis applications. We have 3 remote-friendly teams working in various domains. Each team consists of ~7 engineers located in five countries (Switzerland, France, Germany, Serbia, Vietnam).

Each engineering team has the following 2 main responsibilities:

1. Take ownership of their domain, from design to implementation & deployment
2. Build the tech that powers our marketplaces & empowers our users

As a Senior Golang Engineer you’ll be part of all aspects of the engineering cycle. You’ll develop and design software. Knowledge sharing is equally important, this includes code reviews as well as Golang Guild contributions, so be expected to mentor peers and other engineers. We have a view of leaving the codebase in a better state than how you found it, so continual code improvement is part of your day to day.

How do we work?

We are a team distributed over multiple locations. Therefore, our default work mode is asynchronous. We write a lot and try to communicate as concisely as possible. We limit our ”Work in Progress” so that you can focus on the task at hand.

Usually, work is assigned to two people so that you always have a sparring partner. This gives you the flexibility to plan the work as you see fit and to pair when needed. It is also a great way to share the knowledge in the team.

Every day we have a short (15-30 min) team daily, where we sync with each other on what we worked on, highlight any blockers we’ve encountered or share what we've learned.

Because the activities on tutti & anibis never stop, we have to keep the lights-on 24/7. For that we have a mature on-call organization.

Requirements

What we are looking for:

Engineers are expected to be proficient in their technology, IDE & operating system of choice, we do not dictate your exact tooling, but you need to be comfortable to perform all aspects of the engineering process efficiently. We are looking for someone with strong experience in Go, as well as working knowledge of CI/CD processes. Additionally, you would have experience with distributed systems running on Kubernetes on AWS.

Our ideal employee would be self organising and would not have to be told what to do on every single detail, they would be given a general task or direction, and as part of their due diligence they would uncover, and execute on what is needed to get from point A → B. When you notice a problem, you don't look the other way; you either fix it or come up with a plan. You are curious and want to understand how things work. You are not afraid to ask for help and you are willing to help other engineers.

We know engineering is a vast field, and nobody can know everything, but you should be familiar with some of the following tools and technologies:

• Strong proficiency in Go programming language.
• An understanding of microservices architecture and RESTful API design.
• Experience with relational and NoSQL databases.
• Familiarity with containerization technologies such as Docker and orchestration tools like Kubernetes.
• Knowledge of best practices in software development, including code reviews and automated testing.
• Strong problem-solving and debugging skills.
• Good communication and collaboration skills.

Recruitment Process:

1. Screening call with HR representative
2. Hiring Manager Call with Engineering Manager
   1. Introduction team, role, and responsibilities (45min)
3. At home technical task
4. Interview Day
   1. Coding Interview (60min)
   2. Architecture & Design (60min)
   3. Meet the team (25min)
   4. Meet the Director (25min)
5. Decision within 48 hrs after interview day