AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Why Engineers Should Brave Capitol Hill

Collected Oct 22, 2026

Nikhil Jathar, a San Antonio–based software engineer and CTO of AvanSaber, a business software company he cofounded in 2014, went to Washington, D.C., in spring of 2025 to advocate for federal support for technology education and research funding. He had been invited to join the annual Congressional Visits Day organized by IEEE-USA, an invitation that goes out to all U.S. IEEE members. Jathar, who had recently settled in the United States from India, had no specific lobbying position on behalf of his company at the time. He returned to Capitol Hill earlier this year for a second round of visits, again within the IEEE-USA framework. His account, published by IEEE Spectrum, doubles as a practical guide to how engineers can engage legislators.

The first lesson is that staffers want a specific request. Common asks include cosponsoring or opposing an existing bill or amendment, preserving, removing or modifying legislative text, adding language to an appropriations bill or committee report, posing an oversight question to a federal agency, requesting a briefing, hearing, Government Accountability Office review or stakeholder roundtable, or pressing an agency to clarify a technical rule. A staffer for the House Committee on Science, Space, and Technology, speaking anonymously under the office's media policy, said ideas for policy can start with a legislator, staff, a constituent request or industry need, and that staff weigh what would do the most good. The staffer added that lobbyists left to their own devices will understandably pursue their clients' interests.

Congress distinguishes between broader constituent advocacy and professional lobbying, the latter involving paid professionals and governed by the Lobbying Disclosure Act. Professional societies such as IEEE organize visits that can fall under lobbying rules, so organizers told Jathar he was representing the organization rather than his own views and would need to stick to the talking points IEEE-USA prepared for all participants regardless of specialty. On his first visit those points covered funding smart grids, authorizing Department of Energy research and investing in STEM education. Jathar says STEM education funding is close to his heart, even though the priorities did not all map directly onto his own work.

There is a trade-off here that developers weighing similar trips should recognize: joining a large group buys credibility and access, but it dilutes individual focus. Jathar notes anyone can approach representatives with personal priorities, yet staff pressed for time are more likely to take a meeting that reflects the views of many constituents. He says staff are more likely to listen to someone speaking as part of a much bigger organization.

Organizers assigned Jathar, based on where he lives, to the offices of Representatives Greg Casar (D-Texas), Lloyd Doggett (D-Texas) and Barry Moore (R-Ala.) — a mix of both parties. He found staffers or senior office members more engaged on policy detail than representatives themselves, reasoning that a representative juggles many high-level concerns while a staffer can concentrate on specifics. Visits typically run 15 minutes to an hour, so he kept his points short and jargon-free, with bullet points ready and a one-page handout for numeric or technical material, holding detail in reserve for follow-up questions.

The House Science Committee staffer echoed the need for clarity, saying the best meetings are with people who know what they want and know where Congress stands. That means tracking the legislative calendar: whether it is appropriations season, when the next budget is set, how far a bill has progressed and what is realistic to change at that stage. Jathar learned the jurisdictional point firsthand in 2025, when one office politely explained that the legislator did not sit on the committee with authority over the IEEE-USA talking point under discussion, and that other offices would need to be approached.

On his second visit, Jathar brought something else staff value: authoritative technical knowledge. When he introduced himself as a software developer, one staffer asked whether AI would replace coders, and the conversation turned into a back-and-forth with Jathar and his fellow engineers. He described ERPClaw, his company's open-source business-management software built for use with AI agents such as OpenClaw, which led into a discussion of open source's role in AI — a theme in one of IEEE-USA's proposals for democratizing AI. That let him align the organization's advocacy with his own expertise and the staffer's interests.

The staffer said it is too early to judge the legislative impact, but described this as the kind of informed, relevant proposal offices seek out, adding that people who build trust carry more weight because they have asked for something reasonably thought out. Trusted advocates, in turn, help staff make the case internally. The staffer, who once lobbied Congress as a visitor before moving to the staff side, recalled delivering a professional society's pitch without much personal buy-in, and advised feeling emotionally connected to whatever issue one advocates. Jathar's open-source commitment fits that mold: he argues open source gives smaller companies a foundation to adapt and build on while letting other developers extend the work, so progress comes faster. In his view the motivation is not only business benefit but broader technological advancement.

For developers and product teams, the practical takeaway is that policy engagement is a learnable skill rather than a lobbying insider's game. In my reading, the biggest lever for a technical person is not a polished pitch but being the person who can explain how a rule would actually affect code, models or infrastructure — the kind of context staff rarely get from clients' representatives. The trade-offs are real: group visits constrain the message, offices differ in what they can act on, and results are slow and hard to attribute. But constituent visits are free, open to members of professional societies, and meetings run under an hour, which makes the barrier to entry lower than many engineers assume. Why it matters: engineers whose products touch AI, open source or research funding are increasingly the subject of legislation they had no hand in shaping, and staffers explicitly say they want technical input. Developers who prepare a concrete ask and show up as part of an organized group can influence which questions get asked and which technical nuances reach the people writing the rules, though the source offers no evidence yet of enacted change from these particular visits.

Read at IEEE Spectrum · AI

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

When San Antonio–based software engineer Nikhil Jathar first went to Washington, D.C., to advocate for federal support for technology education and research funding, he was in awe of the opportunity. It was spring of 2025, not long after Jathar settled in the United States from India, when he got an invitation to join the annual Congressional Visits Day organized by IEEE-USA . “My first reaction was, ‘Wow, I get to visit Congress,’ ” says Jathar, CTO of AvanSaber , a business software company he cofounded in 2014.