Jaival SaijaDevOps Engineer · AI Automation
About MeProjectsExperienceCVBlogContact Me
  • Email
  • LinkedIn
  • GitHub
  • CV
© 2026.
Jaival Saija.
All Rights Reserved.

About Me

I'm a DevOps engineer. I like deployments that are boring, and servers that stay up without anyone watching them. Right now I'm in Kaiserslautern, doing my Master's in Computer Science at RPTU ✈️

Contact

Whatever it's about, send me an email and I'll get back to you. I swear.

Job Opportunities

I'm looking for a working student or junior role in DevOps, cloud or AI automation, anywhere in Germany.

  • Hours: 20 h/week, 40 in semester breaks
  • Start: As soon as possible
  • Graduation: M.Sc. expected autumn 2027
  • Permit: §16b student permit, working student OK
  • Languages: English C1, German A1

If you think I fit, my CV has the details.

Social Links

LinkedInGitHubTwitterInstagram

Tech Stack

Cloud
AWS (EC2, S3, IAM, VPC, CloudWatch), Google Cloud, Firebase
CI/CD and DevOps
GitHub Actions, Docker, Git, Linux administration, Terraform (basics)
Security
IAM least privilege, VPC network segmentation, OIDC trusted publishing
Code
Python, Bash, TypeScript, JavaScript, Flutter (Dart)
AI
Claude, Claude Code, MCP
Data
PostgreSQL, MySQL, Firestore

Learning Kubernetes, Helm, Prometheus, Grafana, in my Kubernetes lab.

I got into computers at 15, mostly because of games. For a while the plan was to become a game developer. That didn't happen, but the interest stayed, and I ended up in a bachelor's program at Ganpat University that specialized in cloud-based applications.

Cloud is the part that held me. I wanted to know how it worked underneath and what actually happens when something goes down. I finished with a CGPA of 8.67, in the top 10% of my class, and by the final year I was the one on my project team handling the infrastructure, the CI/CD, and the database choice.

My first job was at Maven Infosoft, running AWS for a .NET CMS product across dev, stage and production. I was usually the only infrastructure person there, so alerts came to me first. About 50 incidents in my first six months, most of them solved by reading logs and untangling networking. After the bad ones we sat down with the developers and worked out the root cause, so the same bug would not come back a month later.

I also wrote the deployment runbooks, which hadn't existed before. Onboarding a new developer got roughly 30% faster after that, and cleaning up the update SOPs cut about 20% off our maintenance time.

Now I'm at RPTU in Kaiserslautern for my Master's, on distributed systems and network security. Next to it I build small apps with CI on every change, and most of what I build now involves AI tools: jobhunt-agent runs my job search every day, inside guardrails I wrote. I've also started a Kubernetes course on a local kind cluster, which is where Helm, Prometheus and Argo CD come in.