Over the past few years I have been building with Python and deploying systems. This work spans web applications, APIs, and cloud infrastructure, with a strong focus on the Google Cloud Platform.

Yes, I hold both the Associate Cloud Engineer and Professional Cloud Architect certifications. They are feathers in the cap, certainly, but more importantly the projects and software I work on reflects hands-on experience building and deploying systems that impact reality.

I have been actively contributing to open source, particularly the BeeWare project, among others. Along the way I have found myself increasingly drawn to architecture: designing systems, automating infrastructure, and thinking about how software behaves in the real world. I am interested in a role where that kind of work is the core of the job.

Why I am looking

Working at the Scripps Research Institute has been a positive experience. That said, I am not being challenged in a way that fully exercises my strengths. The challenges I face are real, but they are a different kind of work than what motivates me most.

I am looking to sink my teeth into architectural and software-focused problems. I want the space to think and design, while still building and contributing quickly. Working on open source projects has shown me how effective a team can be when building something meaningful, both synchronously and asynchronously.

What I am looking to do

The kinds of problems I enjoy

How I like to work

Ownership and accountability
I take ownership of the problems I am given and prioritize my work accordingly. I am comfortable being accountable for outcomes, not just tasks, and I take responsibility for moving work forward without needing constant oversight.

Long-term systems over throwaway work
I prefer to zoom out and understand the bigger picture before making technical decisions. Taking time to learn an organization’s goals helps inform the technologies used and how systems should evolve over the long term. One-off projects are sometimes necessary and useful for short-term objectives, but I like to ground those efforts in a broader understanding of where the system is headed.

Documentation and knowledge sharing
When I design architecture or commit code, I document changes thoroughly. I care deeply about leaving systems in a state where someone else can understand, maintain, and extend them. When I pick up an unfamiliar project, I value clear documentation, and I write with that same expectation in mind for others.

Collaboration style
I work well in both synchronous and asynchronous environments. I do my best work when given space for focused, deep work, paired with clear checkpoints and milestones. This balance supports accountability while still allowing thoughtful progress on complex problems.

What I am looking for next

I am looking for a cloud or software engineering role where building, operating, and improving systems is central to the work. I am most engaged when I can work across application code and infrastructure, rather than treating one as an afterthought.

I want to be on a team that treats infrastructure as a product. Provisioning and maintaining infrastructure is inevitable, and I prefer to do this through version-controlled infrastructure as code, with an emphasis on clarity, repeatability, and long-term maintainability.

Continuous learning is important to me. I do not believe in resting on past experience alone, and I value environments where learning, experimentation, and thoughtful iteration are expected and supported.

Over time, I am looking to grow into architecture responsibility within an organization. That means earning trust through hands-on work, making good technical decisions, and contributing to the direction of systems as they evolve.

What I am not looking for

I am no longer looking to work in helpdesk or device-management roles.

At this stage of my career, I am focused on roles where working with code and cloud infrastructure is the core responsibility. While I ultimately want to grow into a cloud architecture role, I am realistic that this path may involve working as a cloud engineer first, and I am comfortable with that progression.

Open source & learning

Open source matters to me because it shows what is possible when people are motivated to work together toward a shared outcome. It aligns individual interests with collective utility and produces tools that can be genuinely useful in the world, sometimes in serious ways, sometimes simply because they are interesting and well-built.

Contributing to open source has improved my engineering judgment in ways that are difficult to replicate elsewhere. Reading committed code exposes me to a wide range of design decisions and problem-solving approaches. I find it valuable to see how thoughtful trade-offs, structure, and orchestration come together to form maintainable systems.

I also believe in learning in public. Working in the open creates accountability and encourages a deeper level of understanding, especially when collaborating with people I respect and want to learn from. It pushes me to be more deliberate in both my contributions and my reasoning.

Logistics & constraints

I prefer a remote role, but I am comfortable with a hybrid arrangement that includes time in the office. I value flexibility and in-person collaboration when it makes sense.

I am currently based in San Diego and would prefer to remain here. That said, I am open to relocating for the right role and opportunity.

I am very open to travel for work, including team meetups, on-site collaboration, and conferences.

While based in San Diego, I can comfortably work Pacific Time, Eastern Time, and anything in between.

Work with me

If this sounds like a good fit, I would be happy to connect and talk through my experience in more detail. I enjoy walking through real projects, discussing trade-offs, and explaining how systems evolve over time. I also have a more traditional resume, along with code, documentation, and case studies that reflect how I work. If you think there may be an opportunity worth exploring, feel free to reach out.