MIKE HERNANDEZ

HIRE ME

Looking to hire?

I'm actively seeking software engineering positions

Writing code, and collaborating with people who depend on it, is my bread and butter.

I'm a generalist. T-shaped builder, constantly learning and applying new skills. Since 2010, I've worn many different hats. Some of the work I've done includes

  • Zero-to-one experience cofounding a startup for frontline workers to make paperwork less cumbersome
  • Supporting a former Fed Chair with a data analysis before their 60 Minutes interview
  • Gathering product feedback with sales and engineering during SaaS prospect demos
  • Re-designing the user experience of Search at a Slack competitor
  • Architecting an API to make bed data at housing shelters more transparent
  • Partnering with city leaders in Syracuse and San Diego to make it easier to start and operate a business

I'm open to related roles in

  • Product Management
  • Solutions Engineering (or any customer-facing integration)
  • AI Engineering / Automation in a non-ML capacity
  • Revenue-driving roles in GTM Engineering aka (Growth Hacking)
  • Developer Evangelism

Contact me if you'd like to collaborate.

Currently working on

Software engineering isn't just writing code.

There's a process behind it, centered around feedback loops (including but not limited to testing), predictability (determinism), and communication (with computers, our future selves, and teammates).

We're going through another point-of-inflection right now.

And the last time this happened we were just starting to put computers in our pockets.

I hypothesize software engineers will continue to be expected to do more with less. At the moment, I'm experimenting with LLMs in order to understand:

  • What they're getting better at as new versions of foundational models come out
  • How to effectively leverage them
  • Which parts of the software development lifecycle are automatable

so that I can more productively deliver software, and potentially share any lessons learned. Here's what's on the roadmap

  • Building a tool for new engineers to understand and automate version control. Version control with Git can be intimidating. I'm building a CLI tool to help new engineers and builders use a professional workflow, with support in everyday language, in order to manage their code when using a terminal-based code editor. It explains what commands are being run, helps visualize a change history, and encourages the habit of committing working code frequently.

    This is currently being co-developed with Claude Code as an agentic pair programmer.
  • Replace document (project artifact) handoff with an MCP. Can tool-calling and automatic data retrieval replace design handoff? Figma has an MCP available. This experiment involves taking a UI launched as an MVP, re-designing a SaaS/Enterprise version in Figma, and working with an LLM to port it over using the pre-existing codebase. How good are LLMs at inferring business logic from Figma without annotations and notes?
  • Security through system prompts and custom instructions. Can these two affordances act as a reliable gating mechanism for applying security? The OWASP checklist has existed since 2003. Is it feasible to trust an LLM to interpret OWASP, analyze code, and make dependable recommendations? Can a consensus or committee of LLMs do a better job of catching security flaws?

If this is interesting to you let me know.

HIRE ME