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. At the time, he did not have a specific lobbying position on behalf of the company. But he was intrigued by the invitation—which goes out to all U.S. IEEE members—and as he read more about congressional visits, his motivation deepened. He realized: “I need to try this. I want to see where it goes.”
Congressional staffers say they welcome the knowledge and perspective that engineers like Jathar and other visitors from beyond Washington, D.C., provide. It’s also important for those visitors to be clear on what they are advocating for. One staffer for the House Committee on Science, Space, and Technology, who agreed to speak anonymously due to the office’s media policy, says, “Ideas for new policies come from multiple places. It could begin at the [legislator] or staff level, an ask from a constituent, or needs from industry. It’s up to us to figure out what would do the most good,” the staffer said. “For instance, if you leave it to the lobbyists, they’re understandably going to do what’s in their clients’ interests.”
For engineers in the United States, speaking with elected representatives is an effective way to shape key policies, but it takes some preparation and the right approach, as Jathar learned over the course of two visits.
Mapping Your Way Into Washington
Congress’s job is to act on behalf of the people, and it has rules for how people can lobby it. It distinguishes between broader advocacy—conversations between constituents and U.S. representatives—and professional lobbying, which involves paid professionals and is governed by the Lobbying Disclosure Act. Many professional groups like IEEE also organize congressional visits for their members. Those visits can be subject to lobbying rules, so the organizers told Jathar that: “You are representing the organization, not your own views.” He would need to stick to the talking points IEEE-USA had prepared for all its participants, regardless of their specialty, to promote across several congressional offices.
On Jathar’s first visit, those organizational talking points included advocating for funding smart grids, authorizing Department of Energy research, and investing in STEM education. That represents one of the trade-offs of access in Washington. IEEE-USA’s priorities didn’t all overlap directly with Jathar’s work, but they were broad enablers of science and technology and, he says, “STEM education funding is close to my heart.”
Anyone can approach their representatives in Washington with their personal priorities, Jathar notes, but given how pressed for time congressional staff are, they are more likely to prioritize a meeting that represents the views of as many of their constituents as possible. “I could have gone outside the IEEE structure,” Jathar says, but congressional staff “are more likely to listen if you are part of a much bigger organization.”
For Jathar’s first congressional visit, organizers assigned him to call on the offices of several representatives from both political parties based on where he lives: Representatives Greg Casar (D-Texas), Lloyd Doggett (D-Texas), and Barry Moore (R-Ala.). “Meeting a staffer or a senior member from their office is good. They tend to relate to these issues more than a representative, because a representative has 10 different high-level things they have to worry about whereas the staffer can be more focused on the policy details,” Jathar says.
A typical visit like this may last anywhere from 15 minutes to an hour, so Jathar kept his talking points simple and short. “First and foremost you’re gonna get a very small window,” he says, “Make sure you’ve got everything ready to present in bullet points and not a lot of jargon. You can always bring that out later if they ask more questions.” Simple visual aids, in the form of one-page handouts, may be helpful for communicating numeric or technical information, too.
“If you leave it to the lobbyists, they’re understandably going to do what’s in their clients’ interests.”–Staffer for the House Committee on Science, Space, and Technology
The House Science Committee staffer agrees: “I prefer meetings where people know what they want and know what we’re doing in Congress.” In addition to having a clear request, the staffer says engineers and other advocates should keep track of where Congress is in its cycle: Is it appropriations season, and when is the next budget being set? How far along is a given piece of legislation in the process, and what is realistic to change at that point?
During Jathar’s 2025 visit to one Capitol Hill office, he learned firsthand the importance of preparation. For one of the three representatives he visited, staff politely pointed out that the legislator they worked for was not on the committee with jurisdiction over the IEEE-USA talking point they were discussing. “They explained that there are only certain things [the legislator] can do on that issue and that there are other people we need to talk to, to achieve more,” Jathar recalls.
Shortcuts to Influence
Earlier this year, Jathar decided to go back to Capitol Hill with his newfound knowledge, again within the framework of an IEEE-USA visit. This time he was able to provide something else legislative staff want from engineers: authoritative technical knowledge.
“When I introduced myself as a software developer to one staffer, his first question was, ‘Do you think AI will replace coders?’ ” Jathar says. The conversation went back and forth, with the staffer asking Jathar and his other engineering companions questions. Jathar went on to explain that his company developed an open-source business-management software it calls ERPClaw, designed to be used with AI agents such as OpenClaw. That led naturally to discussing the role of open source in AI, which plays a role in one of IEEE-USA’s proposals for democratizing AI. This time Jathar was able to align his organization’s advocacy with his expertise and the staffer’s areas of interest.
It’s too soon to know what legislative impact that advocacy might have, but it’s the sort of informed, relevant proposal that legislative staff seek out. “The people who build trust have more cachet with congressional staff because they’ve asked for something that’s reasonably thought out,” the House Science Committee staffer says. In turn, congressional staffers can advocate better within their offices for policies brought to them by people they trust.
And talking about the issues you care the most about can deepen that trust. The House Science Committee staffer once visited Congress as an advocate before switching to the other side of the table. On that visit, as on Jathar’s, the professional society organizing the visit provided a pitch. “I was making a pitch that was given to me without a lot of personal buy-in,” the staffer says. Instead, “you should feel emotionally connected to any issue you’re advocating for.”
Jathar’s support for the open-source movement is like that. Open source gives smaller companies a foundation they can adapt and build upon, while allowing other developers to extend that work. “We can progress a lot faster,” Jathar says. “I’m not doing it only because it’s good for my business, but because I feel it’s good for any technological advancement.”
From Your Site Articles
Related Articles Around the Web
