> ## Content Index
> Fetch the complete content index at: https://wire.fourthweb.ai/llms.txt
> Use this file to discover other available public pages before exploring further.

# Engineers Are Writing the Code. Lobbyists Are Writing the Laws.
- URL: https://wire.fourthweb.ai/engineers-are-writing-the-code-lobbyists-are-writing-the-laws/
- Published: 2026-10-22T15:31:05.000Z
- Updated: 2026-10-22T15:31:07.000Z
- Description: The people who build the technology shaping policy aren't in the room when those policies get written — and that's a problem Congressional staffers actually want to solve.
- Author: Travis Wright
- Tags: AI Agent Economy, AI Agents, AI Infrastructure, Compute Wars, AI Governance, Tokenized Assets, Institutional Crypto, Smart Contracts, IPO Watch

**The people who build the technology shaping policy aren't in the room when those policies get written — and that's a problem Congressional staffers actually want to solve.**

### The Summary

- Software engineer Nikhil Jathar went from "wow, I get to visit Congress" to understanding why [engineers need to show up on Capitol Hill](https://spectrum.ieee.org/engineers-lobbying-congress?ref=wire.fourthweb.ai) — not just for photo ops, but to shape the policy that shapes their work
- Congressional staffers say they actively want technical expertise from engineers, but most engineers never engage with the legislative process
- IEEE-USA runs annual Congressional Visits Days to train engineers on lobbying — with clear playbooks on what to ask for (bill cosponsorship, appropriations language, agency oversight)

### The Signal

Nikhil Jathar, CTO of business software company AvanSaber, went to Washington in spring 2025 to advocate for tech education funding. He didn't have a company agenda. He went because [the invitation from IEEE-USA](https://spectrum.ieee.org/engineers-lobbying-congress?ref=wire.fourthweb.ai) made him curious about how policy actually gets made.

What he found: staffers desperately want what engineers have — domain knowledge about how technology actually works. A staffer for the House Committee on Science, Space, and Technology told IEEE Spectrum that policy ideas come from legislators, constituents, and industry, but it's staff who figure out what would "do the most good." That calculation gets harder when the people doing the building aren't in the conversation.

> "Ideas for new policies come from multiple places... It's up to us to figure out what would do the most good."

The gap is obvious in AI regulation debates. Congress is writing rules for agent systems, model training, and algorithmic accountability — but the engineers who understand training data provenance, inference costs, and deployment risk often aren't at the table. That leaves policy shaped by executives who pitch and lobbyists who spin, not builders who know where the system breaks.

IEEE-USA's Congressional Visits Day teaches engineers the mechanics: how to ask for bill cosponsorship, modify legislative text, add language to appropriations, or request agency oversight. These aren't abstract civics lessons. They're the actual levers that determine whether AI safety research gets funded, whether crypto custody rules make technical sense, or whether export controls on chips account for how supply chains actually work.

**Key asks engineers can make:**

- Cosponsor or oppose specific bills or amendments
- Modify language in active legislation
- Add provisions to appropriations bills
- Request GAO reviews, hearings, or stakeholder roundtables

The absence of engineers in policy discussions shows up in bad regulation. When lawmakers don't understand the difference between open-source model weights and proprietary APIs, they write rules that treat them the same. When they don't grasp how tokenization of [real-world assets](https://wire.fourthweb.ai/tag/tokenized-assets/) actually settles, they create compliance frameworks that make the whole category unworkable in the U.S.

### The Implication

If you're building agents, deploying models, or tokenizing assets, the policy being written right now will determine whether your work is legal, fundable, or possible in five years. Congressional staffers aren't the enemy — they're often the only people in the room trying to understand the tech. But they can't do it without you.

IEEE-USA's Congressional Visits Day is one entry point, but the broader lesson is simpler: show up. Write your representative about a bill that would break your product. Offer to brief staffers on how a proposed rule would actually play out. The alternative is policy written by people who've never deployed a model, never written a [smart contract](https://wire.fourthweb.ai/tag/smart-contracts/), and never had to explain to a user why the system didn't work the way they expected.

Engineers like to complain that regulators don't understand technology. Fair. But if the people who do understand it won't show up to explain it, that complaint rings hollow.

### Sources

[IEEE Spectrum AI](https://spectrum.ieee.org/engineers-lobbying-congress?ref=wire.fourthweb.ai)