logo
HireVue Product Documentation

 

Effective Feb 1, 2025 
Version: 2.0

     
      T2O Technical Specifications

 

Overview

HireVue's Talent to Opportunity (T2O) platform is designed to meet the unique challenges of talent acquisition, such as scheduling, interviewing, and assessing a candidate. In addition to a core set of common services hosted on core application servers, each component utilizes unique services hosted on its own set of servers. HireVue's Professional Services Consultant coordinates with each customer’s network and security team to identify which regional servers are referenced when using the T2O platform.



General application requirements

 

Browser requirements and compatibility

HireVue's Next Generation is a 100% SaaS application that supports the following browser versions:

    • Chrome: Current version -1, JavaScript enabled

      • Not supported on iOS

    • Firefox: Current version -1, JavaScript enabled

    • Edge: Current version -1, JavaScript enabled

    • Safari: Current version -1, JavaScript enabled

 


 

Minimum computer recommendations

    • Windows 10/8, MAC OSX+ or Linux with 1.2GHz (or faster) processor & minimum memory required by O/S

    • Webcam (for video recording only)

    • Speakers or headphones (for audio based questions)

    • Keyboard (for typing based assessments)

    • Microphone (for audio recording only)



Recommended internet connection

HireVue recommends using the HireVue's Next Generation SaaS solution T2O with Internet connection speeds of 3Mbps (minimum).



IP addresses and ports

This section describes the specific sets of IP addresses and ports required in support of each service.

 

Core application IP addresses and port(s) - outgoing connections

All clients must enable outgoing connections to HireVue’s core application servers. The HireVue core application includes the web application supporting recruiters’ activities related to job and candidate management, ordering on-demand interviews and scheduling live interviews, many of which generate system emails to interview participants. HireVue’s core application servers perform those activities.

 

Server description

IP address/ domain

Outgoing port (s)


HireVue Applications

(http & https)



*.hirevue-app.com (All Clients)

*.uat.hirevue-app.com (All Clients)

*.hirevue-app.eu (EMEA Clients)

*.hirevue-app.com.au (APAC Clients)

*.hvue.io

80, 443

Required for all HireVue applications

54.79.162.150 (APAC)

 

52.21.220.221 (US)

 

34.242.85.194 (EU)

 

54.176.75.170 (Disaster Recovery)

 
 

34.225.125.241 (Disaster Recovery)

 
 

52.45.52.6 (Disaster Recovery)

 
 

3.24.191.61 (Disaster Recovery)

52.48.239.14 (Disaster Recovery)

 

 

Server description

IP address/ domain

Outgoing port (s)

Email Servers

54.240.44.212 (US)

25, 465, or 587

 

54.240.44.213 (US)

 
 

69.169.235.54 (AU)

 
 

69.169.235.55 (AU)

 
 

54.240.88.96 (EU)

 
 

54.240.88.97 (EU)

 

Outgoing Email Addresses


noreply@mail.modernhire.com

noreply@mail.uat.modernhire.com

noreply@mail.modernhire.com.au

noreply@mail.modernhire.eu

noreply@mail.hirevue-app.com noreply@mail.uat.hirevue-app.com noreply@mail.hirevue-app.com.au noreply@mail.hirevue-app.eu

 

SPF Domain

smtp-out.mail.hirevue-app.com smtp-out.mail.uat.hirevue-app.com smtp-out.mail.hirevue-app.eu

smtp-out.mail.hirevue-app.com.au

 

DKIM Signing Domains


mail.hirevue-app.com 

mail.uat.hirevue-app.com 

mail.hirevue-app.eu 

mail.hirevue-app.com.au


amazonses.com

 

HireVue supports and highly recommends allowing of domain names (*.hirevue-app.com, *.hirevue-app.eu, *.hirevue-app.com.au, and *uat.hirevue-app.com) and does not recommend allowing of IP addresses. The HireVue application automatically provisions new servers in response to usage spikes with frequent changes to IP addresses.

Please understand that by allowing IP addresses, HireVue will no longer remain reliable, scalable and elastic for your company. Any IP address discovered through network analysis may change at any time and should not be used in an attempt to allow IP addresses. Your HireVue Professional Services Consultant and/or Client Success Manager is available to work with your network teams to ensure reliable connectivity to HireVue servers.

 

 

On-Demand Video IP address & port(s) - outgoing connections

HireVue has a dedicated set of servers for recording and playback of videos. For those clients only using HireVue's on-demand video platform, HireVue uses servers at the following IP address ranges for playback of video. HireVue delivers playback via port 443 (https). Clients will also be required to open ports 80, 443, and if your talent acquisition team requires recording of on- demand videos or job related videos inside their corporate network.

 

Server description

IP address/ domain

Outgoing port(s)

HireVue on-demand playback video server(s)

*.hirevue-app.com (All Clients)

*.uat.hirevue-app.com (All Clients)

*.hirevue-app.eu (EMEA Clients)

*.hirevue-app.com.au (APAC Clients)

s3.amazonaws.com

cdn.dev.mhire.io

cdn.test.mhire.io

cdn.uat.modernhire.com

cdn.modernhire.com

cdn.modernhire.eu

cdn.modernhire.com.au

80, 443 (for playback)

 

54.79.162.150 (APAC)

 
 

52.21.220.221 (US)

 
 

34.242.85.194 (EU)

 
 

54.176.75.170 (Disaster Recovery)

 
 

34.225.125.241 (Disaster Recovery)

 
 

52.45.52.6 (Disaster Recovery)

 
 

3.24.191.61 (Disaster Recovery)

 
 

52.48.239.14 (Disaster Recovery)

 

HireVue on-demand recording servers

*hirevue-app.com

*.modernhire.com

*.modernhire.eu

*.modernhire.com.au

*.uat.modernhire.com

*.test.mhire.io

*.dev.mhire.io

80, 443 & (for recording)




 

Live Video platform IP address & port(s) - outgoing connections only

The following table documents the domains and ports required by HireVue’s WebRTC live video servers. UDP port 3478 is the preferred communication port to the WebRTC live video platform.

However, if UDP port 3478 is not available, media communication utilizes TCP port 443. For an optimal video experience, clients must allow outgoing connections (UDP/3478) and configure network appliances to minimize latencies with the client to server communication for the live interview servers.

HireVue live video browser client software uses regular HTTPS and WebSocket connections to the signaling servers via the Internet on port TCP/443. If the only way to access the Internet from your network is through a proxy, then it must be a transparent proxy or configured in the browser for HTTPS connections. Ensure TCP/443 is open for outgoing connections to the domains identified. The minimum requirement is that outgoing TCP port 443 is open. Some default firewall/ proxy rules only allow for SSL traffic over port 443. You will need to configure firewall and proxy rules so non-web traffic (non-https) can also pass over this port. Also, WebRTC signally traffic requires a persistent WebSocket connection and a load-balanced proxy server configuration must accommodate a persistent connection.

Although HireVue live video client software can use UDP or TCP connections for media, we highly recommended enabling UDP to improve the quality of the real-time audio and video communications. In the case of UDP, the browser client requires connectivity from the browser to the media servers via the Internet on port UDP/3478. The browser client initiates the connection from inside the corporate network, and there are no connections initiated from outside the corporate network.

 

Server Description

IP Address/Domain

Outgoing Port(s)

HireVue Live Interview Video Server(s) 


Only required for Live Video Interview 



Important: HireVue does not recommend the allowing of IP addresses.The HireVue application automatically provisions new servers in response to usage spikes with frequent changes and IP addresses. 


Please understand that by allowing IP addresses, HireVue will no longer remain reliable, scalable and elastic for your company. 



 Any IP address discovered  

 through network analysis may 

 change at any time and should  

 not be used in an attempt to 

 allow IP addresses. 

  *.tokbox.com, *opentok.com & *.vonage.com 

  (for all ports) 





54.69.125.241/32 

74.201.205.0/25 

72.251.224.0/25 

72.251.228.0/25 

95.172.84.0/25 

117.20.41.128/25 

52.41.63.240/28 

52.200.60.16/28 

52.51.63.16/28 

54.250.250.208/28 52.65.127.192/27 

52.66.255.192/27 

54.89.253.64/28 


35.158.127.224/28 34.218.216.144/28 

13.251.158.0/28 

52.213.63.176/28

99.80.88.240/28 

3.123.12.128/28 

34.223.51.192/27 

34.223.51.224/27 

3.214.145.96/27 

3.23.232.160/27 

34.222.66.96/28 

99.79.160.16/28 

18.202.216.0/28 

18.139.118.176/28 

3.248.234.48/28 44.232.236.96/27 

3.127.48.224/28 

3.248.243.144/28

3.234.248.80/28 

3.248.244.96/27 

18.156.18.0/27 

18.180.159.224/27 18.141.165.128/27 

3.7.161.0/26 

3.7.161.48/28 

18.179.48.208/28 

3.25.48.192/28 

18.157.71.112/28 

3.235.255.176/28 

44.234.90.64/28 

15.228.1.16/28 

168.100.64.0/18

TCP/443 & UDP/3478 

optional but preferred

 

For Chrome and Firefox only: The link https://tokbox.com/developer/tools/precall/ tests and verifies network accessibility to the servers required to participate in the WebRTC interview and/or meeting and the ability to send non-web traffic via TCP over port 443. Reporting which diagnostics pass or fail will help your HireVue Client Success Manager diagnose connectivity issues.

 

Reporting the video and audio bandwidth and packet loss will help your HireVue Client Success Manager diagnose connectivity issues.

 

Live interview soft phone browser client

The soft phone is not required for on-demand voice or on-demand video interviewing. It is an optional component for both HireVue live video and HireVue live voice interviews.

Typically, clients use their office telephones when working at their place of business. Some users elect to use the HireVue soft phone within the HireVue application in lieu of their business phone.

For those clients planning use of the soft phone inside their corporate network for either live video interview or live voice interview, your firewall should allow outgoing UDP ports 10,000 - 20,000 to the public internet from the browsers that will be using soft phone client and allow return traffic in response. Due to the dynamic nature of phone Amazon AWS cloud platform, we strongly recommend that you not limit this access to a specific range of IP addresses

 

 

Bandwidth Usage

       On-demand video and voice

 

Reviewing an on-demand video

The typical on-demand video response is approximately 1 minute and ranges from 1.5 to 2 MBs in size. The video player will buffer ahead so bandwidth demand will be higher during the initial viewing of the video. On average, on-demand playback uses approximately 150 - 200 kbps to maintain smooth video flow without any pauses or delays. With unlimited bandwidth and monitoring the network, clients will see a few seconds of high bandwidth usage and then minimal bandwidth consumption for the remainder of the minute. The video player will be very tolerant of any throttling imposed on incoming video streaming, but the live video experience will not.

Recording an on-demand video

Recording uses local buffering since candidates may have less than reliable connections, so we tolerate some bandwidth limitations during recording. With a good network connection combined with HireVue’s standard resolution and frame rate, clients typically see an average rate of approximately 160 kbps. Again, this assumes a relatively stable image. There are examples of people sitting in front of a window with a lot of background activity and bandwidth usage will jump to 400 kbps, but that is highly unusual. Demand for recording within a client’s corporate network is very low, so HireVue does not consider usage for recording a potential high bandwidth, client network consumer.

Reviewing an on-demand voice

The typical on-demand voice response is 1 minute long and averages approximately 250 KBs in size. The audio player will buffer ahead so bandwidth demand will be higher during the first few seconds of playback. On average, on-demand playback uses approximately 10 - 20 kbps to maintain smooth video flow without any pauses or delays. With unlimited bandwidth, clients monitoring their network will see a less than a second of high bandwidth usage and then minimal bandwidth consumption for the remainder of the minute. The player will be very tolerant of any throttling imposed on incoming audio.

 

 

Live interview bandwidth usage

HireVue’s live video WebRTC application delivers a highly interactive video experience between interview participants while minimizing load on our client’s corporate network and responding appropriately to candidate connectivity worst-case scenarios. The following graph demonstrates the expected bandwidth usage for an interview based on the number of participants. HireVue’s live video interview platform uses compression to minimize traffic and the actual bandwidth can vary slightly over the course of an interview session.




A graph of a number of peopleDescription automatically generated





Live interview quality of service (QoS) for live video interview

HireVue recommends clients implement a QoS policy for both incoming and outgoing traffic to its live video interview servers prioritizing the live interview network traffic higher than the default Best Effort priority (AF41 preferred). Clients can estimate approximate incoming and outgoing bandwidth QoS policies using the following equations. Assume each participant generates approximately 240 kbps.

 

Outgoing traffic estimates

 

    • NI = Number of simultaneous interviews

    • NLP = Number of participants connected to the local network

    • Total Outgoing Traffic = NI * NLP * 240 Kbps

 

For example, assume your HR department is planning on panel interviews with two hiring managers in the local office, a hiring manager at another facility and a candidate. The HR department believes there will be at most 6 simultaneous interviews at any point in time.

    • NI = 6

    • NLP = 2

    • Total Outgoing Traffic = 6 * 2 * 240 kbps = 2,880 Kbps

Incoming traffic estimates

    • NI = Number of simultaneous interviews

    • NLP = Number of participants connection to the local network

    • NP = Number of total participants in an interview

    • Total Incoming traffic = NI * ((NP * NLP) – NLP) * 240 Kbps 



Using the preceding example:

    • NI = 6

    • NLP = 2

    • NP = 4

    • Total Incoming Traffic = 6 * ((4*2)-2) * 240 Kbps = 8,640 Kbps