Work
Car Washer
[Placeholder employer] · [City, State]
I took this job because I needed to start somewhere and learn what showing up every day actually looks like.
- Work ethic
- Customer service
Shaping who and where I am today.
My Professional Journey
Every major decision I've made has been intentional. This page is not just where I've worked or what I've studied. It's why I chose each step, what it taught me, and how it shaped the way I approach software, systems, and growth.
Career timeline
- Work
Landscaper
[Placeholder employer] · [City, State]
I wanted work that was physical, outdoors, and taught me how to finish a job even when I was tired.
- Teamwork
- Reliability
- Work
Utility Worker / Line Cook
[Placeholder employer] · [City, State]
I needed flexible hours and fast-paced work that forced me to stay organized under pressure.
- Pace
- Systems thinking
- Military
Infantryman
U.S. Army · [Duty station — edit later]
I joined the Army because I wanted discipline, direction, and a hard reset on who I was becoming.
- Discipline
- Leadership
- Pressure
- Education
Software Developer Trainee
Microsoft Software & Systems Academy · [Location — edit later]
I entered MSSA because I needed a serious bridge from military service into software.
- C#
- Cloud
- Team projects
- Leadership
Shift Manager
[Placeholder employer] · [City, State]
I stepped into management because I wanted to learn how to lead people, not just complete tasks.
- Leadership
- Communication
- Freelance
Freelance Software Developer
JustJosh.dev · Remote
I started freelancing because I wanted real client problems, not just classroom exercises.
- Web apps
- Prototypes
- Automation
- Education
Software Engineering Student
Arizona State University · Tempe, AZ
I chose ASU because I wanted a structured path to deepen my engineering fundamentals while still building real projects.
- Software engineering
- Systems design
- Projects
PromptIQ
Personal project · Remote
I started PromptIQ because I kept seeing people struggle to turn vague ideas into useful AI outputs.
- Next.js
- AI
- Full-stack
- Personal
Current Direction
What's next
I'm focused on full-stack development, cloud patterns, automation, and building systems that are practical and secure.
- Full-stack
- Cloud
- Automation
Principles I Keep Coming Back To
A few sayings I've carried since I was around 14 — not as motivational posters, just as reminders when things get hard or unclear.
“Do today what others won't, so tomorrow you can do what others can't.”
— Jerry Rice This reminds me that small improvements compound. Whether it's learning a new technology, improving a workflow, or even figuring out how to fold a burrito one second faster, I try to find small things others overlook and get better at them.
“Life sucks, and then you die.”
On the surface, it sounds dark. To me, it's more about accepting that life is going to throw challenges at you. You can either complain about that forever, or you can roll with it, learn from it, have some fun, and keep getting better.
“Live for the challenge.”
Challenges are where growth happens. Most of the decisions I'm proud of started because they were difficult, uncomfortable, or uncertain.
“If I'm the smartest person in the room, leave.”
I always want to be around people who know more than I do. I want to learn from bigger fish until I become better myself.
Still Building
This journey is still being written. Every class, project, client, and challenge adds another piece to the story. The goal is simple: keep learning, keep building, and leave every system a little better than I found it.