Andreas Wagner

Ruby on Rails Developer

I take over Rails applications whose original developers are no longer available. I keep them stable in production and make changes low-risk again.

  • 9 years freelance Rails development, since 2017
  • 13 years running production systems, from fintech to museums
  • 4 Rails applications under management

Profile

Ruby on Rails developer with nine years of practice. Strong experience in system administration. I work on existing applications and create new ones. I prefer plain, conventional Rails to clever code, because convention over configuration applies to style as well. As I run the servers myself, I know what a change means in production: deploys, background jobs, backups. I work remotely from Tallinn, directly with decision-makers and business teams.

Project experience

Takeover and modernisation of the competition platform Defolio.com

2017 - today

Freelance via Whyservices OÜ · Tallinn, remote

Industry: marketing · Role: Rails developer & maintainer · Team: solo, with the client's product owner

The application was in production, but database queries got slower with every competition. Framework upgrades had been applied, but syntax and code style drifted further and further apart. There were no functional tests, and the framework was tightly entangled with the operating system. I started with an in-depth review: reading the code and the infrastructure, then a written report with the risks ranked by severity. Before changing anything, I covered the business-critical paths with tests. I then completed the Ruby and Rails upgrades, replacing deprecated and broken syntax, and swapped custom workarounds for Rails conventions along the way. Deploys now run through a CI pipeline with staging and rollback, and backups have a restore procedure that has actually been rehearsed. The application is back on a supported version (Rails 7 → 8.1), and I resolved almost all N+1 queries. Deploys take 4 minutes from git instead of 30 minutes by hand. The client kept its application instead of paying for a rewrite estimated at €45,000.

  • Ruby on Rails
  • PostgreSQL
  • Sidekiq
  • Redis
  • GitHub Actions
  • Docker
Andreas Wagner · Ruby on Rails Developer contact@andreaswagner.io · +372 5870 8341

Project experience (continued)

Back-office application for a hosting business

2015 - today

Whyservices OÜ, own product (WellPress / WellHost)

Industry: Hosting & IT services · Role: product owner & sole developer · Team: solo

Running managed hosting for many small clients meant invoicing, client communication, status updates and each site's hosting history were spread across separate tools. Every new client added manual work and the risk of a missed invoice or an unannounced maintenance window. I designed and built a Rails back-office application that brings these together: invoicing, client communication, public status pages and a per-site hosting history. It calls the hosting providers' APIs and manages the administration runbooks. I kept it plain Rails, so that maintaining it stays cheap for a one-person business. One person runs 30 client sites and applications. Setting up a new project takes 30 minutes instead of 8 hours, and invoicing and status communication are automated.

  • Ruby on Rails
  • Ruby
  • Ansible
  • REST APIs
  • e-invoicing

Greenfield Rails application with business stakeholders

2025 - 2026

MTÜ Ruumiharidus · via Whyservices OÜ

Industry: Education · Role: Rails developer, from discovery to operation · Team: solo, with two stakeholders on the business side

The non-profit ran its core process by hand in spreadsheets and email, with a WordPress plugin managing students, groups and timetables. Double entries and errors cost the team 16 hours a week, and nobody had a reliable overview of what the software could do. I worked out the requirements directly with the stakeholders: short sessions, written specifications and small releases they could try out early. I built the application as a conventional Rails monolith. I also set up hosting, CI and monitoring, so the client had one contact from the first conversation to operation. Live after 12 weeks, with 2 people using it daily. Manual work dropped by two thirds.

  • Ruby on Rails
  • PostgreSQL
  • Sidekiq
  • CI/CD

Head of System Operations

2013 - 2017

Cash on Go Ltd · Tallinn

Industry: fintech, regulated (PCI DSS, FCA) · Role: head of system operations · Team: 3 system administrators

The company's main application and database ran on hand-administered servers in the data centre and in the office. A hardware fault would have stopped the business, and audits required documented, repeatable processes. I led the system administration team and agreed release and deployment policies with the development team. We moved from manual shell work to infrastructure as code, first with Chef (Ruby), later with Ansible. Together with the developers, we migrated the PHP/Symfony application and its MySQL database to a redundant, multi-location setup on AWS. The single point of failure was removed and releases followed a documented lifecycle. As primary lead for PCI DSS procedures, I took the company through 3 audits without major findings. Received the company's 2014 Einstein Award for work across departments.

  • Chef
  • Ansible
  • AWS
  • MySQL
  • PHP/Symfony

Earlier positions

  • 2016 - 2024Exhibition IT for Estonian museums and EU2017 (via Whyservices OÜ): Windows terminals managed with Ansible, deploy pipelines for up to 50 devices per exhibition.
  • 2008 - 2012Owner, Whyservices, Berlin: web development, hosting, web design and remote administration for small clients.
  • 2009 - 2010Student assistant in IT administration, Humboldt University Berlin: users, network and Active Directory.