Pros
- Exposure to a wide variety of technologies across the firmware stack, from drivers to application-layer code. - Consistently challenging work that provides meaningful technical growth and a strong sense of accomplishment. - Open, responsive verbal communication among team members that facilitates collaboration.
Cons
- Verbal communication too often substitutes for written documentation (code, timelines, requirements); ownership of smaller design decisions can become a “hot potato.” - Product Management holds most decision-making power and prioritizes shipping the current product over longer-term quality or future releases; engineering suggestions are frequently ignored. - Management has shown a pattern of dishonesty about future work, leadership opportunities, and job security, which undermines trust. - Weekly 1:1s are treated as “your time” in name only—managers sometimes repurpose that time—further eroding trust and making effective teamwork difficult. - Titles and seniority are inconsistently applied: more experienced engineers can be placed under less-experienced leads, which creates confusion about authority and career progression.