Professional summary
I work at the intersection of infrastructure, automation, support, endpoint management, identity, backups, monitoring, and security. My focus is turning operational knowledge into systems that are easier to understand, audit, recover, and maintain.
I do not treat scripts, dashboards, policies, and services as isolated deliverables. I document the constraints, decisions, safeguards, failure modes, and tradeoffs behind them so the result can be operated safely over time.
Career
Professional journey
Current role
IT Infrastructure & Security Analyst
I operate across infrastructure, user support, servers, identity, endpoints, backups, monitoring, automation, and technical governance in an industrial environment. The role requires balancing immediate operational needs with security, maintainability, and recovery.
Professional evolution
From generalist operations to security engineering
My work started with broad IT operations and progressively moved toward repeatable automation, endpoint control, hybrid identity, auditability, and security-by-design. That progression gives me a practical view of how security decisions affect real users and production systems.
Current direction
Building toward cybersecurity specialization
I am developing deeper expertise in defensive security, identity, endpoint security, infrastructure hardening, incident readiness, and secure automation while continuing to strengthen the operational foundation those disciplines depend on.
Hands-on scope
Responsibilities and experience
- Administer Windows Server, Active Directory, Group Policy, hybrid Microsoft identity, endpoint enrollment, and access controls.
- Design PowerShell, Python, PHP, and JavaScript automation for recurring operational tasks, reporting, internal services, and lifecycle management.
- Operate backup, recovery, monitoring, logging, remote access, file services, databases, and virtualization workflows with an emphasis on recoverability.
- Provide user support and incident resolution while turning recurring problems into documented processes or automated controls.
- Evaluate technical risk, permissions, failure modes, rollback paths, and maintenance requirements before introducing changes.
- Document architecture, decisions, safeguards, deployment procedures, and operational ownership so systems remain understandable beyond their implementation.
Learning
Education and continuous development
Systems Analysis and Development
My formal education strengthens software development, data structures, databases, systems analysis, and engineering fundamentals. I complement it with hands-on study in cybersecurity, Microsoft infrastructure, Linux, networking, automation, and resilient operations.
Engineering
Engineering principles
Automate with safe defaults
Automation should reduce risk, not merely reduce clicks. I prefer report-only modes, explicit validation, bounded permissions, logs, and reversible actions.
Design for recovery
A system is not reliable because it usually works. It is reliable when failures are observable, recovery is tested, and ownership is clear.
Document decisions
Implementation details matter, but the constraints, tradeoffs, and reasons behind a decision are what make a system maintainable.
Security must fit operations
Controls need to be technically sound and operationally sustainable. Security that cannot be maintained will eventually be bypassed or abandoned.
Direction
Professional objectives
- Deepen expertise in cybersecurity engineering, identity security, endpoint defense, and infrastructure hardening.
- Continue publishing practical projects and technical writing that demonstrate implementation quality, not only conceptual knowledge.
- Develop toward independent security consulting while retaining a strong foundation in infrastructure and operations.
Availability
Open to professional conversations
I am available for technical collaboration, discussions about public projects, infrastructure and security engineering exchanges, and selected consulting conversations.