overall it has been positive. Trying to make changes here is very bureaucratic when partnering with engineering teams. Teams are making changes that they don't understand to the infrastructure with no formal learning in place to bridge gaps.

willingness to learn and grow

They availability to the operational teams to discuss changes, concerns, etc.

willingness to allow folks to learn with a continuous growth model

I am operating within a lead capacity (staff or higher engineer) for the team.

I am very passionate about what I do and how I influence change in organizations that I am apart of

we have fun with what we are doing and make the best of burn out situations of trying to talk through organizational culture changes.

The market analysis is off for someone with my background and almost 15 years of experience. I am fulfilling the responsibilities of a staff engineer but paid as a engineer

I am passionate about what I do and some reluctance to adopt change is inevitable; however, finding solutions and working through problems makes me happy when building out a new program

the flexibility and willingness to adapt to unforeseen events. We laugh through the day and find ways to relate with each other and find ways to keep projects moving forward in an organization that is sluggish to implement change that isn't product focused.

adoption to change. this org still operates like 2 billion$ startup and that is alright as a culture to some degree but can conduct operations like that refined business process needed across the org but teams are to concerned with operating with no operational guardrails