Working at Lucasfilm | Glassdoor

Lucasfilm Overview

Work Here? Get a Free Employer Account
San Francisco, CA
501 to 1000 employees
1971
Subsidiary or Business Segment
Motion Picture Production & Distribution
$50 to $100 million (USD) per year
DreamWorks Pictures, Sony Pictures Entertainment
The Force is definitely with Emperor George Lucas. The brains behind the "Star Wars" and "Indiana Jones" series, Lucasfilm is one of the most successful independent movie studios in the history of film. Owned by ... Read more

Lucasfilm Reviews

3.2
StarStarStarStarStar
Rating TrendsRating Trends
Recommend to a friend
Approve of CEO
(no image)
Kathleen Kennedy
27 Ratings
  • Helpful (3)

    "Coordinator"

    StarStarStarStarStar
    Current Employee - Coordinator/Manager
    Current Employee - Coordinator/Manager

    I have been working at Lucasfilm full-time (More than 3 years)

    Pros

    The company culture is wonderful. The company does mini-talks by people in the Entertainment and Tech industry. It feels like a mini-film school. The films are epic, so you always feel like you are involved in something bigger.

    Cons

    In my time at Lucasfilm I was relocated to San Francisco, and then back to Los Angeles. I love San Francisco, but the hardest part about being there is you feel a little detached from the Entertainment Industry.

See All 130 Reviews

Lucasfilm Photos

Lucasfilm photo of: Yoda Fountain
Lucasfilm photo of: The Main House where george works
Lucasfilm photo of: Tech Building
Lucasfilm photo of: Lake Ewok
Lucasfilm photo of: Yoda
Lucasfilm photo of: Home away from home
See All PhotosSee All

Lucasfilm Interviews

Experience

Experience
59%
23%
18%

Getting an Interview

Getting an Interview
61%
26%
9%
4

Difficulty

2.7
Average

Difficulty

Hard
Average
Easy
  1.  

    Software Engineer Interview

    Anonymous Interview Candidate
    No Offer
    Negative Experience
    Easy Interview

    Application

    I applied through an employee referral. I interviewed at Lucasfilm.

    Interview

    I had a phone interview, and a few weeks later, they wanted to fly me in to SF for an onsite interview. I asked if they would fly me out of Burbank instead of LAX, because I live right next to Burbank. I also asked if I could come in the night before, because the interview was set for 9 a.m. and I didn't want to have to wake up at 5 a.m. and have a half-day interview after that. They said they would look into these things for me, but they didn't respond -- they just bought me a ticket out of LAX for early that morning. My flight, of course, got delayed. So I was super-anxious about that. I called them and they said it was fine, but I ended up being two hours for the interview. My first meeting was with three project managers at the same time. This part of the interview was probably the best part. They asked a lot of good questions about how I work and how I would respond in certain situations. Then the next interview was with 10 engineers at once -- apparently the whole team, all sitting around a table with me in the middle, and they went around one by one and asked me mostly basic questions about front end engineering. It was a tad bit unnerving, but I think I did well. Everyone seemed to like me except one of the lead engineers, who for some reason seemed to look at me suspiciously. He asked a question about browser event capture that I answered but not quickly, and others kinda smirked at his overly serious nature toward me. Then he asked me if I ever used the framework Gulp before, and he was flabbergasted that I had not really much experience with him. I tried to explain that I came from a Ruby on Rails background (Lucasfilm is Python), and that RoR uses Asset Pipeline to handle task-running, that in fact Grunt and Gulp are copied from Asset Pipeline. This did not seem to register with him. I think I actually did fine during this phase of the interview, except for these two points. The third interview was supposed to be with the head of the group, but because I was late to the interview because of the the flight delay, she said she would have to shuffle things around and meet with me later in the day. So at that point, I had been scheduled to meet alone with the lead engineer who didn't like me to do some whiteboarding. I mentioned that I wasn't a huge fan of whiteboarding as a means of gauging a programmer's skills. I didn't in any way suggest that I didn't want to do it -- only that I didn't care for whiteboarding in general. This really pushed him over the edge, I think. He left the room and never came back. I sat there for 10-15 mins. I literally didn't know what was going on -- I thought maybe he had some scheduling conflict he had to resolve and that he would come back to the room momentarily. Finally, the admin came in and brought me back to her desk and said the lead engineer was busy and would come out to interview me in a little while. The admin kept apologizing and said the head of the group would come meet me first, and THEN I'd meet with the lead engineer after that. I ended up sitting next to the admin for about 45 mins. Finally, she got word that both the head of the group and the lead engineer were pulled into other meetings and would be unable to meet me at all. So I flew back home and got word a few days later from the internal Lucasfilm recruiter: the answer was "maybe." They couldn't say yes or no at that point, but I took it to mean no. I filed my cab receipts as expenses (which they said to do), but they said they wouldn't pay for my cab fare to and from LAX, which ended up costing me $150. Six month later, I emailed the recruiter telling him that he never gave me an official decision, that he only told me "maybe" and I never heard back from him. He apologized and said no.

    Interview Questions

See All 24 Interviews

Lucasfilm Awards & Accolades

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

Work at Lucasfilm? Share Your Experiences

Lucasfilm
  • Star
  • Star
  • Star
  • Star
  • Star
 
Click to Rate
or