Facebook adds 5 divs, 9 spans and 30 CSS classes to every post in the timeline

I interviewed at FB recently (didn't pass the in-person) and the one question I asked each interviewer was "tell me about the parts of FB I don't see" - because they have an odd hiring process where you don't figure out what team you'd be working with until after you are hired...and I had no interest in pushing Ads, but understood that wouldn't be a great pitch from my side.

Turns out there is a LOT about ads at FB. Not everything, but a lot. Particularly in the Seattle office.

I was surprised I hadn't passed the interview (thought I did well), but in retrospect I'm glad. Whether that's sour grapes on my part, the fact the news has been full of reasons to be glad not to work at FB, or that I was very concerned that anything I did would end up pushing ads is something I can't be 100% certain of.

> you don't figure out what team you'd be working with until after you are hired

That sounds like hell. I need to meet the team I'll be working with before accepting an offer. It's the only way to know if they're competent, can communicate, and are not assholes.

> I need to meet the team I'll be working with before accepting an offer. It's the only way to know if they're competent, can communicate, and are not assholes.

This is exactly how Facebook's onboarding process works (at least in engineering). You spend 3-4 weeks in "bootcamp" classes (React 101, IOS 101, etc.). After that, you spend another 3-4 weeks auditioning teams -- you sit with teams that have open headcount for a week, attend their meetings, and work with a mentor on a coding project. Once you decide which team is the best fit, you "graduate" bootcamp and join them.

It's not perfect -- if there's no open headcount on your dream team, you'll have to pick another, but it's the best onboarding process I've seen from an employee standpoint.

Is this process for new college grads or senior engineers? I can't imagine principals go through this process, do they?