Apprentice wanted: security and SaaS setup, learned by doing it

Illustrated infographic summarizing: Apprentice wanted: security and SaaS setup, learned by doing it

By Greg Nowak. Last updated 2026-10-10.

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.

You get your own account with two-factor, and only access to the system the task is about. Customer sites come after you have run the checklist on my own domains, and I look at anything you change on a customer system before it goes in. Customer data stays where it is. When we stop, I close your accounts.

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.

You can show what you did here afterwards. First we take out customer names, domains, IP addresses and anything an attacker could use, and I read it before it goes anywhere.

Write to me

Use the contact form with the subject [grn-praktik]. The subject is filled in when you come from this link. Send me a link to the most broken thing you got working again, and two lines on what went wrong. I answer myself.

Latest articles

Check whether AI crawlers can reach your service and product content. Compare response HTML with rendered pages, then identify practical CMS and rendering fixes.

Improve site search for customers who use everyday language. See where synonyms, semantic retrieval and behavioural signals help, while keeping product codes reliable.

Follow customer data through n8n, OpenAI and your CRM. Check who can access retained copies, what redaction hides and whether deletion works before scaling.

When checkout fails, your operations provider needs concrete evidence to work with. See how AI, dmesg and journalctl can gather the evidence into a useful incident ticket.

OpenAI’s hosted Evals platform is closing. Preserve your tests, validate replacement scoring and keep releases covered before the October and November 2026 deadlines.

Decide which AI-assisted pages to keep, improve, combine or remove. Check claims, page overlap and metadata, then put clear review controls into your CMS.

Use October to trial daily AI reorder recommendations before Black Friday. Get your Shopify data, lead times and budget in order before turning recommendations into purchases.

When an OpenAI request stalls, customers need an accurate status. Set sensible retry limits, preserve submissions, and make unresolved work visible.

I learned server operations by breaking my own servers. I want someone who stands next to me while I do it, then does it themselves the week after.

I am good at building and bad at calling. Here is who I want next to me, what is easiest to sell, and how we split it.