Clement Poisson Email & Phone Number

Pleasanton, Ca, Us

Pleasanton, Ca, Us

Transitioned from being a team lead for the Access Control team to managing the team in its entirety. With my significant background on this team, I continue to work closely with Product Management such that the feature designs mesh well with our architecture and answer questions related to our team's components.Under my direction, the Access Control team has been delivering new feature work as well as significant performance improvements to our core existing feature sets. As a first project, we designed and delivered an optimal data structure that has enabled a 99% performance improvement in applying row-level security across tens of millions of documents with large security configurations.With my continued advocacy and involvement in the productivity space, I was tapped to build a team dedicated to this endeavor on July 2020. This team aims to improve various aspects of an engineer's day-to-day workflow by addressing bottlenecks, automating common repeatable tasks, and building out a platform over which development teams in our organization can continue building their own internal projects without the costly overhead.

Pleasanton, Ca, Us

As the go-to person for questions relating to Access Control, I spent my time mixed between the implementation of core team features and providing guidance to the younger engineers on the team. I participated in recurring feature planning and prioritization efforts to provide product leadership with technical guidance and feedback.I continued to involve myself in special internal projects. I worked with 3 other engineers to deliver the MVP for an internal project named "Performance Inspector". This is a single-page webapp built with React and Spring Boot which aggregates performance data across the entire production Vault fleet to highlight events that exceed our established SLAs. Backed by elasticsearch, the tool also provides the ability for engineers to quickly find real examples of poor performing operations when triaging customer reported performance issues.

Pleasanton, Ca, Us

As the development team increased in size, I continued to focus primarily on matters of access control within the platform. I personally led several large projects such as a full re-write of the persistence for content sharing and contributed heavily in multi-team efforts for providing granular access control to content on a row, column, and cell level.During this time I became invested in improving my personal development flow and wrote a handful of scripts and utilities to help with that. One of the tools that I wrote, the git j-utilities, has now become a core part of the established efficient workflow for the entire Vault team of over 500 engineers. This tool provides engineers a quick way of basing their code off of commits that have passed various stages of our CI pipeline in jenkins (hence j-utilities is short for jenkins-utilities). With this tool, engineers can focus on issues with their changes by avoiding commits containing bugs from other developers.I worked with a team of 3 other engineers to build and deliver an internal special project named "Piper" which is a React webapp that simplifies the visualization of Vault's CI pipeline. In a single page, anyone in the engineering team can easily comprehend the status of the pipeline. In addition to simple visualization, the tool provides advanced features like highlighting builds containing commits of a given username, subscribing to SMS alerts, bubbling up failed build claims, and viewing the commits + files changed in any given build.

Pleasanton, Ca, Us

One of the first 20 software engineers on the Vault platform now having grown to over 500 engineers. I focused primarily on matters relating to user management, authentication, and authorization. As the development team was small, I also contributed to various other areas of the platform such as configuration management and content security.In my first year, we designed and delivered user administration features at a domain level. As one customer may have multiple different Vaults under one domain (say example-pharma.com), the user administrators gained the ability to add users and change security profiles across all of the vaults from one -- rather than logging in to each vault individually to make the same changes. This feature is an early example of cross-vault communication. My focus was on designing and implementing the UI layer (JavaScript/Java) for this feature.In my second year, the team undertook a replacement of a hard-coded role based access control mechanism to a customer configurable design. While the Principal engineer designed the overall system and internal interfaces, I replaced the occurrences of hard-coded role checks with the appropriate granular permission checks. I also designed and implemented a Spring interceptor allowing engineers to annotate UI endpoints to easily check required granular permissions before entry.

San Luis Obispo, Ca, Us

Provided first-tier technical support for students, faculty, and staff. Managed user accounts and security requests.