I'm a software engineer with a background that spans hands-on technical work, engineering support, software quality, automation, project leadership, operations, and people management. I build practical tools, systems, and workflows that make technical work more reliable, repeatable, and easier to scale.

Currently: Software Engineer in Test in the medical device industry, working on verification and validation, test automation, CI/CD, hardware-in-the-loop systems, and the internal tooling that holds it all together.

My interests center on AI-assisted software engineering, developer productivity, automation, software quality, systems integration, and the boundary between software and real-world hardware.

• Developer tools and workflow automation
• AI-agent engineering workflows and governance
• Test and quality automation
• Hardware/software integration and technical utilities
• Full-stack, data, and systems projects
• Experiments that turn interesting technical problems into working software

An open-source engineering framework for disciplined AI-assisted software development across coding agents, testing, documentation, architecture, security, CI, and release discipline. Includes bootstrap tooling, governance checkers, agent integrations, reusable templates, an MCP server, and a growing project wiki.

A Microsoft PowerToys Command Palette extension for managing developer workflows. It discovers Git repositories, surfaces branch and stack information, launches development tools and local services, supports custom commands, and can synchronize GitHub repositories in bulk.

A practical tool for organizing and accessing SSH-managed devices, reflecting my interest in infrastructure, remote systems, and small utilities that remove friction from technical work.

A software-testing study and simulation tool built around structured question practice, combining my software engineering work with a long-running focus on quality and verification.

I like software that is useful in the real world, not just technically interesting. My projects tend to emphasize:

• clear architecture and documentation
• automated testing and repeatable workflows
• maintainability and operational awareness
• thoughtful use of AI coding agents without giving up engineering discipline
• practical interfaces between software, hardware, infrastructure, and people

That philosophy is formalized in Eric's Engineering Constitution, which I use as a reusable standard across my own projects.

My path into software engineering was not a reset from another career. I've been doing technical work since I was young, including RF/electronics work early in my career, and later held successful roles in departmental management, operations management, project management, and retail/store management.

That mix matters to how I work today: I care about the code, but I also think about users, operations, schedules, risk, maintainability, communication, and whether a solution actually improves the system around it.

B.S. in Computer Science, Southern New Hampshire University (2026)
Emphasis in Project Management for STEM · GPA 3.92 · President's List

My coursework covered algorithms and data structures, databases, software security, test automation and QA, mobile development, full-stack development, operating platforms, computer graphics, applied linear algebra, intelligent agents, systems analysis and design, and the software development lifecycle.

I also hold an A.S. in Drafting/CAD (Honors) and two A.A. degrees from Santa Barbara City College, along with the Google Project Management Professional Certificate.

My capstone ePortfolio, showcasing enhanced work in software design, algorithms and data structures, and databases, is at esanacore.github.io.

• CS-300: Data Structures & Algorithms
• CS-340: Client/Server Development
• CS-465: Full Stack Development
• CS-370: Intelligent Agent

"The best way to predict the future is to invent it." — Alan Kay