Why Engineers Should Brave Capitol Hill

If you spend your time building in crypto or AI, you probably view Washington, D.C. as a slow-moving obstacle at best or a direct threat at worst. Most of us prefer the clean logic of code over the messy, transactional nature of policy. But as Nikhil Jathar, CTO of AvanSaber, recently discovered, staying in the lab while others dictate the rules of the game is a losing strategy.

Jathar, an engineer who moved to the U.S. from India, recently made the trek to Capitol Hill as part of an IEEE-USA delegation. His experience offers a masterclass in how builders should approach the legislative process. It turns out that while we think we are speaking a different language, the people in those marble offices are actually starving for someone who knows how things actually work under the hood.

The Vacuum of Expertise

There is a massive gap between the people writing the rules and the people building the future. A staffer for the House Committee on Science, Space, and Technology put it bluntly: if engineers don't show up, the only voices left in the room are professional lobbyists. Lobbyists aren't there to explain how a large language model works or why open-source licensing matters; they are there to protect their clients’ bottom lines.

When Jathar first arrived in D.C. in early 2025, he wasn't there as a paid shill. He was there as a constituent and a practitioner. That distinction matters. Congressional staffers—the people who actually do the heavy lifting on policy—are often younger, overworked, and desperate for technical clarity. They want to know what happens if they regulate a specific API or how a new funding bill for STEM might impact a small software shop in Texas.

Stop Pitching, Start Translating

One of the biggest mistakes founders make when talking to the government is treating it like a VC pitch. You aren't there to sell your company; you’re there to explain the ecosystem. Jathar found that his value increased exponentially when he stopped just reciting talking points and started answering fundamental questions.

During his second visit, a staffer asked him a question every developer hears: "Do you think AI will replace coders?" That’s a gateway question. It allowed Jathar to bridge the gap between abstract policy and the reality of his work on ERPClaw, an open-source business management tool. By explaining how AI agents interact with open-source code, he wasn't just talking shop—he was providing the raw data staffers need to craft sensible regulations.

The Practical Logistics of Power

If you're going to take the flight to D.C., you need to understand the mechanics of the building. Jathar’s experience highlights a few hard truths for builders:

• The Staffer is the Key: You might want to meet the Representative, but the staffer is the one who actually understands the tech. They have the time to go deep on the details that their boss will only see in a one-page summary.
• Watch the Clock: You usually get 15 to 20 minutes. If you spend 10 of those on your life story, you've failed. Use bullet points. Bring a one-page handout that looks like a technical spec, not a marketing brochure.
• Jurisdiction Matters: Don't pitch a privacy bill to a staffer whose boss sits on the Agriculture Committee. Knowing who has the power to actually move the needle on your specific issue is half the battle.

The Open Source Argument

For those of us in the builder community, Jathar’s focus on open source is the most relevant takeaway. In D.C., "open source" is often a misunderstood term. Some see it as a security risk; others see it as a hobby. Jathar argued that open source is a foundation for fast-paced innovation, allowing small companies to compete with giants by building on shared infrastructure.

This is where the founder’s perspective is vital. A lobbyist for a tech giant might argue for "safety" regulations that effectively kill open-source competition. An engineer can explain why that actually hurts the national interest by stifling the very developers who drive the economy. When Jathar spoke about open source, he wasn't just doing it for his business; he was doing it for the advancement of the field.

Why Builders Must Engage

The skeptical view is that D.C. is a swamp where nothing gets done. While there’s truth to that, ignoring it is a luxury we no longer have. Whether it’s crypto regulation, AI safety, or R&D tax credits, the rules are being written now. If we aren't at the table, we are on the menu.

Jathar’s journey from a hesitant software engineer to a trusted technical resource for congressional offices shows that there is a path forward. It doesn't require a million-dollar PAC or a fleet of lobbyists. It requires showing up, speaking clearly, and being the person who can explain the code to the people writing the laws.

The Takeaway for Founders

Your technical expertise is a form of political capital. Most people in Washington don't know the difference between a blockchain and a database, or a transformer and a simple algorithm. If you can provide that clarity without the hype, you build trust. And in a town built on transactions, trust is the most valuable currency there is. Don't wait for the regulations to break your business—go tell them why they shouldn't break it in the first place.

---

Read the original at IEEE Spectrum →