Plato Elevate Winter Summit has been announced (Dec 7th-8th)

🔥

Back to resources

Collaborating With a Cross-Functional Expert

Dev Processes
Internal Communication
Team Processes
Cross-Functional Collaboration

17 June, 2021

Rafal Leszczynski
Rafal Leszczynski

Engineering Manager at Sourcegraph

Rafal Leszczynski, Engineering Manager at Auth0, relied on the help of an assigned expert from the security team to provide context to them as developments emerged and problems arose.

Problem

At my previous job, my team, the product engineering team, was having some trouble cooperating with the security team. We had a lot of interaction with security, mostly concerning vulnerabilities that they’d discovered and new initiatives that we would be collaborating on for the company.

For our purposes, a thorough security review process was essential. The problem that we were experiencing was that there were multiple security engineers reporting their findings to us, and, each time we wanted to have another security review or risk assessment, a different person would be assigned from their end.

Our colleagues from security didn’t necessarily have equal amounts of context when it came to what our objectives entailed. All of the different feedback and suggestions from them were great, but it took a lot of time to bring every new person who became involved up to speed. There was a lot of back and forth and additional work.

Actions taken

We approached the other team and suggested: instead of one of many engineers from their side, assigning only one security expert as our official point of contact. We pledged to invest the time and energy into training them completely on my team and our processes, onboarding them and giving them the knowledge and the expertise needed to function fully in the role.

They would have the opportunity to bond with my team and to build relationships within the company from that perspective. In the long run, we would be able to reduce the back and forth and to have a more common understanding around security problems and our application restraints in order to conduct a more effective security review.

They thought that it would be a good idea. We got our security expert assigned to us. We were already in the process of onboarding a new product engineer, so they were able to go through the process together. We invited this person to all of our outings and social events. In one or two months, we were able to drastically change the way that we worked. We had a new initiative in front of us, and, with our new security expert, all of our security reviews have been really productive and smooth. Ad hoc vulnerability reporting was still done by multiple people as different engineers conducted different penetration tests, but we relied heavily on this one person who was able to provide that context to the security team and to be this kind
of bridge between us and them.

Lessons learned

  • Assigning a specific security engineer to every single team became a company-wide policy after this experience. This unique solution was applied widely and to our advantage as a company.
  • My team really enjoyed having somebody specific to talk to about the problems that they were having. We weren’t just throwing our problems over the wall anymore. We became more equipped to work together and to collaborate effectively.
  • Both teams were able to acquire a more nuanced understanding of both the other side’s domain, as well as the domain that they already were experts in beforehand. They not only had access to more new information on a professional level; there was also this human-to-human interaction that allowed them to move past the distance of a distributed remote environment.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Delegate successfully as a first time manager of Product Managers

24 November

Andrew Tsui, a Product Leader, works to build great teams that are independent, demonstrate mastery of their domain, and fully commit to their purpose.

Scaling Team
Building A Team
Delegate
Coaching / Training / Mentorship
Psychological Safety
Cross-Functional Collaboration
New Manager
Andrew Tsui

Andrew Tsui

Director of Product at Startup

Specialization vs. Wearing Many Hats

23 November

William Bajzek, Director of Engineering at Sapphire Digital, compares and contrasts a team structure that utilized siloed skill sets and one where everybody’s duties overlap at the edges.

Internal Communication
Collaboration
William Bajzek

William Bajzek

Director of Engineering at Sapphire Digital

Building a New Team in a Foreign Country

23 November

Adam Hawkins, Site Reliability Engineer at Skillshare, went all the way across the world to build a brand new team who worked very differently than he was used to.

Team Processes
Adam Hawkins

Adam Hawkins

Site Reliability Engineer at Skillshare

What It Takes to Understand Other’s Perspective

23 November

Nicholas Cheever, Divisional Vice President, Global Supply Chain Technology at Trimble Transportation, shares how to really understand someone else’s point of view.

Team Processes
Nicholas Cheever

Nicholas Cheever

Divisional Vice President, Global Supply Chain Technology at Trimble Transportation

How to Handle Team Collaboration After a Merger?

23 November

Nicholas Cheever, Divisional Vice President, Global Supply Chain Technology at Trimble Transportation, shares how he helped the acquired company’s team members understand the business mission and give them focus.

Acquisition / Integration
Team Processes
Nicholas Cheever

Nicholas Cheever

Divisional Vice President, Global Supply Chain Technology at Trimble Transportation

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.