Building what people actually use.
Meet the Product Development Team
We design and develop IPRally’s core application, feature by feature, release by release, with a focus on clarity, speed, and usefulness.

🎯 What we’re here to do
We’re responsible for the product itself - the thing customers see and use.
We work across the stack to build the UI, backend, and systems behind IPRally’s search and analysis features. That includes evolving our architecture and balancing new development with long-term maintainability.
We aim for clear, understandable code. Less flash, more finish.
We work across the stack to build the UI, backend, and systems behind IPRally’s search and analysis features. That includes evolving our architecture and balancing new development with long-term maintainability.
We aim for clear, understandable code. Less flash, more finish.
🧪 How we work
Everyone is trusted to make decisions, write code, and take things all the way from problem to solution. You can stay deep in one area or move between frontend and backend depending on your interests. We keep the process lightweight: minimal meetings, direct communication, and focus time when you need it.
⚙️ Our tools & tech
Here’s a snapshot of what we use day to day:
Clojure & ClojureScript
Main languages
Python
For integrations and supporting logic
PostgreSQL
Database of choice
GitHub
Version control and collaboration
💡 What guides us
📚 What new teammates usually ask
Will I be stuck in just the frontend or backend?
No. We encourage trying both, and you can shift based on what you enjoy.
How do you support learning?
You’ll have a personal learning budget (€1,000/year), plus time set aside to experiment or try something new.
How close is engineering to product decisions?
Very. Engineers are involved early and often, from shaping the idea to delivering it.
What’s your approach to speed vs. quality?
We move quickly, but carefully. Small, safe releases help us stay fast without adding risk.
Can I work remotely?
Yes. Many of us are based in Finland and drop by the office now and then, but remote is fully supported.
What’s the team’s approach?
We keep it calm and full-stack. The goal is long-term usability, not short-term hacks. We build things to last.



