About Jason Rodriguez

I'm a full-stack software engineer who connects technical decisions to user needs and business goals.

How I Work

I believe good software starts with understanding the real problem before writing code. I ask simple questions first: who are the users, what is slowing them down, and what result matters most?

Then I focus on the simplest solution that works well. I weigh tradeoffs, plan for growth, and make clear decisions even when not every detail is known yet.

I bring three perspectives together:

Technical Depth

Strong technical foundations, reliable systems, and code that teams can maintain long-term.

Product Thinking

Focus on customer value, clear priorities, and business outcomes, not just technical output.

Design Sensibility

Clean, consistent user experiences that are easy to navigate and accessible by default.

Many engineers specialize in one area. I've built depth across all three to help teams move faster with better results.

My Journey

Act 1: Foundation (2015–2017)

I started as a CS student at Jackson State University on a full scholarship. Rather than just completing coursework, I got involved in academic research. I worked on a project called Timely, a data visualization tool for digital forensic investigators managing chain of custody information. That work was published at IEEE SoutheastCon 2019.

What I learned: How to approach problems rigorously. How to go deep into a domain. How to communicate findings formally. That quality work gets recognized.

Act 2: Complex Systems (2018–2020)

I joined Lockheed Martin, working on aeronautics research and F-22 flight systems simulation. I worked with Python, C++, and real-time systems. Got an excellence rating on my 2018 performance review. This was high-stakes work where bugs had consequences.

What I learned: How to think about complex systems at scale. How to handle real-time performance constraints. How to work on problems where reliability isn't negotiable. That precision and clear thinking matter enormously.

Act 3: User-Centered Engineering (2020–2022)

I moved to Moses Lake Industries to focus on frontend and UX. I designed internal UIs for complex software. Learned Blazor and C# while watching the ecosystem evolve. This was my first time thinking deeply about user experience, and how engineering decisions impact users directly.

What I learned: Good engineering is not measured in compile time, it is measured in user satisfaction and business results. UX considerations should shape architectural decisions from the start, not be applied afterwards.

Act 4: Design Systems & Scale (2022–Present)

I joined Springbrook Software as a frontend engineer. Quickly moved into UX design and took ownership of the design library powering Cirrus, their ERP platform serving 1000+ enterprise customers. I led the design system effort that unified visual design, components, and patterns across the entire product.

What I learned: How to scale design thinking across a product and team. How to make decisions that benefit thousands of customers. Design systems are as much organizational as technical, they enable teams to move faster while maintaining quality.

Act 5: Product Ownership (2022–Present, Parallel)

In parallel with Springbrook, I founded DataDustr, a company concept focused on helping professionals reclaim digital space through intelligent cleanup of email and files. This taught me product strategy, business planning, technical architecture choices, design system thinking, hiring decisions, prioritization, and shipping discipline.

What I learned: I can own the complete value chain, from identifying a market problem through building the solution and bringing it to market. You learn more from building than from planning alone. Mistakes are tuition in product development.

What Motivates Me

I'm motivated by two things:

→

Solving real problems for real users. I am energized when I can identify a genuine problem and build a solution that helps. Not abstract engineering problems, actual user problems that affect people's work and lives.

→

Building systems and teams to scale. Small, scrappy solutions are fun. But I'm most energized when I can architect solutions that work for thousands of users, maintain design consistency across products, and enable teams to move quickly.

Why I Approach Engineering This Way

I've observed that the best software comes from integration, not specialization. Companies need:

  • ❌Not just narrow specialists who optimize for one dimension
  • ✓But rather integrators who bridge engineering, design, and product
  • ❌Not pure engineering divorced from user needs
  • ✓But rather engineers who understand user psychology and product strategy
  • ❌Not pure product thinking without technical rigor
  • ✓But rather product leaders who understand architectural tradeoffs

Great software comes from connecting engineering, product, and design. That cross-functional approach is what I bring to teams.

Outside of Work

I live in the Pacific Northwest with three cats. I travel frequently (18 states and counting). I code for fun, there is something deeply satisfying about building something just because it is interesting, without the pressure of commercial success.

I do my best work where technical quality, user experience, and business impact are all treated as important.

If that's what your team cares about, I'd be glad to connect.

Get In Touch