Job description

📍 Project/Client: Cryptocurrency Payments Platform within a Logistics-Fintech hybrid

🌍 Location: Remote (EU-based)

📅 Start Date: ASAP

🌐 Residency: EU citizens or residents only

We’re looking for an experienced Golang Developer to join a fast-evolving cryptocurrency payments initiative. This is a hands-on, problem-solving role for someone who doesn’t just want to write code, but wants to make real technical impact and help steer a project that is currently being reshaped for the better.

🧠 About the Project:

The client, a logistics company entering the fintech space, has acquired a Go-based freight management system (frontend in Next.js, hosted on GCP). The goal is to integrate this system with their main ERP (based on Microsoft Dynamics). However, the acquired system was built in an overly academic and over-engineered way — heavy use of CQRS, event processing, Elasticsearch as a read model, and fragmented microcomponents with poor cohesion.

Right now, the focus is on bringing sanity and business value back into the architecture. You would be joining at a critical point, where the company is finally open to rethinking how the system is structured and maintained.

✅ What We’re Looking For:

• 4+ years of professional experience with Golang

• Strong knowledge of design patterns, idiomatic Go, and clean architecture

• Experience with PostgreSQL, MySQL, RESTful and GraphQL APIs

• Familiarity with microservices, Docker, and containerized application design

• Hands-on experience with CI/CD pipelines, Git, and DevOps practices

• Understanding of security, cryptography, and performance optimization

• Experience with AWS, GCP, and Infrastructure-as-Code (nice to have)

🛠️ What You’ll Be Doing:

• Refactor and simplify the read model (e.g., moving from Elasticsearch to SQL-based queries)

• Propose and implement practical, scalable architectural improvements

• Collaborate with developers, QA, and product stakeholders in an agile environment

• Integrate the Go backend with Microsoft Dynamics and other external systems

• Participate in code reviews, architectural discussions, and sprint planning

• Optionally, provide technical leadership or architectural guidance, if you're interested

🤝 Why Join?

• Opportunity to influence core system architecture and technology decisions

• Open-minded management — the team is ready for change, with the right leadership

• Chance to drive real impact rather than just “close Jira tickets”

• A technical challenge with room to grow, shape, and truly fix something broken