Available for work

Jesse
Anderson

Frontend-focused software engineer with hands-on experience in React and TypeScript, actively building backend skills in Node.js, Express, and PostgreSQL.

This site is a work in progress — just like me.

scroll to explore
About me

Building things
for the web

I'm Jesse Anderson, a frontend-focused software engineer with a passion for building clean, performant web experiences.

My experience has centered around React and TypeScript, where I enjoy creating intuitive user experiences and thoughtful interfaces. Lately, I've developed a growing interest in backend development and the architecture behind modern web applications — how systems are designed, how data moves, and how everything connects under the hood.

I enjoy learning, solving problems collaboratively, and continuing to grow into a well-rounded full stack engineer.

I'm currently open to new opportunities, ideally roles where I can contribute on the frontend while continuing to grow into full stack responsibilities. If that sounds like a fit, let's connect.

RoleSoftware Engineer
FocusFrontend Development · React & TypeScript · Backend Growth
StatusOpen to opportunities
GitHubgithub.com/Jesse9009
LinkedInlinkedin.com/in/jesseanderson12/
Tech stack

What I work with

Tools and technologies I reach for day-to-day.

Frontend
ReactTypeScriptTailwindJavaScript
APIs & Data
GraphQLREST APIsApollo ClientJSON
Backend & Infrastructure
Node.jsExpressPostgreSQLAWS
Tooling
GitGitHubViteWebpackESLintPrettier

Working with AI

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.