Highly Satisfied
Last updated Jan 24 2025
Find out what you should be paid
Use our tool to get a personalized report on your market worth.What's this?
Principal Software Engineer Reviews
What is it like working as a Principal Software Engineer?
March 2020
World class R&D opportunities at Fast Labs.
Principal Software Engineer in Merrimack:
Pros: Down to earth, hard-working people
Cons: Can be difficult to find the right group for you
February 2020
Principal Software Engineer in Los Angeles:
Pros: Freedom to invent.
Cons: Poor implementation of agile methodologies; poor coordination/communication among functional teams.
October 2019
Fantastic, great people, good work/life balance.
Principal Software Engineer in Atlanta:
Pros: Constant challenges and new technologies
Cons: Can be somewhat disorganized due to the amount of employees and team across the globe.
September 2019
Principal Software Engineer in Santa Monica:
Challenging to accomplish quality work due to gatekeeping, constant priority shifts, and too many workstreams that prevent focusing on improving internal procedures and turning out market-leading work. There are many interesting technical problems to solve, but this is hampered by a necessity to influence across the org for almost all decisions - from selection of storage engines, improving deployment pipelines, and finding who has the keys to the gates. The compensation is mostly okay, but maintaining compensation at or beyond market rate is very difficult. After a couple years, our compensation is no longer competitive. Our peers are smart and capable, but their energy is often spent on process and politics, and not on producing quality products.
September 2019
Very Good competitive environment.
Principal Software Engineer in Bangalore:
Pros: More opportunities and most growing pace in knowledge .
Cons: Traffic
July 2019
Good work/life balance.
Principal Software Engineer in Manchester:
Pros: Good benefits, generally good people to work with. Most areas have good technology to work on.
Cons: No room for growth, specific area not doing well, too much cutting costs to look better, rather than actually be better, or doing what makes the most sense. Centralized IT and other functions that save a little in direct costs, with huge indirect costs (and incompetence).
July 2019
Principal Software Engineer in Cambridge:
The Broad engineering organization is becoming a coding farm, with opportunities for advancement bring filled from outside. I felt like a engineering team member and valued member of the Broad, and now Ii feel treated more like a resource, without much consultation about how the resource will be expended.
Principal Software Engineer Job Listings
Featured Content
‹
Remote Work
New research shows how to set pay for remote employees
Gender Pay Gap
New research shows that each woman experiences the disparity of gender pay gap in different ways, depending on her position, age, race and education.
Compensation Best Practices Report
From compensation planning to variable pay to pay equity analysis, we surveyed 4,900+ organizations on how they manage compensation.
Salary Budget Survey Report
See how organizations are shifting their salary budgets this year.
Retention Report
Get strategies you can use to retain top talent and learn how impactful employee retention really is.
Variable Pay Playbook
Before you decide whether variable pay is right for your org, get a deeper understanding of the variable pay options and the cultural impact of pay choices.
›