Working at The Experience Engine | Glassdoor

The Experience Engine Overview

Work Here? Get a Free Employer Account
San Diego, CA
51 to 200 employees
accesso
2013
Company - Private
Enterprise Software & Network Solutions
Unknown / Non-Applicable
Unknown
TE2, The Experience Engine, a division of accesso, provides consumer-facing enterprises an engine to drive personalization, recommendations and commerce for the physical world, in real-time. We believe every consumer facing business with physical locations will benefit from a ... Read more

The Experience Engine Reviews

4.1
StarStarStarStarStar
Rating TrendsRating Trends
Recommend to a friend
Approve of CEO
(no image)
Scott Sahadi
28 Ratings
  • Helpful (6)

    "Best job I've had so far"

    StarStarStarStarStar
    • Work/Life Balance
    • Culture & Values
    • Career Opportunities
    • Comp & Benefits
    • Senior Management
    Current Employee - Software Engineer in Orlando, FL
    Current Employee - Software Engineer in Orlando, FL
    Recommends
    Positive Outlook
    Approves of CEO

    I have been working at The Experience Engine full-time

    Pros

    Our customers are "the big guys" (Sea World, Carnival, Hilton, etc).
    --- I can say "I wrote software that's running on that cruise ship over there." There's something kind of rewarding about that.

    The people are good.
    --- The people in the Orlando office are a rather fun group (good sense of humor, sociable, we have a former bartender which is a plus).
    --- We don't keep those who can't carry their weight. We either train them up or we get rid of them after a few months if training fails.
    --- I don't think I've met, at least in person, anyone here who is not open to creative criticism. This includes the management.

    The working environment is very engineer friendly.
    --- Politics exist in any environment. Both product owners and both managers I've worked under have done a great job at keeping the politics away from us.
    --- We try to follow best practices, when possible, when developing our products, i.e. unit test, do code/peer reviews, microservice all-the-things, take a stab a tech debt from time to time, etc. I've gotten the sense that this supported and encouraged by the executive board.

    Working conditions are good.
    --- I've been working here for almost a year and I have yet to need to work on the weekend.
    --- There are no "dedicated" hours that we're required to work. It's more of a "we have x amount of work that we have to get done by this date" type of environment. I tend to average between 40 and 45 hours a week.
    --- While we are expected to be in the office, we are allowed to work from home a few days a week if needed.
    --- We are allowed to dress casual (we can wear shorts and flip-flops).

    The executives and managers are transparent, care about their employees, and are easily contactable.

    Cons

    Lead developers spend WAY too much time in meetings.
    --- Our leads are very good at developing: that's why we put them there. Allowing them to get put in meetings for 4-7 hours a day is counter-productive.

    There is a serious lack of documentation.
    --- While we have lists of our API calls, including their parameters and returns, there are very few FAQs, user guides, and process flows. There is no documentation, internal or external, for specific sequence of calls required to [insert common process here].

    Advice to Management

    Schedule one day a week (Friday) where any non-"the ship realistically could sink if we don't have this meeting" meetings are absolutely prohibited.
    --- We did this at my last job. Literally no one complained.

    Hire 2-4 technical writers: at least one based in Orlando and at least one based in San Diego.
    --- This needs to be done sooner rather than later and is going to be exacerbated by our growth. This growth includes our number of employees, number of customers, and number of products.
    --- Remember: communication breakdowns can be deadly.

    Do not allow the culture to slip.

See All 30 Reviews

The Experience Engine Photos

The Experience Engine photo of: Cornhole Thirsty Thursday
The Experience Engine photo of: Cornhole Thirsty Thursday
The Experience Engine photo of: Orlando Team is Growing - Welcome RM
The Experience Engine photo of: Bill and Jess
The Experience Engine photo of: LOL no comment needed on this one ;)
The Experience Engine photo of: Alysse's reach is a little too short...
See All PhotosSee All

The Experience Engine Interviews

Experience

Experience
100%
0%
0%

Getting an Interview

Getting an Interview
30%
31%
23%
8
8

Difficulty

3.2
Average

Difficulty

Hard
Average
Easy
  1. Helpful (3)  

    Software Engineer Interview

    Anonymous Employee in Orlando, FL
    Accepted Offer
    Positive Experience
    Difficult Interview

    Application

    I applied through an employee referral. The process took a week. I interviewed at The Experience Engine (Orlando, FL) in May 2016.

    Interview

    I had a phone interview and two in-office interviews with various members of the team. Everyone was very welcoming and good at explaining their role and area of expertise. I felt that the interview was truly as much for me to get to know the company as for them to get to know more about me. We chatted about my previous experience and they asked a couple of technical questions.

    Interview Questions

    • Find the maximum node in an unordered binary tree, and then the same question for an ordered binary tree.   Answer Question
See All 13 Interviews

The Experience Engine Awards & Accolades

Let us know if we're missing any workplace or industry recognition – Add Awards

Pledges & Certifications

Pay Equality Pledge

Committed to paying equitably for equal work & experience

Tech Hiring Commitment

Helping to train, hire and promote more technology workers

Pledge to Thrive

Taking steps to prioritize employee well-being

Work at The Experience Engine? Share Your Experiences

The Experience Engine
  • Star
  • Star
  • Star
  • Star
  • Star
 
Click to Rate
or