I build systems that make work easier. I’m an orchestrator who builds workflow aids to help people save time, resources, and mental bandwidth; run choice analyses and direct research to make sure informed decisions are made; and ease load for users, stakeholders, and teammates alike.
Most recently, I built agentic workflow flags that save subscription tokens, eliminate API tokens, and optimize context while maintaining transparency for human oversight (Relay) on one end and independently presented a cost-benefit analysis for WooCommerce vs PM Pro for the New Orleans Musicians’ Union on the other. Many developers are good problem solvers by nature, but my main aim is to work upstream of the problem: to catch issues before they become problems, make problems easier to surface, and make sure the solutions don’t become problems themselves. I’m currently in search of a Workflow Engineer (Automation Engineer, Solutions Engineer, whatever name you prefer) role where I can build systems and advise on automation at scale, bringing ease to the work of any team around me.
Keyword Bank
Sorted table of common keywords shared by Workflow Engineer and Workflow Engineer-adjacent roles. Further separated individually by the word, and 1 or more places in my resume or individual works I believe demonstrate my execution of the keyword in question.
The best potential hire is one that knows in what environment they thrive. After some thought, I’ve set three lines as guardrails for my personal production environment. I can thrive in most situations, but I do my best work within these parameters.
“When you adopt new AI tools, how do you decide what to sunset or refactor?”
As a workflow engineer, I prefer to work toward the system, not the tool. Chasing the most advanced systems without regard for the workflow that is already established will most often lead to doing the same work over and over from the ground up.
“When a solution isn’t working, how quickly and directly does that feedback reach me?”
I can do my best work when I know what’s not going well. I’m more than happy to reiterate to make something work or to make the process easier, but, if I’m not informed of the issue until it becomes a problem, you may not get my best work every time.
“Will I have visibility into downstream teams and will they be part of solution design?”
The best workflow makes the work flow. I can build for the system I see, and the best results come from a wide field of vision regarding where this work flows downstream