Skip to main content

HPR

Applications Engineer II

Needham, MA$90k–$135.1kmidAdded today

About this role

HPR, a leading provider of ultra-low latency trading infrastructure, seeks an Applications Engineer II to deliver technical support and solutions for tier-1 financial institutions. You'll troubleshoot complex problems, develop customer training, and collaborate with engineering teams to drive best practices and product improvements.

What you'll do

  • Develop expert-level technical competence across HPR's product portfolio
  • Resolve technically complex problems for major financial institution clients
  • Interface with customers via phone, email, and web to provide world-class support
  • Develop and deliver customer training and educational content
  • Drive best practices and lessons learned from customer interactions back to product development
  • Collaborate with engineering teams to expedite problem resolution

What they're looking for

  • Linux systems administration
  • Python and Shell scripting
  • Networking technologies (TCP, switch configuration, routing)
  • Troubleshooting and problem-solving
  • Technical communication and customer service
  • C programming (desired)
  • Jira and Confluence (desired)
  • Business-critical application support
Apply with Autofill

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.

HPR

HPR builds ultra-low latency trading infrastructure for tier-1 financial institutions, providing high-performance systems for electronic trading platforms. The company is hiring Software Engineers and FPGA Design Engineers to develop and optimize core trading systems, network infrastructure, and custom compute solutions.

View all jobs at HPR

Likely interview questions

  • Describe your experience supporting business-critical applications. What was the most complex issue you resolved and how did you approach it?
  • Tell us about a time you had to communicate a technically complex concept to a non-technical customer. How did you ensure they understood?