employer cover photo
employer logo
employer logo

Vehicle History

Is this your company?

Productive and Challenging (in a good way) - Content Director Vehicle History Employee Review

5.0
3 Feb 2021
Recommend
CEO approval
Business outlook

Pros

Progressive leave policy, top of market pay, energetic team, transitioning to agile framework, transparency

Cons

Fast-paced (sometimes overwhelming), the transition to agile is sometimes bumpy but getting better

Explore other reviews about Vehicle History

5.0
30 Jun 2021
Recommend
CEO approval
Business outlook

Pros

A dynamic and empowering working environment, employees have autonomy and trust. The perks are great.

Cons

Fringe benefits could use some tweaking to be in line with competition.

4.0
18 Mar 2018
Recommend
CEO approval
Business outlook

Pros

The whole team and I have fun working on the projects with each other. We get to work with a lot of the latest technology and we try to keep updated so we can use the new toys coming out to PHP, and JS. This is a big plus to me since I dont have to play with the new stuff and wait for it for years to come down the corporate line. We just discuss with the team and move on to the new version as long as there are no major breaking changes. We also work on a lot of interesting and challenging projects. Also the company is growing and is way different then when I first started 7 months ago. We have some of the best talent in Las Vegas. I have learned a lot from the people I work with and I feel they learn from me as well. There is a lot to gain when working for Vehicle History.

Cons

We are an automotive industry company which means we have to deal with automotive vendor API's. The biggest con to my day to day work is dealing with these API's because they have no standards in the automotive world. So a make, model, and year to one vendor might not work with another vendor because they add trim or body style to the model. Some put the body style on the model only for some years. Although as a company there is really nothing we can do but talk to our vendors and try to get them to standardize the API data.

1
See reviews by: Helpful|Rating|Date|All