Cybersecurity Engineering Student / Blue-Team Bias / 2026
I build and study systems that make more sense under inspection than they do at first glance.
- Current lens: blue-team / SOC-side thinking
- Certifications: AWS SAA / eJPT / RHCSA
- Ground: cloud labs, Linux, packet inspection, web security
Method / Internal Logic
Manifesto
I trust traces, flow, and failure modes more than polished surfaces.
That shows up in the work I keep returning to: cloud lab isolation, vulnerability tracking, packet inspection, and scan pipelines. I like systems that reveal their assumptions once you watch the sequence closely enough.
Observation before assumption.
Present Coordinates / Recruiter Signal
Current State
I’m a cybersecurity engineering student with a current bias toward blue-team work, analyst context, and operational clarity.
Current focus
Blue-team / SOC thinking
Signal triage, analyst context, visibility, response
Operating ground
Cloud, Linux, and web
AWS labs, service behavior, permissions, automation
Working bias
Study before certainty
Defaults, sequence, failure paths, evidence
I do not want to flatten myself into one label too early. I move between cloud, Linux, web security, telemetry, and packet analysis, then keep the parts that improve how I investigate and defend systems.
What I’m looking for is straightforward: environments where careful reading, technical curiosity, and disciplined execution are useful, not ornamental.
Certifications
Certifications matter to me as proof of discipline, not as a substitute for building and investigating real systems.
Selected Work / Systems Built And Studied
The Work
Orchestryx
Secure cloud lab orchestration for CTF events, training programs, and cyber ranges.
Built around reproducible AWS environments that can be provisioned on demand without treating isolation as an afterthought.
OBSEC
Privacy-first ecosystem for peer-to-peer communication and anonymous value exchange.
Designed around the premise that privacy should live in the architecture itself, not in optional settings layered over it.
Observation Log / Fragments
Notes
A1
Packet traces change everything once you stop reading protocols in isolation and start reading sequence.
A2
A scanner is only useful if enumeration is disciplined before exploitation begins.
A3
Cloud automation stops being impressive the moment isolation becomes optional.
A4
A vulnerability list without remediation context is just backlog theatre.
A5
Linux keeps me honest because it exposes bad assumptions faster than polished tooling does.
Contact / Direct Channel
For security engineering, blue-team, or systems work, reach out directly.
I’m interested in early-career roles where investigation, operational context, and careful execution matter more than buzzwords.