WILLIAM MILLER RAWLS / SALINAS, CALIFORNIA
Software engineer. Practical problem solver. Currently freelancing, researching AI, and building things I care about.
01 / WHAT I BRING
These are the experiences I would bring into the conversation.
Through Globalpundits, I worked on modernizing a decades-old custom VB.NET application for the University of California Office of the President. The work included report conversion, mapping legacy tables and fields to Salesforce objects, and consulting across teams.
That is the kind of modernization I know: understanding the business meaning inside an existing system and carrying it into the next one.
At Travelport, I worked across legacy and modern technologies, including C#, .NET Framework, .NET 8, WCF, Windows services, Redis, and web applications. My work also included AWS modernization and delivery automation with GitHub Actions, Ansible, PowerShell, and Bash.
I bring travel-industry context and experience with systems that depend on other systems. I would still need to learn this team’s particular aviation workflows.
My background includes a lead .NET role at Worldvision Technologies, backend manufacturing systems at Western Digital, virtualization work at Citrix, and desktop and native-code work at Thermo Fisher.
I’ve worked with SQL Server and Oracle, service boundaries, test-driven development, and the practical differences between desktop, web, and backend software. I enjoy sharing that experience and learning from the people around me. My public XLG project, with C# and XML/XSL code-generation tools, is another example of my interest in making development work easier.
I’m currently freelancing and researching AI. My projects include Broke Budget and Aster, a personal AI system exploring memory, continuity, and task orchestration.
Aster asks a question I find interesting: how can an assistant carry useful context forward and turn it into practical help? I’m building around that question with Python, local and cloud models, and file-backed workflows. There’s more to that story, and I’d enjoy talking about it.
02 / MY FIT FOR THE ROLE
For the aviation .NET Developer role, my clearest strengths are senior engineering experience, backend development, modernization, and travel technology. Here is how I would discuss the rest.
I bring more than the requested ten years of experience, a lead .NET background, and work spanning .NET Framework and modern .NET. I can contribute to assessing an application estate and planning a .NET 8-to-10 upgrade. My upgrade guide shows how I would prioritize that work.
My experience includes ASP.NET Core, Web API, microservices, WCF, SQL Server, Redis, Docker, and CI/CD. For the role’s throughput, async, memory, and resiliency requirements, I would discuss concrete systems and measurements. I would also want to understand the team’s approach to domain-driven design, retries, circuit breakers, and observability.
Travelport gives me a relevant connection to travel technology. I would bring that perspective while learning the employer’s aviation domain, operational constraints, and service contracts. I would be precise about which parts of my experience apply.
I have JavaScript, React, and Blazor experience. This site also demonstrates integrating Auro web components. That is a useful starting point for the frontend discussion. I have not worked with Lit yet, and I would need to build that experience. I would also discuss my TypeScript depth explicitly.
Most of my cloud skills are in AWS and Google Cloud. I also bring Docker and delivery automation experience, with a little Terraform experience. This role’s Azure stack would require a ramp-up: App Services, Container Apps/AKS, Service Bus, Cosmos DB, Azure SQL, Entra ID, and Key Vault. I would bring transferable cloud knowledge while being clear about the Azure-specific work ahead.
I have extensive experience with ChatGPT, Enterprise Copilot, and running models at home using myst. That work gives me a practical foundation for discussing context, prompts, model selection, and multistep workflows. Claude is a platform I would need to get up to speed on. For enterprise integration, I would focus on evaluation, authentication, observability, token budgets, failure handling, and scale.
I’ve held a lead .NET role, consulted across teams, and worked across industries and technology generations. I like mentoring, asking useful questions, and helping people find a workable solution. In an architecture review, I want the tradeoffs to be clear enough that the team can make and maintain a good decision.
03 / HOW I WOULD START
I’d start with the application inventory, owners, dependencies, deployment paths, and critical aviation workflows. I’d ask where the team is losing time and where failure hurts most.
I’d capture the existing behavior and performance, choose a representative service, review .NET 9 and 10 compatibility changes, and prove the release and rollback paths.
Once the baseline is sound, I’d target improvements with a clear payoff: simpler delivery, better diagnostics, reusable components, or a bounded AI workflow with a way to judge its results.
WHAT I WANT YOU TO REMEMBER
I’ve spent a career learning unfamiliar systems and helping move them forward. If you need someone who can work through the details, contribute perspective, and be a good person to have on the team, I’d welcome the conversation.
Let’s connectMy current focus and platform experience reflect my own clarifications. The career examples here come from my supplied résumé; the role comparison follows the supplied aviation .NET Developer job description. This is my assessment of the match. My public profiles and projects provide additional context.
Prepared October 5, 2026.