Jake L. Muller Principal Software Engineer

Principal Software Engineer & Enterprise Architect

Jake L. Muller I turn what an organization needs into software it owns.

Decade-long track record of architecting scalable healthcare and enterprise platforms while leading high-performing engineering teams. This enterprise experience is complemented by a portfolio of independent, custom-stack products designed, built, and shipped entirely from scratch. I specialize in complete technical ownership: designing system architecture, directing technical strategy, and steering complex builds through to production success.

Describe your solution View resume
  • DNVdesignation
  • 575Kavoided / yr
  • 16systems shipped
  • 10years

Enterprise platform

In order: Web · iOS · Android; ASP.NET · Active Directory; MS SQL · Audit trail.01WEB · IOS · ANDROID02ASP.NET · ACTIVE DIRECTORY03MS SQL · AUDIT TRAIL3 LAYERSIn order: Web · iOS · Android; ASP.NET · Active Directory; MS SQL · Audit trail.01WEB · IOS · ANDROID02ASP.NET · ACTIVE DIRECTORY03MS SQL · AUDIT TRAIL3 LAYERS, TOP TO BOTTOM

Clinical DNV designation

Avoidance $575,000 / yr

Systems 16 projects

What the role actually is.

  1. 01 · Direction

    I translate what the organisation needs into what gets built.

    Department heads describe a bottleneck, not a specification. My job is to sit in that conversation, find the system underneath it, size it against what a vendor would charge, and come back to the CIO with a recommendation that has a number attached. Chair of the Software Developer Committee, presenting roadmaps and beta releases to the C-suite.

    Direct report to the CIO

  2. 02 · Ownership

    Buy becomes build when the maths says it should.

    Five third-party platforms retired and rebuilt in-house, each one sized against a real quote before a line was written. Contracts, evaluations, policy control, scheduling, and fax now run on infrastructure the hospital owns, with the data under its own governance.

    Modelled avoidance, 575,000 per year

  3. 03 · Delivery

    Teams that ship, on systems that survive a survey.

    Mentoring and directing web and mobile engineers through more than ten production releases in a single year. Audit trails, access logging, and retention designed into the schema rather than assembled the month before an inspection, which is how a hand hygiene system ends up earning a DNV designation instead of merely passing.

    DNV designation, 99.9% uptime

Two systems that show how the work gets done.

Clinical safety and owned infrastructure. The rest of the 16 projects live in the register.

  1. C-01 2022

    Hand Hygiene Capture

    Real-time capture of hand hygiene events that moved a hospital-wide safety metric far enough to earn an external compliance designation.

    Designation
    DNV
    Uptime
    99.9%
    Read the case
    In order: Capture point; Event stream; Audit ledger; Unit dashboard.CAPTURE POINT01EVENT STREAM02AUDIT LEDGER03UNIT DASHBOARD044 STAGES, LEFT TO RIGHTIn order: Capture point; Event stream; Audit ledger; Unit dashboard.01CAPTURE POINT02EVENT STREAM03AUDIT LEDGER04UNIT DASHBOARD4 STAGES, IN ORDER
  2. P-01 2020

    Policy & Procedure Management

    Document control for a hospital, with a transactional checkout that makes concurrent editing impossible rather than merely discouraged.

    Documents
    10,370
    Avoidance
    240K / yr
    Read the case
    In order: Check out; Revise; Concur; Publish.CHECK OUT01REVISE02CONCUR03PUBLISH04CLOSED LOOPIn order: Check out; Revise; Concur; Publish.01CHECK OUT02REVISE03CONCUR04PUBLISHCLOSED LOOP, RETURNS TO 01

  3. Full register

    See all 16 projects.

    Clinical, platform, mobile, and product work in one drawing register.

    Open the register

Results the organization can point to.

A DNV designation from real-time hand hygiene capture, and four vendor platforms replaced with software the hospital owns.

Uptime

99.9%

App Installs

5,250

Policies Live

10,370

Shifts Published

628K+

Latency Cut

68%

See full results

Notes

Start with the top three.

Each piece comes out of a decision recorded in the work, so the reasoning and the evidence sit next to each other.

  1. Build versus buy When buying is the wrong answer, and how to prove it with a number Every build recommendation is an opinion until it has a quote attached to it. Here is the arithmetic I do before I open my mouth. 4 min read
  2. Regulated systems Design the audit trail before the feature Compliance built onto a schema is a report. Compliance built into one is evidence. A surveyor can tell the difference, and so can an engineer. 4 min read
  3. Internal platforms Why one workflow across twelve departments fails The cleanest schema is often the one nobody uses. What the platform should own, and what it should leave alone. 3 min read

All notes

Delivered for

  • Garnet Health
  • Live Technology

Two ways in.

If something in the organization is stuck, describe the bottleneck. If you are hiring, start with the resume.

Describe your solution View resume