About
Hans Spiller
More than a decade in corporate environments
Hans Spiller brings together skills that usually sit in separate IT teams: infrastructure, security, data, automation, governance and applied AI. Rather than looking only at the tool, the work covers the whole process: data source, business rule, infrastructure, security, user, automation, evidence and ongoing support.
This profile makes a difference when the cause of a problem is not in a single system. Many projects cut across technology, operations, HR, databases, spreadsheets, networks and integrations: understanding the operation, investigating the problem, organizing the data, building the solution, adjusting access, validating the result and documenting the new process.
The approach is practical and evidence-driven: find the real bottleneck, reduce manual work, protect the critical points and leave a clear trail. In critical environments, changes are small and reversible, and human validation stays wherever the risk calls for it.
Stack
Technologies and skills by area
- Data and BI
- Advanced Excel
- Power Query
- Power BI and DAX
- Python, pandas and openpyxl
- SQL
- KPI modeling
- Automation
- Python
- PowerShell
- VBA
- RPA and Selenium
- Scheduled jobs
- Email and file automation
- AI and knowledge
- LLMs and agents
- OCR
- RAG and embeddings
- Semantic search
- Classification and summarization
- Local models
- Infrastructure
- Windows Server
- Linux and systemd
- Active Directory and GPO
- DNS, VPN and SSH
- Backups
- Monitoring
- Security
- Hardening
- Firewall and web filtering
- DLP and encryption
- Endpoint
- Access reviews
- Logs and governance
- Networks
- Switches and patch panels
- Segmentation and VLANs
- MAC-based access control
- Connectivity diagnosis
- Development and version control
- Git and GitHub
- Branches and pull requests
- Test environment
- GitHub Pages and DNS
- Technical web
- Technical SEO
- Semantic HTML
- Accessibility
- robots.txt, sitemap and Search Console
- Documentation and QA
- Procedures and manuals
- Audit reports
- Action plans
- Checklists and evidence
- Change control
Way of working
Eight principles in every project
From assessment to solution design, implementation, validation, documentation and ongoing support.
The real process first
Understand the process as it actually happens before automating or changing any technology.
Evidence before conclusions
Separate symptom, likely cause and evidence, so decisions do not rest on perception alone.
Risks mapped
Map dependencies and risks before any change.
Small, reversible change
Prefer small changes, with a backup and a way back, in critical environments.
Human validation where it matters
Automate what is repetitive and keep human validation wherever the risk calls for it.
Objective success criteria
Define metrics and criteria to confirm, with data, whether the solution worked.
Documentation to carry on
Document so that someone else can operate, audit or continue the work.
Incidents become improvements
Turn incidents and one-off tasks into permanent improvements whenever possible.
Confidentiality
How your work is handled
Confidentiality as a method, not a clause. The projects on this site follow the same rule applied to every client engagement.
No client names
Not in the portfolio, in published projects, in conversations with third parties or in file metadata.
Examples are always fictitious
Anything shown in public uses synthetic data. Real screenshots never leave the project.
What is yours stays with you
Code, files and credentials stay in your environment and are never reused for another client.
Agreement before access
A non-disclosure agreement can be signed before any access to data.
Contact
Want to talk about a specific process?
The first conversation is about understanding the problem. If it makes sense, the next step is a fixed-scope assessment.