25.06.2025 aktualisiert
CS
100 % verfügbar
Software Developer, Team Lead
Wien, Österreich
Skills
LLMs, Langchain4j, claude code, ollama
TDD, Kotlin, JVM, Ruby, Javascript, Ansible, Team Lead, Continuous Integration, gitops, Kubernetes, Flux
TDD, Kotlin, JVM, Ruby, Javascript, Ansible, Team Lead, Continuous Integration, gitops, Kubernetes, Flux
Sprachen
DeutschMutterspracheEnglischgut
Projekthistorie
Kotlin on the backend, Vue.js on the frontend, non-blocking web server, TDD,
Continuous Integration, automated deployment to AWS for both frontend and
backend. I was the Development Lead of the whole project and contributed
mostly to the Kotlin backend.
Continuous Integration, automated deployment to AWS for both frontend and
backend. I was the Development Lead of the whole project and contributed
mostly to the Kotlin backend.
The main purpose of the app was to collect data from the client's browser to
detect fraud. Lightweight, non-blocking Kotlin Webserver with Undertow as
HTTP frontend, Continuous Integration, automated deployment to Google
Cloud. Very high throughput and low latency with automated benchmarks also
running on Google Cloud.
detect fraud. Lightweight, non-blocking Kotlin Webserver with Undertow as
HTTP frontend, Continuous Integration, automated deployment to Google
Cloud. Very high throughput and low latency with automated benchmarks also
running on Google Cloud.
On my first day at Collective, I started to rewrite the tag server in Ruby, fully testdriven.
Later I rewrote it again in non-blocking Ruby, and finally in Node.js. After
that led the team that created Collective's real-time bidder. That was my return
to the JVM and Java. I think I managed to create a Java project that did not
suck, and people seemed to like working on my team. At Collective I refined my
workflow for rapid iteration, short feedback loops, and continuous delivery. Also
I've learned that it's necessary to automate every step.
Before that, I was working at various Austrian IT companies since 1991
Later I rewrote it again in non-blocking Ruby, and finally in Node.js. After
that led the team that created Collective's real-time bidder. That was my return
to the JVM and Java. I think I managed to create a Java project that did not
suck, and people seemed to like working on my team. At Collective I refined my
workflow for rapid iteration, short feedback loops, and continuous delivery. Also
I've learned that it's necessary to automate every step.
Before that, I was working at various Austrian IT companies since 1991