Senior Clojure developer
Infine is looking for a senior Clojure developer able to work partly remotely in Helsinki, Finland.
What is Infine?
Infine makes it easy for food resellers and producers to analyze their products from all sustainability angles. The software behind the service reads in product data and provides results such as the risk of forced labor, endangered fish species, CO₂ Footprint, and animal welfare. The goal is to make it so easy to check relevant features and risks for product assortments that they become more commonplace; we believe you need to know your challenges before you can improve.
Simplified, we are selling SaaS, but the business model is a bit more sophisticated.
Infine has a small team of seven employees and a group of advisors. We are expanding into new markets this year and have more to do than we have time for.
What are we looking for
We are using Clojure full-stack and don’t really have time for a long ramp-up period, so Clojure experience is important.
We are looking for a developer who doesn’t need, or even want, a fully specified issue to work on a solution. You would need to take responsibility for implementing whole solutions, and to do that, you might need to talk with non-technical experts to figure out the exact requirements, go Wikipedia hunting for numerical algorithms, or browse through EU sites for relevant regulations. It might be enough to change the frontend or backend, but often both are needed. We want people who prefer simple, readable, and maintainable code over clever code.
You will be the second technical person in the company, so you need to get familiar with the whole system, also for redundancy. Given the rapid pace of change, you can also have a significant influence on the overall architecture. We also don’t have a settled AI/LLM strategy, though we want to keep the core of the product fully understood by our developers (not just how the code works, but why it is designed the way it is), so it would be valuable if you could help shape it.
We work remotely most of the time, but we find it important to meet in person at our Helsinki office now and then. At the beginning, we would work more remotely until you get up to speed, but later, you would need to live close enough to show up a couple of times a month. Most of the team lives in the capital area, with one person living part-time in Oulu, and the rest in Helsinki.
We are looking for an individual with a long-term commitment, with no cross-border contracts. Primarily an employment contract, also open to freelancers, but not interested in consulting companies.
We can also accommodate part-time work, though probably anything under 80% would make it difficult to keep up.
These things would also be nice:
– You want to save the world, or at least make it a better place.
– Experience with LCA/carbon footprint calculations.
– Experience and interest in sysadmin/devops and even generic IT support.
– Note that we don’t have dedicated people looking after our production environment, company website, or email.
– You are familiar enough with neurodivergence to understand that people work in different ways.
– Understanding Nordic and/or Baltic languages.
We aim for a monthly wage of 4000–6000€, depending on experience, and it is also possible to become a shareholder.
How to apply
Please apply by May 3rd by sending an email to recruitment ät infineinsight.com with your CV and a free-form description of why you think Infine would be good for you, and you for Infine. All reasonable applications will get an answer, so you know what’s happening.
Next steps: A short, half-hour video call to get quick QA and clarifications for both sides.
Then, a 1.5-hour face-to-face technical interview with the CTO at Infine’s office in Alppila, Helsinki. And finally, an interview with the larger team at the same place.
Simple process: We respect your time and won’t require you to spend any more than we would. There will be no assignments to take home or required portfolios; we understand that professionals are busy and usually work with codebases that cannot be published. There won’t be coding sessions on paper where you would have to work without your usual tooling, but part of the interview might involve pair programming, where the interviewer has editor control, and you would give higher-level directions.