Kyle Krueger / Software engineering

Good software crosses boundaries.

Senior software engineer and technical lead

I work with clients to shape scope and priorities, then help teams carry that work through design and delivery. I combine hands-on implementation with architecture and technical leadership.

AI is central to how I develop software. I build reusable agent workflows and review practices, and help other developers apply them.

Selected work

A few projects

Some of the problems I’ve worked on
and the choices along the way.

System sketch

An application over an agent API

Service teamApplicationAgent APITechnical informationService teamApplicationAgent APITechnical information

The data platform enforces what each user can access. The agent works within those permissions.

Conceptual view

An AI assistant for technical service teams

Service teams needed to find information spread across technical manuals, parts catalogs, and operational systems. The assistant had to respect source permissions and handle uncertain results.

My work

I built the Blazor frontend on .NET, designed authorization, and designed and implemented the infrastructure and CI/CD flow. My role grew from API support into technical leadership and some project coordination, with ongoing responsibility for backlog preparation, planning, code review, and developer support.

Separate domain behavior from presentation

I worked on the integration contracts and separated shared instructions about how the company organizes and presents its data from application-specific presentation instructions for our custom frontend components. The endpoint and contract were designed with future application reuse in mind, including access to the same data and tools.

Enforce access in the data platform

I designed the access approach around the client’s custom OIDC provider, a token exchange with Azure Databricks, and on-behalf-of access. Unity Catalog applies data permissions for each user, so access is enforced by the data platform rather than decided by the AI agent.

Define infrastructure and delivery in code

I designed and implemented the infrastructure and CI/CD flow across the solution. Bicep defines the Azure infrastructure, Terraform manages Databricks access policies, and Azure DevOps Pipelines handles the CI/CD flow.

Where things stand

The team delivered the application through pilot in a production environment. A limited-user release is planned for November 2026.

Jul 2025–present

  • C# / Blazor
  • Azure Databricks
  • OIDC / OAuth
  • Bicep / Terraform
  • Azure DevOps
Link to this project
System sketch

Shared context. Independent judgment.

Prepare & specifyImplementFresh-context reviewPrepare & specifyImplementFresh-context review

A change can be small even when the context it needs spans several repositories.

Conceptual view

How I work with coding agents

A change can touch application code, data, and infrastructure in separate repositories. Coding agents need to understand those connections while staying focused on the task.

My work

I use coding agents in projects I help implement, leading and orchestrating AI use alongside hands-on software development. I built on BMAD and added custom skills for preparing features, planning, implementation, and independent review.

I also lead a biweekly developer meeting focused on using AI effectively and keeping the team current. We share practical experiences and discuss new models, agent harnesses, capabilities, and use cases, learning from one another about what could help our work.

Share context without copying internal tools

I set up a separate internal repository that gives agents access to related codebases. Our reusable skills stay there instead of being copied into client projects.

Review from a fresh context

I ask a separate agent session, sometimes using a different model, to question assumptions made during implementation. I check its findings alongside tests and my own review.

Where things stand

I apply these workflows in my own implementation work and lead AI use on those projects. Independent reviews have caught issues missed in earlier pull-request reviews.

The biweekly developer meeting provides a regular place to exchange practical experience and stay current with changes in AI tools, models, and capabilities.

What I’m exploring

As models improve, I’m trying simpler instructions and checking whether the extra planning helps catch problems.

Jul 2026–present

  • Codex
  • Claude Code
  • BMAD
  • Independent review
Link to this project
System sketch

From stored data to the application

Stored dataApplication APIsWeb interfaceStored dataApplication APIsWeb interface

The data model, API, and interface need to make sense together.

Conceptual view

Connected equipment insights for Vermeer

Vermeer’s telematics platform needed to turn equipment data into useful information for dealers and equipment owners. Our backend work connected stored data to the frontend while priorities and the team structure continued to evolve.

My work

I designed and implemented database tables for storage and access needs and APIs connecting that data to the frontend. I also helped shape technical decisions during feature planning and shared what I learned as our team started working with KQL.

Alongside development, I implemented Renovate for dependency updates, helped introduce SonarQube, and worked on CI/CD and automated test consistency. I later took on delivery lead and scrum master duties, helping prepare work and coordinate with Vermeer’s other development teams.

Design the data and API together

The APIs sat between stored data and the frontend. I designed and implemented the tables and APIs together, considering how the application would store and retrieve the information its features needed.

Make maintenance part of the team’s work

Dependency updates, consistent tests, and code analysis needed attention alongside features. I helped establish practices around those tools and introduced separate refinement sessions for technical debt, giving that work clearer preparation.

Where things stand

Better-prepared work items helped improve the team’s delivery pace as I combined delivery responsibilities with hands-on development.

Code standards and testing improvements made the codebase clearer and easier to maintain, with shared guidance supporting less-experienced developers.

Renovate and the team’s update practices made dependency maintenance more systematic.

Apr 2023–Oct 2024

  • Connected products
  • API development
  • Data modeling
  • KQL
  • Renovate
  • SonarQube
  • CI/CD
  • Agile delivery
Link to this project
System sketch

Connecting existing systems to a new platform

Core ERPAzure integrationsMasterMindCore ERPAzure integrationsMasterMind

The integration is part of the product.

Conceptual view

Connecting logistics systems

MasterMind was a new transportation management system for driver and load planning and execution in one Schneider line of business. We were connecting existing enterprise systems while its vendor, Mastery, was still developing the product.

My work

I led the development team building Azure-based integrations between Schneider’s core ERP systems and MasterMind, covering requirements, technical design, implementation, and support. I brought experience from Schneider’s team customizing, supporting, and extending its Oracle Transportation Management (OTM) system and the applications and integrations around it.

Bring operational knowledge into a new product

I worked with Mastery to help shape MasterMind while we built the integrations. My experience with Schneider’s existing transportation systems helped me connect technical direction with how the business needed to plan and execute its work.

Where things stand

Azure integrations connected the core ERP systems with the new transportation platform.

2019–2022

  • Azure
  • APIs
  • Enterprise integrations
Link to this project

More selected work

My approach

How I work

I use AI for planning, implementation, and review, while keeping responsibility for technical decisions and the software we deliver. I share reusable workflows with other developers and keep adjusting them as the tools improve.

Shape the work with clients

I help clients define scope, prepare backlogs, and plan priorities and delivery. That gives the team a shared understanding of the problem and the work ahead.

Work through the tradeoffs

I consider how a change fits the system, the constraints we need to work within, and where it could go wrong. I use that to guide technical design and planning.

Keep the work connected

I help developers coordinate changes across application code, data, and infrastructure. I give coding agents the relevant context through shared workflows and help colleagues apply those practices.

Review and deliver

I check changes with tests, code review, and a fresh AI review context. I assess the findings and help the team decide what is ready to deliver.

Career

Experience

Twisthink

Team Lead and Senior Software Engineer

Oct 2025 - Present

Lead the Digital Platforms team across client applications, integrations, and cloud infrastructure. Combine hands-on engineering with technical direction, developer support, and helping teams adopt AI development practices.

Senior Software Engineer

Oct 2022 - Oct 2025

Built backend services and cloud infrastructure for client applications, taking work from implementation through deployment across AWS and Azure. Used infrastructure as code and CI/CD to make environments and delivery processes repeatable.

Bravo LT

Senior Software Engineer

Mar 2022 - Oct 2022

Designed and implemented tools supporting changes to benefit and eligibility platforms at Priority Health. Helped the team improve delivery practices, clarity, and alignment through discussion and facilitation.

Schneider

Technical Lead and Senior Software Engineer

Oct 2019 - Mar 2022

Led Azure integrations for a new transportation management platform, drawing on experience with Schneider’s existing systems to help shape the product with its vendor. Guided the team from requirements and technical design through implementation and support.

Team Lead and Software Engineer II

Feb 2018 - Oct 2019

Led a team supporting business-critical truck telematics and transportation execution applications and integrations. Helped lead a major Oracle Transportation Management upgrade, coordinating changes across dozens of integrations and custom applications.

Earlier engineering roles at Schneider

Software Engineer II

Sep 2016 - Feb 2018

Helped define integration contracts with Platform Science as it developed its telematics platform, including the software running on mobile tablets. Implemented backend integrations with Schneider's execution systems to support a phased migration from Qualcomm Omnitracs in-cab units.

Software Engineer I

Jan 2015 - Sep 2016

Built enterprise integrations and customizations around Schneider’s Oracle Transportation Management system to support transportation operations.

Education

Bachelor's Degree in Computer Engineering

Michigan Technological University · 2009 - 2014

Tools & methods

Technical expertise

Applications & integrations

  • C# / .NET
  • Python
  • APIs & enterprise integrations
  • Blazor
  • Java / Spring

SQL & data platforms

  • SQL
  • Oracle SQL
  • SQL Server
  • PostgreSQL
  • Azure Databricks
  • Kusto Query Language (KQL)

Cloud & identity

  • Azure
  • AWS
  • Amazon EKS
  • OIDC & OAuth

Infrastructure as code

  • Bicep
  • Terraform
  • AWS CDK

Delivery & code quality

  • Azure DevOps Pipelines
  • GitHub Actions
  • GitLab CI/CD
  • SonarQube
  • Renovate
  • Automated testing

AI-assisted engineering

  • Specification-driven development
  • Reusable agent skills & cross-repository workflows
  • Independent AI review
  • Codex & Claude Code

Get in touch

Let’s connect

If something here connects with work you’re doing, feel free to reach out. I’m happy to talk through a project or compare notes on how we build software.