Rakettitiede allows its consultants to focus actively on software development and take part in solving unique problems in the clients’ product development teams.
Our culture dictates that each of our rocket scientists gets to choose their own placement and task. In our experience, this helps to keep the developer motivated, excited and happy – and that’s when the magic happens.
Experiences of a rocket scientist: optimising a telecommunications network
The gig?
💬 “Optimising a telecommunications network with national coverage.”
Challenges?
💬 “Configuring base station operations to adapt according to use. The optimisation model was developed by a team with expertise in telecommunications networks and machine learning. Other interesting challenges popped up as well: an insane amount of configuration data from the base stations that needed to be read daily. Reading the XML configurations quickly enough was no mean feat, and we ended up carrying out semi-manual GC management in a Python app.”
Learning points?
💬 “I received varied and detailed insights into the workings of 2G, 3G ja 4G(+) networks and base stations.”
Technologies used?
💬 “The tech stack included PostgreSQL, ElasticSearch, an ETL process implemented with Python and, as a reference, an old Java implementation that was about to be discarded.”
Best part?
💬 “I thought the challenges were perfectly balanced: I could benefit from my good knowledge of the tools, and it was important to promote rigorous and proven software development methods as well as have an understanding of algorithms.”
– Edvard, Rocket Scientist #20
Want to learn more about our Rocket culture? Click here to read more!
Clients
We’re not going to make any guesses about what rocks your boat. Our clients include a wide range of industries and vary from start-ups to listed companies.
To prevent the Rocket from going into a tailspin, each consultant focuses on one client at a time. On average, a rocket scientist typically spends a couple of years in one place. We also do shorter gigs, but six months is usually needed to get a more in-depth understanding of the client’s mojo.
Experiences of a rocket scientist: software design to monitor an athlete’s performance
The gig?
💬 “Software design for an entire new generation of wearable devices for performance monitoring of active/professional athletes, mainly sport watches.”
Challenges?
💬 “Wearable devices have unique requirements not only regarding their hardware design but also software. Optimisations must be made in multiple dimensions: memory consumption, execution speed and perhaps most importantly the current consumption.”
Learning points?
💬 “All-encompassing design of MCU software in such a way so that current consumption of individual parts as well as their interactions is optimized to the exterme. In addition, device drive design and integration for modern components such as MEMS sensors.”
Technologies used?
💬 “ARM Cortex M4 MCU real-time OS software architecture, low power devices on multiple heterogenous buses, minimal BLE and USB stacks.”
Best part?
💬 “Opportunity to learn various new technologies and implement state of the art products.”
- Anonymous rocket scientist
Client stories
KONE - Intelligent lifts require a systematic but creative programmer
KONE's elevators challenge even the most experienced developer.
Rakettitiede supports Suunto’s core business needs
The tight interplay between Suunto’s software and hardware is what sets its products apart from its competitors.
Readpeak: Rethinking game analytics service technology with consultants’ support
GameRefinery’s service was revamped with the help of Rakettitiede’s experts.
Experiences of a Rocket Scientist: CSP deployment
The gig?
💬 “Evaluation of a Content Security Policy deployment and assistance with the deployment in the contents of a media service in connection with a publishing platform overhaul.”
Challenges?
💬 “Over the years, a lot of interactive content that had been implemented in various ways had been published on the website, and the client wanted these to function even after the deployment of the CSP. More recent articles often contain embedded media and content from other services. These content types and their JavaScript libraries and APNs had to be tested and inspected carefully to ensure that their functionality could be verified going forward.”
Learning points?
💬 “The deployment of a rigorous CSP in an old system can be really challenging or even impossible. We did manage to pull it off, however, since the back-end system was being upgraded at the same time. This enabled us to make use of broader architectural solutions that took the CSP into consideration.”
Technologies used?
💬 “Browsers offer varying amounts of support to CSPs and their different levels. In the evaluation, I used TypeScript and JavaScript executed with Node. The development team was in charge of adding dynamic rules as a part of the content creation funnel of the production system.”
Best part?
💬 “The best thing was to see how the solution is genuinely able to prevent things like user tracking on a website. We noticed that some users’ browsers were infected with malware, and we were able to limit their activity. The deployment was a success, which means the technology will see wider adoption in the future.”
– Joona, rocket scientist #36
Vacancies
Embedded & IoT
Bare metal, drivers, the web and code strings – these are a few of our favourite things.
We know our hardware and know how to bend the software without breaking it.
Full stack
Verticality beyond the cloud, enabling encounters between people and computers.
We build functional browser-based user interfaces and have command of both back end and front end technologies.
Mobile
Building demanding mobile software requires experienced developers.
We develop mobile applications for the client’s platform of choice — even for a C64.
Experiences of a rocket scientist: a new reporting and admin tool
The gig?
💬 “Around the turn of 2021, we created a new reporting and admin tool for compliance course records for a client. Their existing tool was being phased out and needed to be replaced. The courses and their records were accessible through the StudyTube platform interface, while the business unit hierarchy and course record metadata were managed using an admin tool. This data was used to create the actual reports in Microsoft Power BI. Two other team members were responsible for implementing the reporting component as well as the data pipeline from StudyTube to the admin tool.”
Challenges?
💬 “The project had a tight schedule, since the new tool had to be ready before the closure of the old one. The budget was also on the small side, so we had to prioritise the features we needed and make cutbacks where possible. The work was made easier by having the old tool as a reference, as it helped us understand the tool’s functionality and realise what was needed.”
Learning points?
💬 “This was my first ever application running on a cloud platform (AWS, Serverless Framework), so I had the work cut out for me. My colleague’s support with the platform and in understanding its architecture was invaluable. The reporting platform was used relatively infrequently, with reports generated quarterly and the admin tool used only occasionally, so opting for a fully serverless solution (Lambdas and database) was the most cost-effective solution in this case.”
Technologies used?
💬 “The technology stack used included Serverless Framework + AWS (the database was Aurora Serverless and AWS Lambdas with Node.js) + React (user interface) + Microsoft Power BI (reporting).”
The best part?
💬 “The manageable scope of the task, gaining an understanding of the cloud platform and the support from my team members throughout the project. It was refreshing to work in a small team after a long while.
- Kalle, consultant and one of the Rocket’s founders
Experiences of a Rocket Scientist: software for sports watches
The gig?
💬 “I was involved with developing software for sports watches. The job included the development of new features, fixing bugs and writing unit and integration tests. One of my final tasks was to further develop the platform to enable the running of third-party apps on the watch.”
Challenges?
💬 “Watches, just like other embedded environments, typically have limited resources – memory usage, for example. Prior to this, I wasn’t really aware of the importance of power-saving in watches.”
Learning points?
💬 “I learnt event-driven architecture and a bit of HTTP standard and JavaScript, which was somewhat surprising considering it was an embedded system.”
Technologies used?
💬 “C++, Gtest, Robot framework, Python and JS.”
Best part?
💬 “Amazing colleagues and learning new things.”
- Anonymous Rocket Scientist
Want to learn more about the Rocket culture? Click here to read more!
Questions? Get in touch!
Tessi Reispakka
recruiting
+358 45 213 2234
tessi@rakettitiede.com
Karri Kallela
recruiting
+358 50 554 2634
karri@rakettitiede.com