Engineer 'fired' after he lets daughter film iPhone X at Apple campus

The video may cause more damage as it includes footage of an iPhone X with special employee-only QR codes


Tech Desk October 29, 2017
Engineer gets fired for letting daughter film iphone X PHOTO: SCREENSHOT

Apple reportedly fired an engineer after a video was released showing him letting daughter use the iPhone X.

Brooke Amelia Peterson published a vlog earlier this week, which included a trip to the Apple campus to visit her father and to see an unreleased iPhone X.  The video quickly went viral and spread even further on YouTube.

Every iPhone X sold will make Samsung a lot of money

Peterson made another video later claiming her father has been fired as a result of her video. In a tearful message, she explains how her father violated an Apple company rule by allowing her to film the unreleased handset at Apple’s campus.

Apple’s request to remove the video went in vain as the video had already spread by the time they realized the damage.

It REVEALED MORE THAN IT WAS SUPPOSED TO

Apart from showing the iPhone X, which hasn’t publicly been made available, the video may cause more damage as it includes footage of an iPhone X with special employee-only QR codes along with a footage of the notes app which included the codenames of unreleased Apple products. Filming on Apple’s campus is strictly prohibited, so it's not much of a surprise that Apple acted so harshly to the filming.

Apple says iPhone X pre-orders are 'off the charts'

In the past, we’ve seen such dismissals for rule violations as a Microsoft employee was dismissed after his son posted pictures of the Xbox 360 before its release.

The engineer in had worked at the company for over four years, building the iPhone RF and wireless circuit design. Apple hasn’t responded officially yet.

You can see the video below.


This article originally appeared on The Verge.

 

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ