I'm Jesse Anderson, a software engineer specializing in frontend development with deep experience in React and TypeScript. Beyond the UI, I've built and integrated backend services with Node.js, Express, and GraphQL, worked on serverless event-driven systems on AWS, and taken features from concept to production across the full stack.
I'm genuinely curious about how things work — how systems are designed, how data moves, and how everything connects under the hood. That curiosity has pushed me to grow beyond the frontend, and I'm continuing to deepen my understanding of backend and systems design while staying closely connected to product and user experience.
I'm currently open to new opportunities, especially with mission-driven organizations where technology can make a meaningful impact on people's lives. I'm drawn to teams that prioritize collaboration, mentorship, and who care deeply about what they're building and who they're building it for. If that sounds like a fit, let's connect.
Life outside work revolves around family — young kids, high energy, and the kind of beautiful chaos you can't really prepare for. Football season brings some structure to it all. I let the Vikings get my hopes up every year, only to be reminded that hope and heartbreak are kind of a package deal. In the quieter moments, I'm usually deep in a techno-thriller audiobook, a podcast, or down a rabbit hole on whatever topic caught my attention that week.
Tools and technologies I reach for day-to-day.
AI tools have become a meaningful part of how I work as a developer by helping me learn faster, move more efficiently, and tackle problems outside my comfort zone.
Planning before implementation has become a key part of my workflow, using AI tools to think through architecture and break down tasks. I work primarily with GitHub Copilot, Claude Code, and OpenCode.
I've also written custom agent skills: structured, reusable prompts built for specific tasks. This gave me practical experience with prompt engineering and taught me how to get consistent, reliable output from language models, including when to trust that output and when to push back on it.
The architectural decisions, debugging judgment, and code ownership stay with me. I think of these tools as a way to move faster and think more clearly.