Back End Software Engineer

As a Back End Software Engineer at Ravelin, your primary responsibilities will include developing reliable and resilient software for our fraud detection platform. You will collaborate closely with data scientists and product managers to ensure our systems operate effectively under real-world conditions. Additionally, you will build microservices using Go, contribute ideas to product direction, and create internal tools and processes that enhance our software’s performance.

To apply for the Back End Software Engineer position at Ravelin, candidates should have substantial experience in programming languages, an understanding of data structures and algorithms, and experience with database design principles. Familiarity with testing and quality assurance practices, as well as version control, is essential. While not mandatory, experience with Golang, cloud technologies (like GCP, AWS, or Azure), and knowledge of microservices architecture and containerization will certainly be beneficial.

Ravelin is committed to fostering an environment of continuous learning and skill development for Back End Software Engineers. We provide a £1,000 Annual Wellness and Learning Budget that can be utilized for fitness, mental health support, and professional learning experiences. Additionally, we have scheduled Monthly Wellbeing and Learning Days, allowing team members time off to learn something new or recharge, ensuring that your personal and professional growth is always prioritized.

While proficiency in a variety of programming languages is helpful, Ravelin particularly values experience with Golang. Candidates should also have substantial and demonstrable experience in other programming languages and a solid understanding of data structures and algorithms. This diverse skill set enables our engineers to tackle complex challenges effectively, so familiarity with additional languages like Python can be particularly advantageous.

At Ravelin, the culture is a blend of collaboration, innovation, and support. We maintain a flat hierarchy, encouraging open communication and idea sharing among all team members. Our commitment to empathy, ambition, unity, and integrity shapes our work environment, making it both engaging and inclusive. With flexible working hours and a remote-first approach, we believe in promoting a healthy work/life balance, allowing our engineers to produce their best work while also enjoying personal time.

In responding to this question, focus on specific projects where you designed, built, or maintained microservices. Discuss your understanding of the principles behind microservices, how they enhance scalability and maintainability, and any challenges you faced during implementation. Be prepared to mention any tools or technologies you used, such as Docker or Kubernetes.

When answering this, speak about best practices you follow, such as writing comprehensive unit tests, integrating continuous integration/continuous deployment (CI/CD) pipelines, and conducting thorough code reviews. Mention any specific tools or frameworks you use to maintain quality and performance, and discuss the importance of user feedback in refining reliability.

Be honest about the languages you excel in, particularly mentioning Go if applicable. Explain why you prefer certain languages, touching on aspects like performance, ease of use, or community support. Sharing an example of a project where your preferred language had a significant impact can strengthen your response.

In your response, highlight your communication skills and the importance of understanding different roles in a team setting. Discuss how you foster collaboration by actively soliciting feedback, maintaining open lines of communication, and finding common ground to ensure all team members are aligned towards the project's objectives.

When asked about debugging, outline a systematic approach. Discuss the tools you use for debugging, how you isolate issues, and the methodologies (like rubber duck debugging) that help clarify your thought process. Provide an example of a complex bug you resolved and what you learned from that experience.

Use the STAR method (Situation, Task, Action, Result) when answering this question. Set the stage by describing the situation, the task you identified, the specific actions you took regarding your idea, and finally, the positive outcome that resulted from your contribution. This structure clearly illustrates your thought process and impact.

In your response, emphasize any hands-on experience you have with deploying applications on cloud platforms. Discuss specific services you’ve utilized and how they improved your workflow or application performance. If you have instances of migrating legacy systems to the cloud, don't hesitate to discuss those experiences, as they demonstrate valuable skills.

When discussing prioritization, specify methods you use, such as agile methodologies or project management tools. Mention how you assess urgency and importance for project deadlines, and provide an example where you successfully navigated competing priorities while still delivering quality work.

Share specific resources you trust, such as online courses, professional communities, or tech blogs. Discuss your approach to lifelong learning, whether it’s through formal education, personal projects, or attending conferences. Illustrate the importance of staying informed in the fast-evolving tech landscape and any recent advancements that you've applied to your work.

Discuss the version control systems you have used, focusing on Git. Explain your familiarity with branching strategies, handling merge conflicts, and the significance of version control in collaborative coding environments. Providing an example of a time version control helped resolve a team issue can also enhance your answer.