Recipe Tester | Kitchen Helper | Home Cook | Age 34
Based in Portland, Oregon
I’m Jason Miller, and my job at Sipresh is simple: make sure every recipe actually works in a real kitchen.
I’m not a trained chef. I didn’t go to culinary school. I’m just someone who loves cooking but learned the hard way that not all recipes are created equal.
That perspective is exactly why Zoe brought me onto the Sipresh team.
How I Got Into Recipe Testing
I started cooking seriously about eight years ago when I moved into my first apartment. Like most beginners, I relied heavily on online recipes — and I quickly learned that “easy” and “30 minutes” don’t always mean what you think they mean.
I’d follow instructions exactly, only to end up with undercooked chicken, burnt garlic, or dishes that somehow took twice as long as promised. At first, I assumed it was my fault. Maybe I wasn’t skilled enough. Maybe I was missing something obvious.
But after ruining the same “simple weeknight pasta” recipe three times, I started questioning the recipes themselves.
That’s when I began keeping notes — what actually took 10 minutes versus what took 20, which steps were unclear, which ingredients seemed unnecessary. It became a habit. Every time I cooked, I annotated the recipe like I was grading a test.
The Recipe That Changed Everything
In 2021, I tested a recipe for braised short ribs that completely fell apart — not the meat, the instructions.
The timing was off by over an hour. The steps assumed I knew how to sear meat properly (I didn’t). The recipe called for “a splash of red wine” without defining what a splash actually was. And worst of all, it promised fall-off-the-bone tender meat but delivered something closer to leather.
Instead of giving up, I rewrote the recipe as I went. I adjusted the timing, clarified the steps, and tried again the next weekend. The second attempt worked.
That experience taught me something important: recipes don’t fail because people are bad cooks. They fail because instructions are poorly written.
What I Do at Sipresh
At Sipresh, I test recipes exactly the way most readers would cook them — after work, with limited time, using ingredients from a standard grocery store, and without professional equipment.
My role involves three main tasks:
Testing for clarity: I follow each recipe line by line and flag anything that feels confusing, vague, or assumes prior knowledge. If I have to Google a technique, it needs better explanation.
Verifying timing: If a recipe says something takes 15 minutes, I time it. If it actually takes 25 minutes, we update the post. Accurate timing matters when you’re trying to get dinner on the table.
Checking ingredient accessibility: I shop at regular grocery stores — Trader Joe’s, Safeway, Fred Meyer. If I can’t find an ingredient easily, we either swap it for something more common or make it optional.
The goal is simple: if I can make it work on a Tuesday night after a long day, chances are you can too.
My Testing Process
Here’s what happens when Zoe sends me a recipe to test:
- First cook: I follow the instructions exactly as written, taking notes on timing, clarity, and any moments of confusion.
- Feedback: I send Zoe detailed notes — what worked, what didn’t, what could be clearer. This usually results in revisions.
- Second cook: I test the updated version to confirm the changes improved the recipe.
- Final review: I check one more time for flow, ingredient order, and any lingering questions a reader might have.
Some recipes pass on the first try. Others require multiple rounds of testing. I’ve cooked the same dish five times before giving it the green light.
What I’ve Learned From Testing Hundreds of Recipes
After testing recipes for three years, a few patterns have become clear:
Clear instructions matter more than technique. A well-written recipe can teach someone how to sear meat or make a roux. A poorly written one assumes you already know.
Timing is everything. If you promise 30 minutes, deliver 30 minutes. If it takes longer, say so upfront. Readers plan their evenings around those estimates.
Small details make a big difference. Specifying “large dice” versus “small dice” changes cooking time. Explaining when garlic should be “fragrant” versus “golden” prevents burnt garlic. These details aren’t nitpicking — they’re the difference between success and failure.
Ingredient accessibility matters. Not everyone lives near a specialty market. If a recipe requires an ingredient most people don’t have, it needs to be optional or substitutable.
Why I Care About This Work
I test recipes because I remember what it felt like to fail at something that was supposed to be “easy.”
Cooking should build confidence, not destroy it. A good recipe should feel like having someone cook alongside you — someone who anticipates your questions and answers them before you have to ask.
That’s what Sipresh aims for, and it’s why I take this work seriously.
Every recipe I test is meant to feel achievable, familiar, and worth repeating. If I wouldn’t cook it again, it doesn’t belong on the site.
Outside the Kitchen
When I’m not testing recipes, I’m usually meal prepping for the week, trying new grocery store finds, or experimenting with ways to make cooking more efficient.
I’m the person who reads ingredient labels for fun, reorganizes the spice cabinet by frequency of use, and genuinely enjoys doing dishes (it’s meditative).
I also read recipe comments obsessively. Feedback from real home cooks matters more than anything else — it’s how we know what’s working and what needs improvement.
Let’s Keep Cooking Simple
If you’ve ever felt frustrated by a recipe that didn’t work as promised, I understand. My job is to catch those issues before they reach you.
Every recipe on Sipresh has been tested, timed, and refined to work in a real kitchen. That’s a promise.
Get in touch:
Jason@sipresh.com