By Greg Nowak. Last updated 2026-10-03.
I learned server operations by breaking my own servers and fixing them again. It is still the way I believe in most. So I am not looking for an intern to sit with PowerPoint. I am looking for someone who will stand next to me while I do it, then do it themselves the week after.
What you will get your hands on
I run a server fleet with around 50 domains behind Cloudflare, Drupal and Laravel sites, a password manager, mail routing, backups and a handful of AI agents working for customers. All of it is under attack around the clock. Most of it bounces off because someone set it up properly. That someone can be you.
Week one: you get access, and we check one of my own domains together. Headers, TLS, versions, logins, backups. Week two you do it alone on the next domain, and I read your report. Then come the customers' sites. Later you set up tools for a customer: a Trello board, Google Workspace or Microsoft 365, two-factor access, a password manager. And one day a real problem lands in the middle of it all, and you watch how it gets solved.
What I expect
That you can find your way around a terminal. That you know what DNS does, or will find out the same day. That you write down what you did, briefly enough that I will read it. And that you say it out loud when you have made a mistake. Mistakes are expected. Hidden mistakes are the only thing that is not okay.
You do not need certifications. I would rather see a server you set up or a script you wrote than a course certificate.
The terms
We start with one day a week and can go up to two. Remote, with a fixed weekly call. It can be a paid student job, or it can be an internship through your studies if your programme requires one. We decide that together once we have talked. Three months to begin with, then we see.
Write to me
Send a mail to [email protected] with the subject [grn-praktik]. Send me a link to the most broken thing you got working again, and two lines on what went wrong. I answer myself.
