Golang Back-End Engineer
Ziglu, United Kingdom

Having launched to the public in June 2020 Ziglu are bringing challenger bank ethos to the crypto sector. For our customers we provide simple, safe and affordable access to the major crypto and fiat currencies alongside traditional banking services. We are regulated by the FCA (EMI license) and registered under 5MLD making us one of the first, fully regulated, crypto challengers in the UK.

Are you a mid/senior level accomplished professional that is looking for a new career within a top rising FinTech crypto challenger? Do you have experience in backend engineering primarily using Golang to develop micro services for transactional and event driven architectures in the Financial or FinTech sector?

We are looking for engineers to help design and deliver a range of new services for our cutting edge banking platform and digital asset exchange.You need to be enthusiastic, hardworking, proactive and willing to enhance yourself as well as the company.

We are looking for mid/senior level engineers that take ownership of their work. This means identifying and liaising with all stakeholders as and when needed to maintain delivery progress. You'll need to be proactive about identifying blockers, seeking help and chasing vendors for answers and support. There is no time to delegate these responsibilities to other people or wait passively for a problem to fix itself. You'll be surrounded by people that want to see you succeed because we all share in each others success.

Reporting to our Head of Engineering in the Core Engineering team which is responsible for the architecture, design, development and support of the Ziglu Digital Asset Exchange and ancillary services. Your primary responsibilities will be:

• Evaluating the best technologies and picking the right tools for the tasks in hand
• Establishing standards for backend development
• Debating, discussing, and deciding on the systems architecture
• Designing our microservices, APIs, and systems
• Writing beautiful, elegant, easy to maintain, and understandable code for backend services
• Documenting and describing your decisions in diagrams and comments
• Ensuring high performance and responsiveness of our APIs
• Maintaining the end-to-end software delivery cycle

You may be required to participate in interviews and will have an influence in hiring plans for teams working around you. You will also be required to provide input and interact with the Frontend, Platform, QA and business stakeholders.

At Ziglu we expect our engineers to support their own code production. Hopefully you'll be sipping your own champagne but if you made a pigs ear of it you'll be eating your own dog food until its fixed.

You will join a fast-paced rising fintech startup. As such, it’s important you know a bit about our environment, technology, and tech stack. We are:

• A small, high-profile core tech team
• A no-nonsense, open-minded, and radically candid culture
• Using open peer debate and searching for best ideas as core approach to decision making
• Using microservice-only docker containerised architecture
• Using automation-only cloud-agnostic infrastructure management
• Practicing an automation-first QA approach, with minimal, but reasonable manual component
• Using a comprehensive testing pyramid, heavy unit, integration and user testing automation
• Using Go as our first choice for microservice development
• Using BDD and TDD as our primary approach, with a strongly test-driven CI/CT/CD pipeline
• Assuming gitflow based peer review to be mandatory process

Requirements

Following the Must/Should/Could language convention, you need to tick the following boxes:

• MUST have good knowledge of web environment, API designs, GRPC, HTTP, REST, WebSockets
• MUST have good knowledge of Cloud Native and Twelve Factor Application development
• MUST have wide experience with PostgreSQL or MySQL
• MUST write reusable, testable, and efficient code
• SHOULD have 2-4 years (mid)/4+ years(senior) of commercial work experience of Golang
• SHOULD have experience of Kafka and event driven architectures
• SHOULD have good understanding of Linux systems
• SHOULD have good working knowledge with NoSQL key-value or document store systems
• SHOULD have experience in defining low level architecture of the systems
• SHOULD know how to interact with front-end developers and define APIs and integrations
• COULD have a good understanding of the principles of highly available systems
• COULD be prepared to review the code of your peers and for a review of your own code
• COULD be looking to set the bar and lead on standards of code quality
• COULD have experience in designing and implementing low-latency, high-availability, and p

Job Rewards and Benefits