Save as PDF

CV · 2026

Nikita Moritz

Backend developer

Java and Spring Boot · DevOps and AI-assisted development

IHK-certified application developer (Fachinformatiker für Anwendungsentwicklung), three years of Java backend work inside the training company of a software house: REST APIs with Spring Boot, data modelling with JPA/Hibernate, versioned migrations with Flyway, PostgreSQL and MySQL, integration tests.

Nikita Moritz

Location

Aachen, Germany

Telegram

Languages

German (B2, certified) · English (technical reading fluent, spoken A2) · Russian (native) · Ukrainian (native)
01

Profile

Since May 2026 I have run my applications on a Linux server of my own. So I do not only write the service, I also see how it fails in operation and build it accordingly: from the data model through to deployment, monitoring and backups.

Development is AI-assisted. Architecture, review, security and operations stay with me.

02

Work experience

May 2026 to present · Remote

Developer and operator of my own products

nikone.dev

  • Four own web products in operation: data model, REST API, authentication and tenant separation, deployment and monitoring
  • Backend architecture along ports and adapters, domain logic independent of framework and database
  • PostgreSQL: schema design, indexes, execution plans, versioned migrations, separate demo and production databases
  • Operations on my own Linux server: reverse proxy, TLS, systemd, daily backups, alerting
  • wildro.app: rebuilding the backend as a Spring Boot service (Java 21, Maven, Flyway, Testcontainers), in progress

July 2025 to Apr 2026, 10 months · Aachen

Further training and job search

  • Worked into frontend and a second language stack: TypeScript, React and Next.js
  • Built up AI-assisted development as a daily tool
  • First own practice project in April 2026, which grew into wildro.app

May 2022 to June 2025, 3 years 2 months · Aachen

Internship and apprenticeship as an application developer

Gypsilon Software GmbH

  • Development and maintenance of performant REST APIs with Java and Spring Boot, documented with OpenAPI/Swagger
  • Final project: appointment management module for the property software K-ZWO. Designed the entities and the data model, recurring appointments with calendar logic, validation and conflict checks
  • Invoice workflow: finding and fixing defects in a process already in production, plus implementing and maintaining the application's translations
  • Connecting relational databases (PostgreSQL, MySQL), JPA/Hibernate and Flyway for data modelling and migrations
  • Integration and API tests, code quality with SonarQube, feature branches and merge requests in GitLab, working with the frontend teams

Oct 2019 to Apr 2022, 2 years 7 months · Aachen

Further training and self-development

  • German to level B2 with certificate, volunteer support in the local community

June 2013 to Oct 2019, 6 years 5 months · Dnipro, Ukraine

System administrator

Ruflex

  • Administration and monitoring of Linux and Windows server environments, setting up network and system components
  • Ensuring system availability, data safety and backup strategies
03

Own projects

  • soultrek.live · Live, Ongoing developmentNext.js, TypeScript, Prisma, PostgreSQL, next-intl
  • wildro.app · In developmentJava 21, Spring Boot, PostgreSQL, Testcontainers
  • pdef.online · Live, Ongoing developmentNext.js, TypeScript, pdf-lib, PostgreSQL
  • nikone.dev · LiveNext.js, analytics
04

Skills

Backend (focus): Java 17 and 21 · Spring Boot · Spring Security · Spring Data JPA · Hibernate · REST · OpenAPI/Swagger · Flyway · Exception handling · Validation · Maven · Gradle · JUnit · Mockito

Databases: PostgreSQL · MySQL · SQL · JPA/Hibernate · Prisma

Further languages and runtimes: TypeScript · JavaScript · Node.js · Bun, in use in my own projects and still deepening

Frontend and client architecture: HTML · CSS · Vaadin · Next.js 16 · Server Components · Tailwind CSS · shadcn/ui

Tools and ways of working: Git · GitLab · GitHub · Docker · SonarQube · Postman · Confluence · IntelliJ IDEA · VS Code · Linux · Scrum

DevOps and system administration: systemd · Caddy · ACME and TLS · GitHub Actions · CI/CD · Backups · Monitoring and alerting · Server administration on Linux and Windows · Network infrastructure

Cloud and hosting: Hetzner Cloud · Vercel · Neon (managed PostgreSQL) · Docker · GitHub Actions

Security: OWASP Top 10 · Authentication and authorisation · Rate limiting · Security headers · Secret management through a vault

AI-assisted development: Claude (API and CLI) · Claude Code · GitHub Copilot

Architecture: Microservices · Vertical Slice Architecture · Hexagonal (ports and adapters) · Multi-tenant SaaS · SSR and CSR trade-offs · Validation at the boundaries · Clean code and SOLID

05

Infrastructure and operations · Security

Runs on my server (Hetzner, Ubuntu 24.04) and serves live websites:

Reverse proxy, TLS and perimeter: Caddy as the only ingress, Let's Encrypt certificates over ACME with automatic renewal, applications listening on loopback only

Processes: Applications under systemd, unit files and drop-in overrides, a timer that restarts failed services and alerts over Telegram

Databases and backups: PostgreSQL in Docker, indexes and execution plans, connection pools, migrations, demo and production kept apart, daily pg_dump on a timer with off-box copies

Enforced in my own projects:

Authentication and tenant separation: one-time codes from crypto.randomInt, a new code voids every previous one, auth and tenant checked on every route

Rate limiting: limits per IP and per account, counters in PostgreSQL so budgets survive a restart

Headers: CSP, HSTS, X-Frame-Options, Referrer-Policy, Permissions-Policy on every route

Passwords and secrets: Argon2id, secrets only in the vault, never in code

06

Education

BWV Aachen

Fachinformatiker für Anwendungsentwicklung (IHK), training company Gypsilon Software GmbH, July 2022 to June 2025

National Metallurgical Academy of Ukraine

Master and Bachelor of Science, automation of technological processes, Sept 2008 to July 2013

Strengths: Independent: my own products run under my responsibility · Thorough: security, backups and monitoring from the start · Team player: three years in an agile team at Gypsilon

Work alongside employment: My own projects run outside core working hours, with no competition to an employer.

Last updated: 2026-09-21