EF Education First Software Developer Reviews

Pros

Very knowledgeable coworkers from which to learn. Great tools and workshops for professional development. They are invested in you and your time there.

Cons

Possibly a long commute, but that is part of living in Boston.

Pros

Lots of freedom and you can make a big impact. Treated like a full time Software Engineer.

Cons

None. EF is a great place to work.

Pros

Party culture, young employees. Nice new facilities in Boston. Expect to make friends here. Great place to start a career, as a developer you'll get to contribute to software used daily, and interact with those very users. Great product you'll feel good working on. Potential for travel perks.

Cons

Little room for growth. Stale technology and ignorance towards developing trends. Noncompetitive salary. Poor retirement package. Company culture to hire young and replace with a new generation once they become dissatisfied. Very shallow depth of experience in tech team.

Pros

EF has great people with amazing team dynamics, making the work atmosphere very pleasant. Management offers many opportunities to developers to grow and own projects.

Cons

EF doesn't give out stock.

Pros

I was an undergraduate 4th year student, working part-time as a mobile developer intern with little experience in iOS development. The progress we made was super fulfilling! We kept momentum, thought carefully about what we could improve, and got things done. I learned everything I know about Objective C and Swift here. Thomas helped us create organized code, and he was careful. I loved the experience and learned a lot! The culture is very uplifting. The people look great and professional. The people are really really nice. The office looks amazing! You will be stunned! There's food at Lingo Bar and Grill downstairs that you can purchase for lunch. If you join as a mobile app developer intern, you will learn a lot and contribute to quality, careful code under great supervision. At least I did under Thomas. Even near the end of my time at EF, we were making a lot of progress and thinking ahead because we cared.

Cons

For software engineers, the development process can feel not so unified among other EF offices. Each office does its own thing, which is fine because EF has many different divisions and functions. But I would like to see information from other offices on their development process or tips, which was not available through a unified documentation portal. I think that other teams (design, marketing, etc.) could be more integrated with the development team. When it came to design, I felt that the design team would give a design without explaining the decisions made. I should have advocated for more meetings between us, developers, and the design team in particular to get a feel for what they were thinking, but I was too shy.