I’m an experienced junior developer who ships practical software, communicates clearly, and learns quickly. I enjoy joining strong teams, owning real work, and improving a little every project.
I care about steady execution more than flashy claims. My focus is writing maintainable code, asking good questions, and creating momentum for the team.
I spent nearly four years in the United States Marine Corps as a Network Administrator, supporting mission-critical environments where reliability and accountability were non-negotiable.
After the Corps, I worked in technical support, then transitioned into software. That path gave me a practical mindset: solve the real issue, communicate clearly, and leave systems better than I found them.
"I bring discipline and consistency now, and I’m hungry to learn from stronger engineers every day."
Today I build SaaS tools and internal products with TypeScript, React, Node.js, and Cloudflare services. I’m aiming for a role where I can contribute immediately while accelerating into a stronger mid-level engineer.
Experience highlights:
• USMC Network Administrator (2018–2022): operations, maintenance, and team leadership.
• Technical Support (~3 years): high-volume issue resolution and process improvements.
• Software Developer (present): building production features, automation, and SaaS products.
What I’m optimizing for: mentorship, strong engineering culture, and opportunities to own challenging work end to end.
Designed around a thin API layer and deterministic setup flows so support staff could handle onboarding without deep infrastructure knowledge. This reduced handoff friction between engineering and ops.
Introduced explicit state transitions and idempotent operations so retries were safe. This made the tool dependable under real-world failures like partial API timeouts.
Iterated prompts around real user language, then tuned output structure for actionability over creativity. The key was reducing cognitive load, not generating long plans.
Split ingestion, normalization, and presentation to keep failures isolated. This made it easier to add or remove sources without destabilizing the full feed.
Focused on practical offline/error handling and simple deployment mechanics so non-engineers could keep using the tool during connectivity issues.