Independent engineering & R&D

I still build, operate and learn.

A working personal platform for software engineering, cloud-native infrastructure and AI-assisted development research. Separate from all professional client environments.

~100Personal application and service repositories
6Kubernetes nodes in my private lab
1Dedicated AI-agent virtual machine
01

Applications and source control

A self-hosted GitLab environment containing around one hundred personal service and application projects, including Java/Spring Boot microservices, Node.js backends and React/Vite interfaces. I use the platform to develop, version, integrate and evolve working software.

GitLabJava / Spring BootNode.jsReact / Vite
02

Cloud-to-private Kubernetes platform

A self-operated, production-running personal platform connects public-cloud entry points with a private six-node Kubernetes environment. I manage container deployment, ingress and reverse-proxy routing, private connectivity and the operational dependencies required to run live applications.

AWSOracle CloudPrivate connectivityKubernetesDocker
03

Observability and reliability

Hands-on experimentation with monitoring, alerting and centralised logging for containerised services. The environment supports realistic investigation of application, network and platform behaviour rather than isolated demonstrations.

PrometheusGrafanaLokiAlertmanagerLinux
04

AI-assisted engineering research

A dedicated virtual machine for repository-aware AI-agent experimentation, development workflows and code-generation proof-of-concepts. I assess how these approaches could support engineering tasks such as implementation guidance, test generation and code review, without presenting experiments as deployed client solutions.

AI agentsGitLab integrationDeveloper workflowsProof of concept

Why I build independently

Experiment privately. Apply judgement professionally.

Independent projects sharpen my technical understanding; enterprise adoption still requires the right governance, risk assessment and stakeholder agreement.

01

Compare technology decisions against practical experience from operating an end-to-end platform.

02

Bring informed questions and actionable options to developers, DevOps engineers and live-service specialists.

03

Prototype approaches independently before considering whether they suit an enterprise delivery environment.

All examples on this page refer to personal infrastructure and proof-of-concept work. No client infrastructure details, source code or private endpoints are published here.

Contact

Let’s discuss the next complex problem worth solving.

I am interested in senior Java engineering, technical architecture and engineering leadership opportunities where sound design must translate into reliable software.

hello@arunrajapandy.com
Newcastle upon Tyne, United Kingdom