Excellent idea, Steve! I love to help anyone who is seeking a new position/career move. So, I'll give you some of my details.
I work in state government, in the southwestern US. I work in one of the largest state departments in my state. Last I knew we had about 200 people in IT (both operations and software development). My title is Application Developer 3, although I prefer the term Senior Software Engineer. Yep, I'm a developer. Please don't hold that against me. 😉 I'll give what I've been working on and a little of what the IT department has been working on.
I've been working on an ASP.NET Core .NET 6 web app to handle some complicated transactions for the state pharmacy. This involves using a third-party tool from Telerik for jQuery.
When working with databases we tend to design a database first, rather than use Entity Framework's Code First approach. This approach is different than many software developers' approach. However, it's easy to scaffold an existing database into model classes and the DbContext class using EF Core. For some reason, the DBAs are not involved in designing new databases. I presume they spend time tuning the database, after we design them.
State government is notorious for being extremely conservative, in software engineering approaches, adopting modern technologies, etc. We have been very slow to adopt putting anything into the Cloud. At the beginning of the Pandemic there was a big rush to get some new apps into Azure, but those stalled and failed. I'm not entirely sure why, as I think it either had something to do with network issues or security/firewall. Both of these are outside my wheelhouse. However, I think we'd be better off today if that had succeeded. We are now in a huge attempt to catch up by moving some of our apps into the Cloud.
Along those lines several SQL Server databases have been moved into Azure. I've been involved in one of those migrations, but many more have been moved into Azure. However, all these migrations have been lift-and-shift migrations of our on-prem SQL Server instances into Azure VMs.
The same is true concerning migrating some of our apps into the Cloud. All those we've moved into the Cloud have been lift-and-shift. None of our apps are "cloud ready" or "native cloud apps".
About 5 years ago I was made the Team Foundation Server (TFS) Administrator, when the previous TFS admin left. We have a really old TFS instance, which has been out of support for many years. Therefore, we're working on migrating our source code out of our on-prem TFS, into GitHub (GH). Due to structural differences between how projects and repositories in TFS are structured and the same in GH, this process is taking a LOT LONGER than I know it could have taken. I advocated using GH Import functionality, which would have greatly sped this up, however management had concerns so two of us are busy manually migrating repos one repo at a time out of TFS into GH using two tools: git-tfs and Git-Filter-Repo.
I hope that someone in these forums will find what I've shared here helpful.
Kindest Regards, Rod Connect with me on LinkedIn.