Welcome to Springworks International!

Springworkers

We are a small, happy, ambitious team that share a passion for technology, problem-solving and developing both our platform and each other.

We are always looking for exceptionally talented people that share our passions!

TEAM

Who we are

We are transparent, fast and truly agile.
At Springworks your opinions really matter, you have the freedom to solve and innovate while growing yourself and our product.

When we are not innovating, improving or developing, we love to have a beer or two, go kayaking or celebrate our last achievement!

Let's talk about Tech!

direct deploys to production ~10-15 times a day automatically after PR review and merge
no test/stage environments - why bother, we have a perfectly fine production environment
all infrastructure in code. The only thing we ever do in the AWS console is to roll back if any of the daily deploys has a glitch
microservices (yes, everyone's got'em) - count of the day is 70
one service - one github repo - one database (if needed) so changes to storage is contained to one service
mono-repo with utilities that are used by several services
all services are containerized and scale on individual rules
the architecture is heavily based on pub/sub messaging - events are broadcast and services that are interested subscribe
monitoring - we use tools like newrelic and splunk to monitor our services and alert us via pagerduty and slack when the shit hits the fan
ad hoc queries - all services log in a unified format accessible for querying in splunk
databases - we favor document databases. But we're not a one-trick pony. Whenever there is a better alternative for a specific use case, we'll use it
most of our stuff is in Typescript. We do have Java components and whatever tech makes sense for the next service - go ahead!