ID 81998

Senior Fullstack Developer

PHP
Git
HTML
JavaScript
CSS
Developer
PSQL
Atlassian Jira
REST
GitHub
CRUD
Slack
Node.js
GraphQL
React
Docker
SCSS
API
Validation
Java Programming
Java Spring Boot
Database design
NoSQL
AWS
Golang
Lead Developer
Clojure
TypeScript
Figma
MongoDB
Google Cloud Plattform
Grafana
TensorFlow
SaaS
MVC Architecture
ExpressJS
Firebase
Mentoring
GCP
Firestore
Groovy
Location
Pohjois-Pohjanmaa
Available
7.2.2023
Fee
Negotiable
Experience
9 years
Languages
suomi, englanti
Set as favorite
You’re glancing a profile of an innovative backend developer, who arrives with a pinch of frontend as well. I’ve had experience in various positions in different team sizes, and I’ve acted in different parts of the team, while usually focusing on the backend and/or database side. I’ve gathered experience as a leading developer in one project. While innovation comes within my personality, I know what’s right for business value and can prioritise tasks to deliver a product of best quality.
Request further information about experts

Projects completed

Product Developer (Backend)

9/2021-
Java
Groovy
Spring Boot
JIRA
I was hired to strengthen a team, which was dedicated to focus on a specific segment of a mobile software. My tasks were focused to the backend side, and my day to day job consisted of building new interfaces as well as maintaining old ones – with a pinch of testing as well.

Software Developer

2/2020-7/2021
Git
REST
Amazon Web Services
Clojure
Node.js
GitHub
Docker
SCSS
TypeScript
CRUD
API
Validation
Slack
Figma
React.js
Developing various tasks in different projects targeting to the public sector. The smallest project was done only by myself, where I focused on developing a proof-of-concept of a naval traffic forecasting platform. The platform could predict an approximate arrival time for cargo vessels and could then alert the pilots in time, so they could navigate the vessels though the fairways. Another project which was thrilling to build was implemented with Typescript, Docker, Postgres, SCSS, AWS and React. In this particular project, I had to recreate a web application using the guidances of an existing one, but migrate the frontend from an abandoned frontend framework to React, convert the database to relational one and build a completely new backend layer. As I had the option to choose the stack, I went with the ones I felt the most confident and with which I’d like to improve as a developer even further. The web-application itself had only few pages, but the complexity came when there was no proper place for multiple components to share code. The design and the data patterns were custom to each sub-relation, allowing only marginal sections to be shared. Due to this, sharing a proper properties through BEM styling classes came handy. Backend layer acted as an API endpoint which had a middleware validation for every endpoint. For example, PATCH requests were designed to modify an existing relation, where POST created a new one. The whole backend also had an authentication middleware check for every request to verify the users permissions. Both backend and frontend were built in separate docker containers, which were then pushed to AWS ECR using Github Actions. This way, every successful push (or merge) to the project now and later will update the production environment automatically, reducing the work load of the developers. Some statistics: Initial loading time was 133x faster than the first version. Filtering the results takes 30-50ms on average, when the customer previously had to use an environment with 4s+ response times.

Project Owner / Dev Mentor

1/2021-4/2021
HTML
CSS
Node.js
ExpressJS
GitHub
Firebase
Mentoring
React.js
GCP
Firestore
I introduced few React assignments for the university of applied sciences of Oulu. Two study groups took these assignments and I acted as project owner but had strong connection with the study groups, since my earlier expertise with developing could come beneficial with these projects. Both of these projects used GitHub, and every commit was peer reviewed by myself. One study group had an assignment to implement a application for The REKO retail and distribution model. Producer-level users had the ability to reserve a parking spot from an upcoming REKO event, so they could come and sell their goods during that event. Customer-level users (default) could interact with the same application, but could not reserve any parking spots. Their only action was to view the data of upcoming REKO-events and view producer info of specific parking spots. Another study group had an assignment to build an web-app, where restaurant keepers could registister and/or login. Once logged in, they could update their upcoming lunch data using a simple UI, add allergen information of the specific dishes, add lunch times and pricing information. This data would be then uploaded to Lounaskartta.fi, making the crawler-based data usage obsolete in some cases. Both of these applications used google firebase for authentication purposes and firestore for data storage.

Full-stack Developer

9/2020-2/2021
CSS
MongoDB
Node.js
GitHub
Google Cloud Plattform
React.js
I was travelling with my wife who is vegan. As she was driving, I was going through the lunch menus of the next possible stops using my mobile phone and tried to find something for both of us. And from there, the idea of Lounaskartta came into my mind – a simple web app, where one could easily search lunches suitable for their diets. The data itself is crawled using nodejs web crawler. The contents of each individual restaurant web page are parsed using dedicated parser, which then looks for lunch list information in predefined spots. Once the data is parsed, it’s formatted to json and stored to MongoDB. Frontend uses React, which is a simple layout of map and list of data. Upon initial load, the application fetches a lite-data of all markers, containing only latitude and longitude of all markers using a GCP serverless function, which then connects to mongo. Once that data has been received, markers are then drawn into the map. Every time the user moves the map, a 3x3 area of latitude and longitude is calculated, positioning the visible area of the current in the middle. The app checks all markers within that 3x3 area and continues to load the lunch data for all markers within that area. This is done using an another serverless function, which takes in an array of identifiers, and then returns the proper lunch data back. For optimisation purposes, I could study server-side rendering for this project, since the layout is quite static. Also, because the amount of restaurants is static (for now), The marker data could be stored in the GCP json file instead of mongo, ditching the initial marker, thus making the service work a tad faster. Also, building a mobile app for this using React Native or Flutter is something I have already planned with Figma.

Lead Backend Developer

2/2019-10/2019
Git
Node.js
Go
JIRA
Lead Developer
GraphQL
PSQL
React.js
Acted as a leading developer in different SaaS product. Designed product changes with the client, instructed developers with the agreed changes and handled bidirectional connection between the developers and the client. I mainly focused in developing the new backend version using completely different stack, but used and improved the frontend side as well, which was built using React framework alongside with the backend. The product contained some task runners implemented using NodeJS, which handled pdf and image generations and modifications. Some web crawlers were implemented using the nodejs as well.

Backend Developer

12/2014-2/2019
HTML
JavaScript
PHP
CSS
SaaS
Git
MVC
Developer
PSQL
Acted as a part of a small team who was maintaining and developing one of the SaaS product. Common day-to-day activity contained some client troubleshooting, guiding customers with their problems and checking / fixing any found issues along the way. Product improvement was done continuously as well.

PHP Programmer

9/2013-12/2014
PHP
Git
Amazon Web Services
Developing a backend server for game client. Server acted as a gateway to AWS environment, from where the data was transferred back to authenticated clients.
Request further information about experts
Return to search results
New search