Locations View all
Companies View all
Job Type

Back-End Developer (Python)

This job opening has expired! View other jobs

Solar Monkey does not offer visa sponsorship

You must be eligible to live and work in the EU.



  • You have a solid understanding of a server-side language (preferably Python) and follow the latest developments.
  • You have considerable experience with building API's or websites as well as background tasks.
  • You are familiar with a couple other programming languages.
  • You have at least 1 year of experience in a similar role.
  • You can write a clear specification or pitch for changes (yes, writing skills are important).
  • You are able to pick up new things quickly.
  • You want to work 32 to 40 hours a week.
  • You are able to work with a diverse group of people. You’re not a rockstar or code-ninja—you’re a human of some form!
  • You must be eligible to live and work in the EU.

Compensation & Benefits

  • We’re a startup, so we can’t offer a highly competitive salary. But we don’t expect a free lunch either. We have around €40-50k per year available, depending on your experience and skills. We do offer stock appreciation rights, which will vest in 4 years.
  • The chance to learn exciting new things as we grow, whether that’s front-end code, GIS, or server infrastructure!
  • A fun team that values long-term thinking, self-empowerment, and eagerness to improve.
  • A healthy workplace where you regularly work the number of hours you signed up for, and where you are able to get 8+ hours of sleep.
  • Lots of freedom in when and where you work, and how you solve problems.
  • Lots of impact on our product, our culture, and the solar world!

Job description

You can build architecture for new features from the ground up and educate others on the why and how. You also have an eye for quality. We'll also trust you to know the difference between SLI’s and SLO’s and help us track and meet them.
We're located in Delft, the Netherlands, but you can also work partially remotely.

The company

Life at Solar Monkey

We combine in-person and online communication (through Basecamp & Zoom), where it might not surprise you that the business side leans toward the former and the development team leans a bit toward the latter form of communication. This enables a very flexible working place, and nobody tells you where or when to work, trusting that you know best how to build on your own strengths.
We don’t uphold a very strict methodology for design, but we do evaluate and improve our process continuously. It’s probably best described as a combination of Kanban and Scrum. This means that we are quite agile and can implement new features quickly when necessary. Our work is divided into clear epics and stories that are tracked in PivotalTracker.
Nowadays we have almost a full continuous delivery pipeline running. Everything we do runs in Docker containers. We’ve written a small helper app that uses Hashicorp’s Nomad to schedule those containers in our production and test environments. We are slowly expanding this into a commit-to-deploy trunk-based integration strategy.
The Joel Test
Never heard of it? See this famous blog post: joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code
1. Do you use source control? → Yes, in multiple Git repositories.
2. Can you make a build in one step? → Yes.
3. Do you make daily builds? → The CI tests immediately and we deploy bi-weekly.
4. Do you have a bug database? → Yes.
5. Do you fix bugs before writing new code? → In a healthy balance.
6. Do you have an up-to-date schedule? → Yes.
7. Do you have a spec? → Yes.
8. Do programmers have quiet working conditions? → Depends on where you want to work.
9. Do you use the best tools money can buy? → We have an allowance for a good laptop & laptop standard. For the rest, we use free tools. What else do you need?
10. Do you have testers? → We have automated tests and before a release, we test with the whole company.
11. Do new candidates write code during their interview? → Yes!
12. Do you do hallway usability testing? → Yup.