Virtu Financial
2027 Internship- Hardware Engineer (FPGA)
About this role
Virtu Financial seeks FPGA hardware engineering interns for a 10-week summer program (June–August 2027) in Austin. You'll work on real ultra-low latency trading infrastructure projects, progressing from architecture through RTL implementation to hardware verification under the mentorship of senior engineers.
What you'll do
- Design and implement FPGA solutions using SystemVerilog/Verilog across the full hardware lifecycle
- Develop RTL code for ultra-low latency trading systems and market-making infrastructure
- Conduct simulation and verification of hardware designs before silicon bring-up
- Collaborate with senior mentors to solve real engineering problems in the trading stack
- Participate in hardware bring-up and testing on live systems
- Contribute to architecture and design decisions for competitive trading systems
What they're looking for
- SystemVerilog or Verilog
- FPGA design and implementation
- Python or C++
- Hardware simulation and verification
- Network protocols
- Problem-solving and debugging
- RTL design
- Communication and collaboration
Benefits
- Onsite gym and workout classes
- Onsite barista
- Weekly happy hours and social events
- Complimentary breakfast and lunch
- Transportation provided
- Mentorship from experienced senior engineers
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Virtu Financial
Virtu Financial builds high-performance trading platforms and infrastructure for financial markets, serving traders and clients with advanced systems for data management, execution, and analysis. The company is hiring Systems Engineers, Software Engineers, and Frontend Engineers to develop and optimize trading tools, platforms, and reference data systems across JavaScript, React, Java, C#, and backend technologies.
- Website
- virtu.com
Likely interview questions
- Walk us through a Verilog or SystemVerilog project you've built—what were the main challenges and how did you debug timing issues?
- How would you approach optimizing a hardware design for ultra-low latency, and what trade-offs would you consider?