Open to new roles · Denver or remote

I end up wherever the gap is between what a client needs and what actually ships.

Eight years across the stack: data, application logic, deploys, the K8s underneath, the alerting on top. Most of it starts with listening, so what gets built is what was actually needed. Lately that points at agentic AI: MCP servers, plugin libraries, and the knowledge bases agents work from.

Download resume
Will Fellhoelter laughing, in sunglasses, against a blue sky
Currently01Principal Software Engineer at Accuris. Agentic AI development, operations, K8s. Jack of all trades and master of none.02Building Sauce. An agentic operating loop for Obsidian, open source.
Years across the stack
8
Tools behind the org’s MCP gateway
250+
Microservices in operations, 6 regions
100+
Repositories moved to GitHub
1,000+
AWS accounts reviewed for architecture and cost
70+

Accuris, 2025 to now. All of it with a team.

01How I work

Defined, communicated, delivered.

It starts with listening: understanding what someone actually needs, then using the engineering to get there without the misunderstandings that derail most projects. Then making it repeatable, so the next team doesn’t start from zero.

  1. 01

    Defined

    Sit with the people who need the thing. Listen more than talk. Pin down what done looks like before anyone writes code.

    forml → first engineering hire, scoping with founders and enterprise clients

  2. 02

    Communicated

    Say it back in plain language, argue the approach while it’s still cheap, and keep the decision where everyone can find it.

    Accuris → design reviews with teams across 70+ AWS accounts

  3. 03

    Delivered

    Data, application code, deploys, the K8s underneath, the alerting on top. Whatever layer the outcome needs.

    forml → one-click on-prem installs, onboarding from 3 days to 4 hours

  4. 04

    Repeatable

    Turn the one-off into the pattern: an MCP server, a plugin, a template, a note an agent can read.

    Accuris → the plugin library and MCP mesh teams use every day

02Selected work

Work I’d point you to.

Agent tooling for a whole org, observability for hundreds of services, installs on someone else’s hardware. Built with platform, product, and engineering teams along the way.

Accuris · 2025–2026 · With the platform team

MCP mesh

Governed agent tooling for the whole org: 250+ tools behind one gateway, SSO, central observability. Built the first internal MCP servers and the plugin library, then, with the platform team, the mesh every team uses. Our own servers for New Relic and PagerDuty live inside it instead of paid vendor connectors.

Accuris · 2026 · Runs on the mesh

From a page to a documented root cause

Point the plugin at a PagerDuty alert. It works through the team’s skills and our own context-aware MCP servers, finds the root cause in New Relic, and writes the finding into the team’s Obsidian vault. Troubleshooting and documentation happen in one pass, so the notes are never behind the incident.

  • Accuris · With the platform team

    The same observability for every service

    Configured the New Relic K8s operator with the platform team so every deployed service gets the same APM injection automatically. No manual setup for developers, consistent naming, and one way to troubleshoot across the org.

    400+

    Services instrumented the same way, no developer effort

  • Open source · 2026–

    Sauce

    An agentic operating loop for Obsidian. Notes become node-based work graphs that agents like Claude Code and Codex execute in isolated workers, with scheduling, retries, handoffs between agents, and a persistent task store. Started as a loop-based forward deployment mechanism, rebuilt around graphs. Versioned vault platform shipped via Homebrew, MIT.

    $ brew tap willfell/sauce$ brew install willfell/sauce/sauce
    github.com/willfell/sauce

  • forml · 2024–2025

    On-prem in four hours

    First engineering hire at an AI startup. Worked with the founders and enterprise clients to understand what they actually needed, then built one-click on-prem deployment so the deals that required customer-hosted installs could close.

    3 daysto4 hours

    Enterprise onboarding time

  • Cerner · Lendflow · Project Canary

    Ephemeral environments, three times

    Self-service test environments with data seeding and automatic cleanup, built for three different orgs: an AWX portal at Cerner, ephemeral infrastructure for dev and QA at Lendflow, a UI with branch and data-source selection at Project Canary. The problem I keep getting handed.

    −32%

    Environment costs at Lendflow

03Experience

Eight years, seven roles.

Full resume, PDF
  1. Mar 2026 – NowAccurisPrincipal Software EngineerMCP mesh, observability, multi-region K8s, 70+ AWS accounts
    • Built and launched the MCP mesh: one governed entry point to 250+ tools for engineering, product, and cross-functional teams, with SSO and centralized observability
    • Designed and shipped production MCP servers that give AI agents natural-language access to internal systems, including our own New Relic and PagerDuty servers in place of paid vendor connectors
    • Built the incident plugin that takes a PagerDuty alert to a root cause in New Relic and documents it in the team’s Obsidian vault in the same pass
    • Grew the AI plugin library into how teams use AI day to day, turning one-off prompts into repeatable workflows
    • With the platform team, rolled out the New Relic K8s operator so 400+ deployed services get consistent APM injection with no manual work from developers, standardizing naming and troubleshooting across the org
    • Operate 100+ microservices on K8s across 6 regions; led the multi-region buildout of compute and data tiers
    • Help map out and drive the standardization of deployment and CI/CD across 1,000+ repositories with templated K8s
    • Own architecture and cost across 70+ AWS accounts, reviewing designs with teams for cost and security
    • Build and run CDC pipelines from PostgreSQL into Databricks for mission-critical data
  2. Apr 2025 – Mar 2026AccurisSenior Software EngineerGitHub migration, first internal MCP servers
    • Led the move of 1,000+ repositories to GitHub and consolidated CI onto GitHub Actions with reusable workflows
    • Built the first internal MCP servers and the original AI plugin library
  3. Aug 2024 – Apr 2025formlSenior Full Stack EngineerFirst engineering hire, on-prem deploys
    • First engineering hire; worked directly with the founders and enterprise clients to scope requirements, set quarterly roadmaps, and ship the platform end to end (Python, Angular, AWS, PostgreSQL)
    • Built one-click on-prem deployment for enterprise clients, cutting onboarding from 3 days to 4 hours and unblocking deals that required customer-hosted installs
    • Led the API and architecture work that carried the platform through 2x user growth in 2 months; promoted to Senior
  4. May 2023 – Aug 2024Project CanaryDevOps EngineerEphemeral environments, RAG, SOC 2
    • Built a self-service tool that lets developers and QA deploy an isolated test environment from any branch in one click, with selectable data sources and automatic cleanup
    • Built a RAG search app on AWS Bedrock and vector databases for querying internal documents across departments
    • Ran observability for 10+ critical services (99.99% uptime) and moved it to New Relic, cutting monitoring costs 14%
    • Fixed bottlenecks in high-throughput time-series PostgreSQL databases, improving query performance 23%
    • Drove the security work behind passing SOC 2 Type I and Type II, automating controls and cutting audit prep ~30%
  5. Aug 2021 – May 2023LendflowDevSecOps EngineerOpenSearch logging, WAF, on-call
    • Centralized logging on OpenSearch, cutting the time to pinpoint production issues from ~3 hours to under 10 minutes
    • Built ephemeral dev and QA environments to replace always-on ones, cutting environment costs 32%
    • Put AWS WAF and CloudFront in front of the platform, reducing security incidents 60%
    • On-call engineer for a platform serving 20K+ users; cut average ticket resolution time 25%
  6. Mar 2020 – Aug 2021MCG HealthCloud / DevOps EngineerOn-prem to Azure, Chef to Ansible
    • Led the migration from on-prem infrastructure to Azure for 3+ teams
    • Built modular Terraform components that cut new environment setup from ~2 days to 1 hour
    • Moved configuration management for 100+ Windows servers from Chef to Ansible, with Datadog monitoring
  7. Oct 2018 – Mar 2020Cerner CorporationSystem EngineerAnsible automation, AWX portal
    • Wrote Ansible playbooks for server configuration and troubleshooting, saving the team 40+ hours a month
    • Built an AWX-based portal for scheduling data restores and spinning up ephemeral test environments
    • Taught biweekly Linux fundamentals sessions for new hires through Cerner’s Tech Academy
  8. 2018Wichita State UniversityManagement Information Systems

04Positions

Things I’ll argue for.

I like a real discussion about the right way to do things, and I change my mind when the better argument wins. These are the ones I keep coming back to.

  1. 01

    Listen first, argue early, write it down.

    Most rework comes from a misunderstanding nobody caught early. So I listen more than I talk, push back while it’s still cheap, and put the decision where the next person will look.

  2. 02

    Plugins over prompts.

    A prompt helps one person, once. A plugin backed by an MCP server gives a whole team the same tools, the same context, and the same result.

  3. 03

    The knowledge base comes first.

    Personal notes, team runbooks, org decisions. If it isn’t somewhere an agent can read it, the agent is guessing. Obsidian, for me and for the teams I work with.

  4. 04

    Workflows need a schema.

    Agents are only as consistent as the work they’re handed. Typed notes, templates, and defined handoffs beat clever one-off chains. Sauce is that idea, open-sourced.

05GitHub

5,012contributions in the last year

github.com/willfell
Last 12 months on GitHub
  • willfell/sauce

    Agentic operating loop for Obsidian: node-based agent execution, versioned vault platform, shipped via Homebrew

    JavaScriptMIT

  • willfell/homebrew-sauce

    Brew up the sauce

    RubyHomebrew tap

  • willfell/will-fell

    This site. Next.js and Terraform on S3 and CloudFront, deployed by GitHub Actions on every merge.

    TypeScriptTerraform

Working on something that needs to ship?

Platform, AI, customer-facing engineering, or a role that doesn’t have a name yet. If the hard part is getting it into people’s hands, I’d like to hear about it.

Download resume
willfellhoelter@gmail.com