Why me.
I have never held the title Product Manager. I started as a front-end developer, and today I am the product owner and builder of my own products and of the tools a ten-team program plans from.
What the posting asks, and what I have done
| The posting asks for | What I have done |
|---|---|
| Previous experience in engineering and/or design roles | I started as an interface engineer at Organic, as a front-end developer on Bloomingdale’s first e-commerce site, then spent three years as a web developer. I build again now, with AI agents, in Rust, TypeScript and C++. |
| Up-front discovery through user interviews, competitive research and data analysis | Before planning my current program I interviewed every workstream lead, and turned the answers into one script that ten vendor teams now plan from. Earlier I planned, ran and presented a user-testing study of a Toyota dealer site. Case study |
| Findings presented with conviction and rigor | The planning board I built never shows a number it cannot source, and a gate with no data shows a dash, never green. I check my agents’ numbers too: a reported 682 tests turned out to be 384. |
| Helping engineers and designers understand user needs | I write it down before anyone builds. Six design documents for the requirements app I co-built, and for the planning module: research, a gap analysis, open decisions and a mock-up before any code. Case study |
| Messaging around upcoming features | Eight years as an agency producer. I led the design, UX and information architecture teams through the sitemap, wireframes and copy deck for American Express OPEN, and produced a film for Citi that sold a website before a line of it was built. Case study |
| Enabling sales and marketing to win | I created, pitched and presented concepts to Citibank and American Airlines, with proposals and cost estimates, and sat on an agency proposal team. On my current program I ran the two-day close-out roadshow for the client. |
| Design and product taste | Judge it from the prototype on this site and from the products I ship. On one of them I ran a three-stage design review that took clipped controls from 17 to 0. Prototype, idM |
| Exceptional product and operational judgement | I keep decisions of record and reverse them in the open. I built a sixth audio engine, cut it the same day and kept the write-up. I switched an engine from Rust to C++ a day and a half in, and wrote down why. Case study |
| Extreme speed and clarity | A browser music product went from first commit to public alpha in four days. The planning board was a working prototype in five weeks. This site took one day. |
| Shameless curiosity | I rebuilt a classic composing program from its manual alone, by turning the manual into 180 capabilities with a test for each. |
| Teams and agents | Four music products shipped with AI agents, with specs written before code and tests as the referee. I also run a loop where local models work coding jobs against hidden tests. How I work |
The gap, plainly
I have not worked at a product-led software company of Linear’s kind, and my titles have been Scrum Master, Agile Coach and Release Train Engineer.
My product work is on my own products and on tools inside a program. I have not owned a feature with a sales team waiting on the message.
What I have done is the work in the posting’s four bullets at a smaller size: ask the users, write it down, build it, and explain it to the people who have to adopt it. I have also lived the problem on this site from the other side, running multi-team programs in Jira.
Linear’s hiring page says it values slope over credentials. This site is my evidence of slope: one finding, taken from reading to a working page, in a day.