J. Thomas

Software Engineer

I am a problem solver trying to become an everything engineer.

Time tracker: 0
Did you know? The average person spends 4.5 seconds on this section.

The best way to describe myself as a Software Engineer is someone who builds new things to solve old problems. I thrive in environments where I’ve got the freedom to fix real issues and suggest smarter ways of doing things. I’ve worked across backend, frontend, and data engineering — but I don’t limit myself to any stack. If there’s a problem worth solving, I’ll pick up whatever I need to get it done, even if it’s weird, new, or totally outside my comfort zone.

When I'm free you'll find me tinkering with code(I'm working on building a custom clock) in more novel settings, playing soulslikes or practicing classic guitar.

My .NET journey started in May 2021 at SETIC/RO, where I interned on the dev team and worked on a monolith called SISNE (the State's system of appoint­ment/dismissal). Up until then, I only had Java EE experience, so I was pretty happy learning .NET.

By May 2022, I moved to the Data Department, but got to keep working with .NET. My capstone project — an IT Help Desk automation platform — featured a custom orchestrator and three .NET APIs (including a SOAP integration with a legacy system). It’s automatically solved over 40k tickets so far, saving about $10 USD per ticket and cutting resolution time by more than 99%.

By April 2024, while I was busy organizing the Data Engineering & Automation team I'd founded in Dec 2023, the Tourism State Department asked for a WhatsApp Chatbot. Relying on my well-documented foresight, I built it in .NET with scalability as the primary concern, designing a graph-like structure within SQL Server to support it.

By May 2025, we launched a full SaaS platform based on that MVP, adaptable to any State Government department. The Tourism State Department planned to purchase a similar solution for $200k USD from a vendor later involved in legal issues — by building our own, we saved $200k USD and avoided the fallout.

Working with .NET

The best developer experience

Because sometimes Python is not consistent enough.

Saving analytics... .NET
Did you know? This page's back-end is built on top of .Net Azure Functions.

My Toolkit

  • .NET Blazor
  • .NET Razor
  • .NET EF Core
  • Dapper
  • Refit