Loyalty · priceless
Tuesday. Named skill-up. Playbook TCS kept. Dawn still quoting the OS-level line. Throughput they renew. Night operator, month three.
Customer in the room. Something that runs Tuesday. A path the next FDE can follow.
Deployed with Dawn · West Bend · Navy Federal · Mercedes · Volkswagen · Toyota · Micron · PepsiCo · Ace · Kohl’s · BNY · JPMorgan · Farmers · NWM · WR · Cargill · Harvard · Smith & Nephew
Carex is hiring the first Forward Deployed Engineer for a Madison fintech: partner with customers, design/build/configure/deploy AI workflows and agents, define the metric before, measure after, found the playbooks. Formal SWE not required. That is Informatica IPS/SEAL plus 24 months of measured agents. Epic Agent Factory preferred — I have not shipped inside Chronicles; I will take it on the floor. Job map →
Embedded until the unofficial definition is named. 19/20 recovered. Dawn featured because the load moved. No predefined playbook is the job I already wrote.
Workflows, integrations, SOAP/REST, CDC, agents, bounded MCP. Configure first. Build when configure is a lie. Hypercare default.
Dawn 8h→1h. Mercedes +200%. West Bend −50%. PepsiCo zero data loss. Lab 1.39→37.47 tok/s. Number first.
Stand with operators. Load, journal, SKU, night workaround. Not the slide.
AS/400, SOAP, messy CSV, agent skills. Make it operable. Do not wait for a clean ontology.
Environment Summary. Six-class test. Named skill-up. If they cannot run it Tuesday, I did not finish.
Compose + CUDA: TabbyAPI EXL3, Ollama, Open WebUI, SillyTavern, SearXNG. Forced CUDA offload, VRAM pre-warm, failover. huggingface.co/jpanasuk/tabby-tavern-stack
Discover, bench decode/prefill, GPU routing, SQLite, CLI + PDF. 1.39 → 37.47 tok/s. Warm stream ~76 tok/s. Measure before claiming.
Agents see Docker/network. Not host-root. Hand the agent the boundary — how you put an agent next to a bank or a clinic without becoming the incident.
Systems → Architect → Synthesis → Validator. Isolated Python venvs. Pydantic JSON handoff, not free text. Self-healing validator writes/executes/debugs until the contract passes. OpenClaw WhatsApp, 10+ skills.
Also retained through 2025 for Informatica production rescue: Grid/HA, PowerExchange CDC, IDQ, v9/v10, SOAP/REST, install-to-go-live. SOW story is the gold box on page 7. Ivy Funds · Fed Reserve Philly · Farmers Linux SOAP/REST · Giesecke REST/SOAP, VMs, GitHub, Docker.
Parachuted into 20 troubled accounts. Recovered 19. Milwaukee insurer: three-month outage closed in two days — one buried IBM DB2 driver. Monitor, troubleshoot, improve reliability. That is the job after the demo. IPS artifacts →
PowerExchange for AS/400 via remote journals. Mentored env management, Type 2 warehouse, security, upgrades. Customer: OS-level knowledge let them automate sourcing outside ERP (~90% of source data). Velocity. IPS: rock star. Full story is the right column of page 4.
Parachute. Taught the on-the-ground TCS team Grid/HA. Longest-running workflows +200%. Software rec for DW growth → $500k deal. Performance-tuning docs stayed with TCS. Founding FDE: leave the path, not a hero week.
Talend 8 simple through complex on a live platform. GitLab CI/CD. Redshift + SQL Server. On-call incident command and root-cause writeups the next morning. Messy production, not a sandbox — the FDE motion.
PepsiCo Grid/HA + DIH NA/LATAM. Led v9→v10 zero data loss. Teradata → Big Data (~40% analytics lift). Tuning written into go-live timelines. Ace PowerCenter → Big Data with business + QA. Ameriprise EDG: IDQ, EDC, Axon. 200+ CDEs. 24×7. Data quality as a control.
Analyst → Program Manager in ten. SEAL. Teams of 7–14. $4M+ services in two years. v7–v10 upgrade specialist. Consultant of the Year runner-up (2016). Parachute closer: 20 in, 19 recovered. Discovery, decompose, scope, implement, adopt, hypercare. Ladder: Sr. Analyst → Principal → TDM → SDM → Program Manager.
Also: Harvard v9 / Solaris off-load · Merrill/Time Inc. SFDC · Ivy Funds Grid/HA · Fed Reserve Philly Windows→Unix · Giesecke REST/SOAP, VMs, GitHub, Docker · Micron Fast Clone + Financial Force · lectures v7–v10.
Medicare + MTM marts. EDW test lead. Analyst → Sr. Analyst 4/5. Quality first — quote is theirs.
Live mill ERP. Demantra Quarterly Excellence Oct 2006. Horizon Milling CFO Award 2005. 24/7 across 20+ warehouses. Fireworks weekends continued after start.
$800K+ seasonal inventory. Turnover under 3 months. Four full-time sales. Profit up six years. Class B shooter. No schema, no second take. Loyalty is the metric.
FDE · customer embed · discovery / decompose / configure-or-build · metric before/after · playbooks · hypercare · Madison hybrid 3 days
Agents · Four-agent runtime on local Ollama (Systems · Architect · Synthesis · Validator, isolated venvs, Pydantic JSON, self-heal) · OpenClaw · TabbyAPI EXL3 · MCP · RAG — not yet Epic Agent Factory; will take it on the floor
Code / data · Python · SQL · Docker · Linux/WSL2 · GitLab CI/CD · PowerCenter · Grid/HA · PWX CDC · Talend 8 · IDQ · SOAP/REST · Oracle · SQL Server · DB2
Education · BBA MIS, UW–Eau Claire 2004 · Informatica Certified Specialist: Admin, Big Data Admin, PowerCenter Developer I & II
Operating line · Customer satisfaction is worthless. Customer loyalty is priceless. · The clip / the talk →
Future data-platform utilization: Informatica v9 capacity + upgrade, multiple HA and Grid components. Target Grid/HA on commodity (Cisco or IBM); cutover off AIX. Current volumes + 3-year growth. Briefed through Senior VPs. ~$2M software close. POCs when VMs were not enough (DQ / MDM on their data).
Resourcing plan with Informatica RMO + NFCU HR. Hands-on: PowerCenter, Metadata Manager, Data Quality, PWX CDC for DB2 on mainframe, Web Services. Technical-stack test strategy for go-live / business acceptance. Mentored NFCU on install, services config, naming standards. Same motion years after Dawn: they can run it without you in the chair.
Not a slogan on a careers page. The operating line I stood on in that room — Gitomer’s Teal Book of Trust — and the line I still run on every deploy. Founding FDE is this: the agent still running Tuesday, not a demo they clapped for once.
A demo they clap for. CSAT they forget. An agent that ran once in a conference room. Policy. “We shipped.” Two clicks they would not make.
Tuesday. Named skill-up. Playbook TCS kept. Dawn still quoting the OS-level line. Throughput they renew. Night operator, month three.
If ops cannot run the agent without you, you installed software. You did not found a function. This talk is how I still show up.
Not the CEO. The customer. Your kids eat because they buy. If they don’t buy, your kids don’t eat. Gitomer, Sales Bible, 1993.
Policy is how you lose a lifetime in two clicks. Founding FDE: never leave the customer with “the model can’t.” Find the path.
You don’t earn loyalty in a day. Dawn was not a one-week hero. 8h→1h because I came back the next morning.
John’s kids. Carnegie. Greene Law 4. Trusted advisor is the buying atmosphere. Agents don’t get that. You do.
Named skill-up. Playbook TCS kept. QA twin. If it only lives in your head, it is satisfaction. If they can run it, it is loyalty.
Featured on informatica.com because the load moved. CSAT is a survey they forget. Throughput is a number they renew.
“Nothing happens until a sale is made.”
Yesterday I had a problem with one of my accounts at Bank of America. I had been with them since 1999 — all of my adult life. To sign up they gave me an MSOE T-shirt. Freshman year, that was more than enough to sign just about anything. I called and asked them to take 30-day and 60-day past-due notices off the account because of a lost or stolen card. Which of course was lost or stolen.
I get Ben on the phone. Obligatory hold. Ten minutes later he comes back: he can’t click the button, but he can transfer me to Kari. I told him his iSeries profile was probably set up wrong by some goof in IT. He clicked me over fast. On hold for Kari I am already dreaming — car loan, the condo in Wrigleyville, Cubs tickets if the stock hits $20. Kari greets me curt. Policy: report the credit accurately. She cannot help.
If you wouldn’t want it done to you, don’t do it to someone else. BofA could have kept me for life with two clicks — home loan, car loan, hundreds of thousands in interest. Because of a “policy,” I was gone. Satisfaction is the lowest acceptable service. Loyalty is a process, not a single action. Founding FDE: if the night operator cannot run the agent, you left them with Kari’s policy. Never leave the customer with “the model can’t.” Find the path. This column is the whole example.
“You don’t earn loyalty in a day. You earn loyalty day-by-day.”
Easy to say. Hard to do. I had been working at Dawn Foods in sparkling Jackson, Michigan. Highest unemployment in the United States at the time — something approaching 10%, and that only counts people “actively looking.” Jackson County was the worst in the state. Some economists put it at 12–14%. Customer loyalty in Jackson may mean the difference between staying in business and the unemployment line. So think about who pays you.
Once you know who pays you, it is obvious: satisfaction is the minimum. I was not in Jackson to be satisfactory. I was there so Dawn would still want Informatica in the building when I was gone — and so the warehouse load that used to take eight hours would take one.
Mentored env management, Type 2 warehouse, reporting staff. They still quote it: “His knowledge not only of the Informatica suite but also at the operating system level has been truly invaluable.” OS-level knowledge let them automate sourcing outside ERP — about 90% of source data. IPS: rock star. That is day-by-day.
Satisfaction is a demo they clap for once. Loyalty is the agent still using what you launched on Tuesday. Dawn 8h→1h got used. That is a deploy, not an install. This column is the whole example. Next page: two more, same pattern.
“You can make more friends in two months by becoming interested in other people than you can in two years by trying to get other people interested in you.”
The BI lead architect at Dawn, John, has four daughters. Sam in the Navy, in Japan. Amanda in 7th grade, just started track — 100-meter hurdles. Jordan at Georgia Tech. Darby living with her mom because she doesn’t like Dad’s rules. John’s line: “The Marines prepared me for everything except four teenage girls in the house at the same time.”
I am not wasting your time. This is the hardest thing I do. For me, anyway. Shut up and listen. Ask questions. Carnegie said it. Robert Greene said it as Law 4: always say less than necessary. The more you talk, the more common you appear. Being liked leads to being a trusted advisor. That is the first part of a buying atmosphere.
Buying a beer? Love. Buying a car? Love. “How much do I have to spend to get that part replaced?” Hate. Your favorite bar raises the price fifty cents. Does price still matter? All things being equal, people want to do business with their friends. All things not being equal — they still do. Gitomer, Little Black Book of Networking, 2007.
I knew John’s kids because I asked. That is not a trick. That is the work. A fintech floor will have unofficial definitions of a good workflow and a night operator who invented the workaround in 2011. If you do not listen, you will ship a dashboard. If you listen, they will actually use what you launched. This column is the whole example.
When you are on the client site and they believe in you, they start believing in the platform. You represent the entire enterprise. At Dawn, because of their belief in Informatica, John told Trillium they were not interested. They would go with Informatica’s data-quality solution when the funds were there. How do I know? He told me. Over lunch. Why? Because he trusts me. Why does he trust me? Because we established a friendship. He was telling our competitors he did not even want a proposal. That is not a close. That is a relationship that closed the next product by itself.
The list we held ourselves to. At Dawn a lot of things were going wrong — process and people. I did not skirt it. Gene and I delivered documentation above what was expected. On site before they arrived and after they left. Weekly email on milestones. Dawn had a sincere lack of project management — Velocity plans and WBS for BI were a major value-add.
01 Tell the truth. Once truth is violated, trust evaporates and may never return.
02 Deliver what you promise. People hope you will. Then they measure you.
03 Do what you say you will do. Reliability is the test.
04 Communicate in a timely manner. Rapid response shows you care.
05 Bring value beyond the product. What you do to help them succeed is your character.
06 Be on time. Respect for their clock. Give away what you want. If you want trust, trust them.
Confidence is built on work you already did. Quick hit: PowerCenter 8.6 up. When MDM install problems hit, they already believed we would resolve it. An index over an update mapping increased confidence tremendously. Then you build confidence in their ability to do it next time without you in the chair. Navy Federal was the same motion years later: scope the 3,000-hour V1, install, test, train, wrap, finish ahead.
If they like you, and they believe in you, and they trust you, and they have confidence in you… then they may buy from you.
IPS embed. Dawn, Navy Federal, Mercedes, West Bend. Unofficial definitions. Night workaround from 2011. Same facts, two rooms — BNY with VPs and CEO Abbasi.
Workflows, agent skills, schemas, integrations, lightweight apps. Configure first. Hypercare. Monitor, troubleshoot, improve reliability. 19/20 recovered.
Posted as a requirement. Already the cover of an Environment Summary. Dawn 8h→1h. Mercedes +200%. Lab 1.39→37.47 tok/s. If the number did not move, we shipped theater.
Playbooks, skill-up, QA twin of production. TCS kept Mercedes. Farmers named the skill-up. Hire two starts on page 4, not Slack.
JPM CoE roadmaps. If three customers hit the same wall, it is the next feature. Field notes weekly.
I already build the tools I wish I had on night one. Local Grid Suite is that instinct on a GPU. Same for a customer ops queue.
Clients asked for me by name. “Rock star.” Loyalty talk on Dawn’s floor. Clear, honest, proactive.
No predefined playbook is the posting. I wrote the operating path on the floor for twenty years.
Four-agent runtime on local Ollama: Systems → Architect → Synthesis → Validator. Isolated venvs. Pydantic JSON. Self-heal until the contract passes. Not a slide about agents.
Judgment you asked for. Most “AI projects” need a better process, not another model. I say so in the room.
Consulting Manager. Formal SWE not required — you said delivery matters more. That is this résumé.
Sand Creek, WI. Hybrid as posted. The constraint lives with the customer. I go there.
No-code builder inside Epic EHR (HIMSS 2026 preview; wider 2027). Art / Emmie / Penny personas. I have not deployed an agent inside Chronicles. I have deployed agents with boundaries, customer workflows, and go-lives in regulated rooms (Navy Federal, Smith & Nephew FDA, Prime Medicare). I will take Agent Factory like Grid/HA: embed, measure, write the standard.
Warehouse load 8h→1h. Featured because the number moved. Unofficial definitions. Night workaround. Mentored the team that kept running it. That is “partner with customers, design/configure/build/deploy/support” on this posting.
3,000-hour V1. Install, services, naming standards, go-live tests written down. Mentored NFCU so they could operate it. Recurring pain became the kit. That is “translate needs into reusable playbooks” on this posting.
Parachute. Taught TCS Grid/HA on the floor. Longest workflows +200%. $500k DW growth rec. Tuning docs left behind. Recurring pain became the kit — not another hero week.
20+ nodes India / UK / New York / Chicago. RHEL GFS + PowerCenter Grid/HA. Built DR, ran the US DR test. “One of the best that Informatica has to offer.” Relationship is the channel.
With Informatica regional managers I wrote the client statements of work: full contract wording, resource levels (analyst through principal), estimates and assumptions. Range was mom-and-pop duration through Micron 2,080 → 7,000 hours and Navy Federal 3,000 hours with Informatica RMO plus their HR. Harvard v9 resource plan through hypercare, not just go-live. Deliver inside the estimates. The two-week POCs on this page are how that SOW gets signed.
Sales does not install PowerCenter and Data Quality on the customer’s metal. Unless the quarter is on the line. I ran the POC anyway. Full smoke. Use-case analysis. Flying colors. The deal closed immediately after. Same window at Volkswagen: complete Grid/HA, live demo a day early.
They wanted the complete stack, not a subset: bonded network / dual NICs, Oracle RAC on InfiniBand, three 8-core PowerCenter servers. Two-week implementation window. Walked the live demo and finished a day early.
Parallel Data Quality on the other side of VW was burning down at the same time — that was the pressure in the building, not my DQ failure. Four customer consultants shadowed the entire install and demo, taking notes. They can run the next one. That is the close.
Two weeks. Day early. Four people who can repeat it. The deal does not wait for a lab VM. Founding FDE: if they will only buy what they just watched run on their floor, you install on their floor.
The customer wanted PowerCenter and Data Quality installed locally on their systems. Informatica sales does not do that. The official path is the VM lab. They would not buy from a VM. So I installed it on their metal anyway — because a sales rep needed to clear the quarter, and a two-week POC was the only thing that would.
Full smoke testing. Use-case analysis against their data. It passed with flying colors. Two weeks. The deal closed immediately after. That POC pushed someone over their target sales goals for the quarter. Client unnamed on this copy — the motion is the point.
Policy said no. Quota said yes. I found the path. Same operating line as Kari at BofA, inverted: the customer wanted yes, so I helped them to yes. Founding FDE never leaves them with “we don’t install that locally.”
The parachute was never a hero hour. It was a written operating path: what is running, what is on fire, what to change, how to prove go-live, who on the customer team can run it after you leave. Same loop the RTX lab uses now. Author: Jeremy Panasuk, Informatica Professional Services.
PowerCenter Environment Recommendations. Owner and date on the cover. How mixed internal / consultant / offshore developers actually use the platform. Numbered review of what was measured and changed — not a wish list.
Informatica Upgrade Roadmap. Current-state performance review, then the product recommendation: PowerCenter with Grid and HA. Internal domain/gateway/node design. External clustering and the shared filesystem that makes or breaks Session on Grid.
Phase 2 is not “more of Phase 1.” Name the product features the next workload requires, the topology that will hang, the filesystem that will plateau partitioning, the skill-up the team still needs.
Jeremy Panasuk / IPS. 28 slides. Why v10, PAM, three upgrade types, six classes of test, Data Validation Option to make same-data honest. This is the coaching deck. The roadmap is the customer-specific evidence. Together they stop “just run the installer.”
Founding FDE translation: Environment Summary = customer process + unofficial definitions + metric. Roadmap = configure vs automate vs build vs simplify. Phase review = next increment, skill-up named. v10 deck = how the room chooses a path and tests it. Same three artifacts before anyone touches Agent Factory, a workflow, or a prototype. Performance loop →
Jeremy Panasuk, IPS. Not an anonymous slide. Someone the customer can call.
Mixed internal / consultant / offshore. Utilization first. Config that is applied, not hoped.
P1s closed with product support in the write-up. The next person sees what already burned.
Grid/HA path, QA twin, filesystem, skill-up named. Executable without me in the building.
Outstanding demos, risks, topology that will hang. Phase 2 is not more of Phase 1.
Five teaching files, same author: xyz- PowerCenter Environment Summary.doc (MBFS + cheat sheet), xyz- PowerCenter Environment Summary (2).doc (NWM), xyz_Informatica_Upgrade_Roadmap_v3.doc (WR), Informatica_xyz_2_Summary - Copy.doc (Farmers Phase 2), PC_V10_Upgrade_Overview.pptx (28 slides). Named copies are the work. Hostnames stay off this copy.
A baseline that is allowed to be slow. A goal. One change between runs. Notes that make the next person dangerous. Thread statistics before folklore. Do not partition until a single partition is understood. The filesystem is often the real Grid/HA product.
Write to a flat file instead of the database. Filter FALSE immediately before the target. Compare to a stand-alone bulk loader. Faster = target-constrained.
Filter FALSE after the Source Qualifier. Read from a flat file instead of the database. FTP the remote file outside PowerCenter. Same speed = source-constrained.
Analyze table / runstats before optimizer hints. Source-only mapping to take transformation and target out of the experiment.
vmstat and sar. Low %idle = CPU. Non-zero si/so or page-outs = memory. Sustained %wio = disk. Notes: session time, rows/sec, config delta, CPU and disk.
ALFA→ODS at 100% CPU. Cache RAM raised so large transformations stop spilling to disk — 20–30% runtime drop. PWX CDC POC vs bulk load. GFS2 flock gap. Knowledge transfer walked ALFA→ODS, ODS→flat file, ODS→warehouse — not a PDF dump after the fact. Same loop as Local Grid Suite: baseline allowed to be slow, one change, notes the next FDE can run. Upgrade path →
Founding FDE translation: Agent latency, workflow duration, prior-auth cycle time, tok/s — same five steps. Measure before you add another agent. Do not change three prompts between runs.
The v10 overview is the coaching deck. The roadmap is the customer-specific evidence. Together they stop an account from “just running the installer.” Founding FDE: stop a fintech from “just turning on the agent.”
| When | Type | Why |
|---|---|---|
| Very short cycle, many installs already certified in a sandbox | In-place | No extra schemas. Users/groups stay. Outage for domain restore. Cannot change domain or node names. |
| Longer cycle, tight outage, want new names | Parallel | Fresh server + repo snapshot. No domain-install outage. Migrate users/groups. Small settings-drift risk. |
| Pre-prod go-live, minimize settings drift | Clone | Identical domain snapshot. Fast like-for-like. Still an outage. Cannot rename. Extra HTTPS caveats. |
Smoke: installer, domain start, repo wizard, services, connectivity, a workflow runs, client login.
Full, partial, or automated regression. Longest bar. DVO so you test all rows, not a sample. 50% S→T, 80% regression, 90% upgrade.
External: injection, SSL, DB grants, open ports. Internal: admin passwords, folder / connection / tool rights.
Client, integration service, server, network. Equal or better than legacy — with numbers.
Schedulers, SVN, deploy frameworks, encryption, file transfer, customer monitors. The item people skip.
HA = single-instance failover, uptime. DR = data-center loss, recovery time and stagnation.
“Customer satisfaction is worthless; customer loyalty is priceless.” — operating line · Gitomer / Carnegie / Greene. Talk given at Informatica while still on Dawn’s floor.
Founding FDE translation: In-place / parallel / clone = ship in their stack vs stand up a twin vs copy prod. Six-class test = operability of the agent, same outcomes, security/BAA, latency, 3rd-party systems, failover. Skill-up named in the close. Four floors →
QA/prod domains brought to best practice (ulimit 64k, DB2 repo settings, concurrent jobs 500, heap, stale NFS logs). P1 workflow-start delay: GCS escalation, DB2 semaphore on the Informatica client. Grid/HA TCO path and a QA twin of production. Artifact: PowerCenter Environment Summary.
ALFA→ODS at 100% CPU. Cache RAM raised so large transformations stop spilling to disk — 20–30% runtime drop. PWX CDC POC vs bulk load. GFS2 flock gap. Performance cheat sheet and load walkthroughs left with the team. Artifact: Environment Summary + cheat sheet.
2-node 9.1.0 grid measured for a month: 80–90% CPU, RAM under-used, disk wait 30–90 ms, SQL wait past 200 ms. UNC is not an HA filesystem. Upgrade types + six-class test plan. Adaptive dispatch, homogeneous nodes, Linux CFS. Artifact: Upgrade Roadmap v3.
Guidewire advanced XML and real-time consumers. 30+ repos / integration services as domain risk. NFS vs Veritas/GPFS. Skill-up named (Developer tool + Advanced XML). Outstanding demos: Operational Insight and Advanced XML on their schema. Team praised in the write-up. Artifact: Phase 2 Architecture Review.
Source artifacts: NWM / MBFS / WR / Farmers / PC 10 deck (Jeremy Panasuk, IPS). Navy Federal TDM-PHI masking Development Guide, TDM 9.5.2 HF1 (cover: Aditya Mohanty, IPS TDM Expert). Internal hostnames, credentials, and production table inventory are not published. Founding →
TabbyAPI EXL3, Ollama, Open WebUI, Compose + CUDA. Forced offload, VRAM pre-warm, failover. huggingface.co/jpanasuk/tabby-tavern-stack
Discover, bench, GPU routing, SQLite, CLI + PDF. Same loop as MBFS: measure before claiming.
Agents see Docker/network. Not host-root. Boundary, not the box — how you put an agent next to a bank or a clinic.
Production WhatsApp agents. Multi-provider routing with failover. Sits on the same Ollama runtime as the four-agent pipeline.
No-code builder inside Epic EHR, previewed HIMSS 2026, wider 2027. Chronicles remains source of truth; Cogito Cloud; Nebula routes models. I have not shipped an agent inside Chronicles. I have shipped agents with boundaries, customer workflows with unofficial definitions, and go-lives in regulated rooms. The founding FDE learns the customer’s platform on the customer’s floor. I will treat Agent Factory like Grid/HA: embed, measure, write the standard, leave a team that can shape the next one.
Every engagement opens with a metric and an Environment Summary. Every close has a skill-up name and a QA twin. No tribal knowledge.
Workflow templates, agent skill patterns, integration stubs, six-class tests. Recurring pain becomes the kit, not another hero week.
Automations that make the FDE function cheaper. I already build the tools I wish I had on night one. Then I leave them.
Field notes back to engineering weekly. If three customers hit the same wall, it is the next feature.
This PDF is the interview. The next FDE should run pages 7–9 without me in Slack. That is how a function is founded.
Hybrid 3 days onsite. I live in Sand Creek, WI. I will be in the room those three days. The customer is why.
Each agent is an isolated Python process with its own venv and tool loop. A crash or a bad script in one does not take the others down. They hand off Pydantic JSON, not free text. Orchestrated on the same 4070 that benches 1.39 → 37.47 tok/s.
Four processes. Four venvs. Dockroot-MCP so they see Docker/network, not host-root. That is how you put an agent next to a bank or a clinic without becoming the incident. Epic Agent Factory preferred — not claimed. I will take it like Grid/HA: embed, measure, write the standard.
Validator does not ship theater. It retries until the schema passes. Volkswagen watched Grid/HA run on their RAC a day early. Unnamed watched PC/DQ run on their metal. Founding FDE: the night operator can still run Tuesday, or I did not finish.
Jeremy Panasuk · Sand Creek, WI · 715-970-0204 · jpanasuk@gmail.com
linkedin.com/in/jeremy-p-34203322 · github.com/jpanasuk-netizen · huggingface.co/jpanasuk
Carex Consulting Group · Job 6273 · Founding Forward Deployed Engineer
Madison, WI · hybrid 3 days · Direct hire · fintech startup partner
carexconsulting.com/jobs/founding-forward-deployed-engineer-6273/