Pros: Mission, the impact this company has and the impact you can create as an intern is amazing. You immediately work on hard and important problems, with no side projects to keep interns busy. You're treated as a full-time employee for the most part. Culture, the people are among the friendliest and smartest out there. You can ask anyone for help. Further, from the constant internal dialogues, you can tell the company is ethically-minded and pursues success with integrity. Support system, mentor/lead/team/recruiter are all actively helping you make the internship a great experience. If there's a problem, you can raise it and it will be addressed. Personal growth, you're given a voice in what you want to do and what skills you want to improve. Travel, we had the opportunity to travel across and out of the country as interns. Perks, the free housing, 3 meals a day, the haircuts, the massages, etc., make life quite comfortable. Intern cohorting, interns in an office got to know each other pretty well and we've become friends throughout the internship. This is just my experience, but my experience isn't uncommon from what I can tell. Compensation, one of the highest out there.

Cons: Finding your own work-life balance. Because of the flexible hours, it can be difficult to find a balance that works for you when you see coworkers arriving or leaving at vastly different hours. That said, I didn't feel any pressure to work late or get in early. It's just a matter of doing what's best for you and communicating that.

Pros: High ownership and smart people.

Cons: Not very much coding day to day.

Pros: Overall: - Good perks, especially house subsidy and free food (go out and buy whatever you want reasonably). - Smart and energetic colleagues. I worked for two different teams, and my experience was very different: Team 1: - Experienced lead with great technical knowledge, very good communication, and quick, actionable feedback. - Workload is reasonable. - Colleagues are very friendly and great to work with. - Probably one of the most pleasant teams to work with. Team 2: - The work is more interesting than Team 1's. - The product is used by several important organizations.

Cons: Overall: - "Flat hierarchy" is a joke; leads with absolute power are big dictators. You will never have a chance to talk to the lead of your lead, and there are 3 or 4 people on the top of the hierarchy if you are a software engineer. - Way understaffed. - Devs in the satellite office are very dependent on devs in the headquarters. Team 1: - The project is a bit tedious, not very distinctive from what many other startups are doing. Team 2: - Possibly the worst software management I have ever experienced. - Very inexperienced, political, terrible, close-minded, and hypocritical lead: doesn't understand the tasks technically, constantly sets unreasonable expectations, judges people at every detail inside and outside of work, thinks documentation is a waste of time, and takes constructive feedback very personally. I am not sure why he is in the tech industry; Wall St may suit him better. - There is little to no mentorship when you get into a new team. - Every word you speak can be used to go against you when needed. - Frequently burnt out due to unreasonable expectations (working up to 5 AM to meet the lead's expectation is a norm). - Many egoistic colleagues are close-minded, unwilling to help, and unwilling to debate for better ideas. - Literally no documentation; you will waste most of your time comprehending code that is done at 2 AM without any support. - The work itself is not hard; it is hard because you are going to work alone without any documentation. - Testing and release process is a joke. - Performance Improvement Plan is an absolute play. If your lead doesn't like you, even if you complete your PIP successfully, he will extend it until he can find a small fault (or maybe not even a fault) to force you out. If you are ever put under a PIP and feeling your lead doesn't like you, make sure to choose to quit for better benefits, as you will be fired at the end anyway. Advice to new hires: avoid the PG Infrastructure team unless you want to be burnt out and to waste your time learning bad-quality codes.