I help teams solve the right problem.

I’m Jared Linden. 15+ years across product management, sales engineering, and data, often in environmental and operations-heavy industries. I’m looking for full-time roles in sales engineering, solutions consulting, or product, and I take on consulting work in the meantime.

Based in South Jersey. Open to remote, or hybrid around Philadelphia and South Jersey. Raised on a dairy farm in Wisconsin.

Jared Linden

How I’ve worked

Different titles, same instinct: understand what people are actually trying to do before deciding what to build, sell, or measure.

Sales engineering

Five years as the Solutions Engineer at PegEx, running discovery and demos for environmental services companies where compliance was a real buying criterion, not a checkbox.

Sales engineering experience

Product management

Director of Product Management at PegEx, and product manager at Alice.com while also running customer service. I tend to spend more time on the problem than on the feature list, and it usually pays off.

Product experience

Data and modeling

I use SQL, Python, and Excel to get to answers instead of opinions. On my own time I build models, including a Monte Carlo simulation of PGA Tour outcomes, and I use Claude Code for front-end builds and code review on the tools I make.

Side projects

Selected work stories

Short accounts of ambiguous situations, the tradeoffs involved, and what ended up mattering.

  • PegEx

    When “Just Give Us the Data” Wasn’t Really About Data

    A request for raw data turned out to be about regulatory reporting. Understanding that constraint led to a simpler, far more useful solution.

    Shows: Customer discovery, regulatory context, simplifying

  • PegEx

    The Demo Was Their Own Compliance Report

    A prospect came looking for a waste operations system. The deal turned on a reporting burden they hadn’t put on the list.

    Shows: Technical discovery, tailored demos, closing

  • PegEx

    When the Solution Wasn’t the Problem

    Our first product helped companies win work. Customers kept telling us the harder problem came after. That led to a second product, and a new direction for the company.

    Shows: Product strategy, 0-to-1 product, customer research

  • Alice.com

    Designing for How People Actually Behave

    Shoppers weren’t using the product the way we expected. The answer wasn’t more optimization; it was meeting them where they already were.

    Shows: Product decisions, user behavior, partner work

Side projects

Things I build because I want to know the answer.

PGA outcome simulation

A Python model built on historical results and Monte Carlo simulation to estimate the range of outcomes for PGA Tour events. It’s a personal project, so the model itself stays private.

Sweatline

A live tournament analytics platform for daily fantasy sports, now in invite-only beta for PGA Tour contests. It re-simulates the rest of the slate every minute and projects where each of a player’s lineups will finish, with a live cut-line projection and a view of how the top 1% of lineups were built. I designed, built, and launched it.

Visit sweatline.io

Aquaculture operations

Designing and building an operations management system for an aquaculture business, shaped around how the work actually happens day to day rather than how software usually assumes it does.

Working with me

Most of my consulting work sits between sales, operations, and the systems underneath them. That means tightening how deals move through the pipeline, cleaning up the handoffs between teams, and making sure the process and the tools fit how people actually work. Sometimes a new system is part of the answer. Usually the work starts with figuring out what’s really slowing things down.

Recently, for a national waste-to-energy company, I rebuilt their RFP pricing workbook and built an AI agent that feeds it. Weeks of manual bid assembly became a reviewed import, and leadership got one place to see price and margin across every line item.

  1. Observe

    Watch how work actually moves: where deals stall, where handoffs break, and where people quietly work around the process.

  2. Fix

    Go after the root cause, whether that’s a process, a report, a role, or a tool, instead of adding another layer on top.

  3. Make it stick

    Changes only count if people keep using them, so I stay through rollout, enablement, and the first round of adjustments.

Let’s talk

I’m always open to conversations about product, sales engineering, and data-focused work, whether you’re hiring, scoping a project, or just want to connect.