Working at Justworks | Glassdoor

Justworks Overview

New York, NY
201 to 500 employees
Company - Private
Unknown / Non-Applicable
At Justworks, we help entrepreneurs take care of their teams through benefits, payroll, and compliance, so they can focus on growing their business.

We are passionate about helping small businesses succeed and it is reflected in everything we ... Read more

Mission: We started Justworks to free entrepreneurs to focus on what matters: growing their business and creating a better place to work.

Glassdoor Awards

Best Places to Work: 2017 (#12)

Top CEOs: 2016 (#2)

Justworks Reviews

Rating TrendsRating Trends
Recommend to a friend
Approve of CEO
Justworks Founder & CEO Isaac Oates
Isaac Oates
88 Ratings
  • "Great company environment"

    • Work/Life Balance
    • Culture & Values
    • Career Opportunities
    • Comp & Benefits
    • Senior Management
    Former Employee - Account Manager
    Former Employee - Account Manager
    Positive Outlook
    Approves of CEO

    I worked at Justworks full-time (More than a year)


    Great people, collaborative culture, good perks


    None that I can think of

See All 96 Reviews

Justworks Photos

Justworks photo of: The Justworks team
Justworks photo of: The Justworks team
Justworks photo of: The Justworks team
Justworks photo of: The Justworks team
Justworks photo of: The Justworks team
Justworks photo of: The Justworks team
See All PhotosSee All

Justworks Interviews



Getting an Interview

Getting an Interview




  1. Helpful (1)  

    Software Engineer Interview

    Anonymous Interview Candidate
    No Offer
    Negative Experience
    Average Interview


    I applied online. The process took 3 weeks. I interviewed at Justworks.


    The interview process consisted of a pre-screen with someone who could not have been less interested in talking to me. A quick technical screen with an engineer, which was basically count the characters in a word. The onsite was 4 back to back sessions of interviews. The first session was a coding test. I met with two other engineers. I was pretty frustrated because I had already been told they were language agnostic, but they told me it had to be done in either Java or Ruby. I was pretty frustrated, and I probably should have toned that back.

    I wound up writing the answer in ruby, but we spent a lot of time dealing with syntax, instead of solving the problem.

    The next pair I met with had me talk through how I would design the MVC portion of a trello like app. It was fun, but a little vague.

    The next pair I met with was just general Q&A about the company. Finally I met with the VP of engineering. He seemed like a good guy albeit with too much on his plate.

    I didn't find out (although I could guess it) what the outcome was until nearly a week later, when I emailed my contact (who I never met) and she promptly responded with a form letter.

    Overall it felt a bit like a meat market, and there was not a real effort to get to know the candidate, and it was tough to get to know the team. It would be nice to have better follow through from the recruiters, and I'd strongly suggest some kind of lunch, instead of sitting in a loud conference room for three hours. It's also really silly to require the coding test in an arbitrary language. The idea is to talk through the problem, not spend time with syntax. From what I could tell, the engineers were a smart and fun group.

    Interview Questions

    • Given a list of arrays, each having a start and end attribute, determine if the arrays are saturated.   Answer Question
See All 115 Interviews

Justworks Awards & Accolades

  • Great Place to Work, Great Place to Work®, 2016
  • Great Places To Work, Great Place to Work, 2017
See More

Work at Justworks? Share Your Experiences

  • Star
  • Star
  • Star
  • Star
  • Star
Click to Rate