Working with the Atlas Growth teams (1, 2, and Platforms), Cloud Frontend Platform team, and experimentation at MongoDB as a whole.

• Built out the Vercel Native Marketplace MongoDB integration, allowing Vercel users to create MongoDB Atlas clusters fully within the Vercel UI. Lead engineer on the project, which spanned 3 eng teams (Growth, Payments, and IAM) and product, design, marketing, and customer support org stakeholders.

• Scoped and rolled out a formalized 24/7 "On-Call" program for the 3 Atlas Growth teams that covered clear statement of duties, escalation policy, onboarding, education materials, training, weekly handoffs, and issue playbooks. Proactively supported On-Call triaging.

• Planned and implemented a new core service, Config Service, and migrated a major consumer to using it with minimal disruptions. Initiative spanned 3 major projects, with Java, Go, Javascript, and K8s elements, and 4-6+ engineering streams for a year.

• Spec'ed, developed, and released a Javascript SDK package for running MongoDB Atlas experiments, with Vanilla JS and React functionality. Package contains extensive documentation for ease-of-use for internal clients. Is the primary way to run Atlas experiments implemented in JS.

• Collaborated closely with Data Analytics and engineering stakeholders to design and develop a "global holdout" feature for the experimentation platform. Managed 4 other engineers to deliver the feature on-time, including extensive manual and automated testing and documentation.

• Designed, developed, and documented an end-to-end analytics testing framework to confirm (via Cypress E2E tests) our Analytics events health for critical events. As part of this project, introduced mock server capabilities to the main Atlas repo.

Engineer on the Atlas Growth 1 team, which designs and implements data-driven tests to improve customer acquisition and onboarding for the Atlas (MongoDB's Cloud-based DBaaS) product.

• Ideated, spec-ed, implemented, and completed A/B experiments for Atlas

• Created RFC (request for change) doc and POC PR to add Jest to the Atlas codebase. Got stakeholder buy-in and approval, leading to the merge of the POC. Over the next 6 months, made 10+ follow-up PRs to allow Jest to be used seamlessly (alongside legacy Mocha tests) in all parts of the codebase. Followed up with compiling a codebase-wide unit test coverage report--a first for the repo.

• Architected a full-stack internal A/B testing platform: front-end NextJS app + authentication/authorization mechanism + a MongoDB Realm orchestration layer (a Node 10-like environment) + Atlas cluster + endpoints for app consumers/producers + a CICD pipeline using Evergreen. Implemented with a project team of 5 other engineers. App contains functionality to set up and monitor A/B tests in MongoDB Atlas.

• Created and led department-wide discussion and approval on RFC to coordinate large frontend changes between teams in Atlas.

• Supported the proposal for and assisted with staffing a new team: Frontend Platform. Rotated on the team during its first quarter (Q1 2022) to build team momentum. Led an in-depth Bazel POC to determine fit for use as a frontend build tool.

• Active participant in bi-weekly Cloud Web Chapter (department-wide frontend discussion guild)

• Stack: React, Typescript, Mocha/Chai/Sinon/Jest, Java 8, MongoDB products (MongoDB, Atlas, Realm, Evergreen)

(individual contributor: non-people-manager track)

Still on debit card self-service team, but spent about 50% of my time on platform- and Bank-wide initiatives.

• Managed the initiative to rewrite all the self-service Debit features (9 features) in Angular 7/8/9 with ngRx and contributed most of the code. Focus was on sustainable code patterns and streamlining/updating Product logic.

• Active code reviewer of not just my team's repos, but also the customer-facing application repo which spans all of Capital One. Reviewed PRs for ~15 teams who contributed to the Bank's features for code quality and patterns. Code reviews represented 50% of my Github activity in 2019 and 2020.

• Socialized and followed-up with individual Bank teams about Platform-wide technical asks and initiatives, such as upgrading versions of software and new security practices, and provided suggestions on how to implement. Ran a weekly meeting with developers across Bank teams. Served as a primary developer contact point for Bank.

• Developed developer productivity enhancement tools (such as dashboards and Github hooks) as side-projects to reduce pain points in using Enterprise tools or adhering to Enterprise initiatives. After achieving stable MVP candidates, shared and presented these tools in department-wide forums so others can use the tools. One tool was being considered for company-wide use.

• One of the primary participants in Bank's Front-End Guild, which spaned across all teams in Bank tech and met twice a month. A regular presenter of topics. Suggested and helped organize first speed competition for the Guild (trying to recreate a mockup in vanilla HTML/CSS in 30 minutes).

• Top 10% of interviewers in 2019 and 2020 (1-3 interviews/week), and engaged in refining the interview process.

Continued work on the debit card self-service team, but with a greater focus on cross-team collaboration and discussion.

• Developed CICD UI application pipeline that runs 4 thorough suites of tests to confirm production-readiness of code before pushing to prod (uses Jasmine, Protractor, Cucumber, Docker, Selenium, mountebank, Applitools)

• Architected complex branch representative-facing feature to allow bank branches to instantly print physical debit cards

• Advised other feature teams on how to develop their features within the larger Capital One self-service application

• Participated and oftentimes led several weekly and bi-weekly forums to determine front-end coding practices and coordinate architecture and organization patterns across the company (multiple teams in multiple locations)

• Organized in-person office-wide AWS learning sessions with AWS account reps to inform architectural/dev-ops best practices and educate about new AWS services. First event featured 8 different topics across 2 days with 10-30 people per session. (Mar 2019)

• Spearheaded the first use case for DynamoDB in our application for the Change Spending/ATM Limit self-service feature

Worked on online debit card features, used by millions. Features allow users to activate, lock/unlock, change pin, order a new card, and track their card delivery. Projects include:

• Building a reusable tooltip component in 98% vanilla JS for company-wide consumption, with different position configurations: explicit, breakpoint-specified, and "smart" positioning based on viewport visibility

• Development of new self-service feature, (Order Debit Card) from creating the Node endpoints to implementing the design and UX in Angular

• Updating functionality to support self-service for multiple product types (360 and retail)

• Working with business to conduct necessary due diligence to adhere to strict internal, legal, and accessibility guidelines

• CICD deploys using an automated pipeline that uses Terraform, Docker, and AWS to deliver code from release branch all the way to production environment

• Coordinating with other Bank teams on cross-team releases and contributing to cross-team repos, in addition to our own

• Promoting our APIs within the company and proving our ability to serve new, non-traditional consumers (e.g. the mobile app) in a way that will lead to more cross-business partnerships in the future

• Certified AWS Solutions Architect

Full stack tech, including: Angular 1.x, Nodejs, testing frameworks (Jasmine, Mocha, Chai, Protractor), Java, HTML/SCSS, AWS