Position: Senior backend developer
Company: kaplink.org
Category: Ruby
Experience required: 3y
English level: upper
Published: 2021-10-01T00:00:00+03:00

**The role and impact you’ll have:**

We're looking to bring in highly experienced backend engineers to help us grow quickly through high-quality scalable solutions. 
We're looking for somebody who has worked on major architectural problems before and is looking to go to the next level themselves as part of a still small engineering team. You'll split your time between figuring out the right technical solutions to push the business forward, mentoring other engineers on the team, and being a hands-on part of programming the solutions. You will work across our engineering squads depending on where the need is the greatest at the time, which you'll be a part of deciding, and report directly to the VP Engineering. 

**What you’ll be doing:**

- Split your time between coming up with software solutions (including architecture), helping/mentoring other engineers to implement these solutions, and programming yourself (in that order of priority).
- Work closely with product managers to understand goals (short and long-term) and make sure other engineers are making the right technical decisions to achieve them. Possible product areas include: claims, expanding into new markets/products, and partner integrations.
- Hold yourself and the team to high technical standards
- Figure out ways to leverage our technology for bigger impacts

**Your experience and abilities:**

- 6+ years experience in backend development working on complex distributed systems, including micro-services and different database technologies.
- You either know Ruby on Rails or are excited about getting to know it well, while also looking out for new technologies and programming languages we should take advantage of.
- A strong interest in learning and keeping up with industry standards. You don't need to be an expert in everything, but if there's a problem we need to solve, we expect you to be able to do the deep research to figure out how we need to solve it.
- You can distill a complex problem into multiple parts and clearly communicate your technical vision to the team