diff --git a/src/resume.json b/src/resume.json index 44717b5..4ce6c5e 100644 --- a/src/resume.json +++ b/src/resume.json @@ -44,12 +44,14 @@ "name": "Custom Ink", "position": "Senior Software Engineer", "url": "https://www.customink.com", - "startDate": "2021-12-21", - "endDate": "2023-12-29", - "summary": "Develop and maintain custom software to support the in-house printing facilities (IHP). Work closely with management and user stakeholders to build software that meets users' needs and make their work more efficient, while interfacing with the hardware used in the screenprinting and direct-to-garment (DTG, digital) printing process.", + "startDate": "2021-12", + "endDate": "2023-12", + "summary": "Developed and maintained custom software to support the in-house printing facilities (IHP). Worked closely with management and user stakeholders to build software that met users' needs and made their work more efficient, while interfacing with the hardware used in the screenprinting and direct-to-garment (DTG, digital) printing process.", "highlights": [ - "I joined with numerous others from other teams to help triage and remedy an incident of widespread technical slowdown within the production facility. The primary root cause turned out to be a networking issue, but due to the intermittent nature of the symptoms, we went through the whole stack with a fine-toothed comb.\nFor my part, I uncovered a misconfiguration in the kubernetes settings for one of our applications that was causing it to kill and restart pods far more frequently than it should have. While this was not the source of this slowdown, I knew fixing it was necessary to ensure proper reliability of that application and those it depended on and would fix other intermittent downstream issues.", - "As a side-effect of the facility slowdown situation, there was an appetite for better deployment notifications. However, the interim solution that had been implemented was very manual and cumbersome. I collaborated with several engineering managers of other teams to come up with and orchestrate the implementation of an automated notification system.\nAs part of a long-term, cross-team initiative, we came up with a plan to use Github pull requests to provide the content and the trigger of a notification that would describe in plain language what the change was doing and why, the level of risk for the deploy, and link to supplemental outputs of the development process (including the issue tracking item, project pitches, architectural decision records, Slack discussions, and anything else relevant). The automated system was then intended to take the pull request contents, display a portion of it on a unified dashboard, with a link to the full pull request for technical stakeholders, and send an email out to those who wanted it.\nAs of the time of my departure, we had taken several steps to bringing the pull requests into alignment with this vision, including working out with a broader collection of engineers a “bring your own process” for assessing the risk of a change while using the same output chart to serve as a common “language” to stakeholders, and were evaluating our existing tools and past projects to see what existing work we could leverage in this new vision." + "Implemented changes with an impact of $650k in annual savings", + "Took ownership of software fundamental to the DTG process", + "Worked across teams and roles to plan and implement process and quality of life improvements", + "Experimented on ways to create better technological solutions to applicable problems" ] }, { @@ -58,7 +60,7 @@ "url": "https://www.proofgeist.com", "startDate": "2018-11", "endDate": "2021-11", - "summary": "Help manage the custom Python/Django portions of client's FileMaker-backed web application.Create a component library system that takes React, Vue, or Svelt components and creates self-contained Web Components for both general web use and use inside FileMaker.", + "summary": "Helped manage the custom Python/Django portions of client's FileMaker-backed web application.Create a component library system that took React, Vue, or Svelt components and created self-contained Web Components for both general web use and use inside FileMaker.", "highlights": [ "Researched and developed a component library and build tool that could take Vue, React, or Svelt components and output self-contained, vanilla Web Components that could be used either in standard web applications, or within FileMaker's environment (which required additional processing to make all of the component's dependencies self-contained)." ] @@ -75,10 +77,19 @@ } ], "projects": [ + { + "name": "Deployment Notification Automation Initiative", + "entity":"Custom Ink", + "description": "As a side-effect of the facility slowdown situation, there was an appetite for better deployment notifications. However, the interim solution that had been implemented was very manual and cumbersome. I collaborated with several engineering managers of other teams to come up with and orchestrate the implementation of an automated notification system.
As part of a long-term, cross-team initiative, we came up with a plan to use Github pull requests to provide the content and the trigger of a notification that would describe in plain language what the change was doing and why, the level of risk for the deploy, and link to supplemental outputs of the development process (including the issue tracking item, project pitches, architectural decision records, Slack discussions, and anything else relevant). The automated system was then intended to take the pull request contents, display a portion of it on a unified dashboard, with a link to the full pull request for technical stakeholders, and send an email out to those who wanted it.
As of the time of my departure, we had taken several steps to bringing the pull requests into alignment with this vision, including working out with a broader collection of engineers a \"bring your own process\" for assessing the risk of a change while using the same output chart to serve as a common \"language\" to stakeholders, and were evaluating our existing tools and past projects to see what existing work we could leverage in this new vision.", + "highlights": [], + "keywords": [], + "startDate": "2023-08", + "endDate": "2023-12" + }, { "name": "Electron Application Shipping Tool Feature", "entity": "Custom Ink", - "description": "I implemented the new shipping interface, allowing the production team to use the Electron application from start to finish for every task, where previously, they needed to switch tools for some tasks. During this implementation, I brought large portions of the codebase up to modern standards, converting the React class-based components to function-based components, and integrating React Router and our in-house component library. I also began the process of reorganizing the file structure to modern standards to allow for better maintainability as the application grew in complexity.\nImpact: $210k annual production cost savings + untracked engineer maintenance cost savings", + "description": "I implemented the new shipping interface, allowing the production team to use the Electron application from start to finish for every task, where previously, they needed to switch tools for some tasks. During this implementation, I brought large portions of the codebase up to modern standards, converting the React class-based components to function-based components, and integrating React Router and our in-house component library. I also began the process of reorganizing the file structure to modern standards to allow for better maintainability as the application grew in complexity.
Impact: $210k annual production cost savings + untracked engineer maintenance cost savings", "highlights": [ "Began enacting previously-created plan to modernize codebase", "Converted many components from class-based to function-based", @@ -96,7 +107,7 @@ { "name": "Electron Application Upgrade", "entity": "Custom Ink", - "description": "I took ownership of the Electron and React application that powered the direct-to-garment (digital) printing process. Starting in my first year, I updated it from Electron 5 to Electron 20, React 16 to React 20, Material UI pre-1.0 to v5, and created a plan and guidelines for keeping it up to date, as well as enumerated up to date best practices.\nAdditionally, I automated the release process by creating Windows and Mac builds in CircleCI and automating the Windows releases to our release server using release-it to automatically generate Github releases.", + "description": "I took ownership of the Electron and React application that powered the direct-to-garment (digital) printing process. Starting in my first year, I updated it from Electron 5 to Electron 20, React 16 to React 20, Material UI pre-1.0 to v5, and created a plan and guidelines for keeping it up to date, as well as enumerated up to date best practices.
Additionally, I automated the release process by creating Windows and Mac builds in CircleCI and automating the Windows releases to our release server using release-it to automatically generate Github releases.", "highlights": [ "Performed a major, breaking upgrade that remained invisible to end users", "Formulated plan for modernizing the legacy codebase for easier future maintenance", @@ -116,7 +127,7 @@ { "name": "Auto Cart Builder", "entity":"Custom Ink", - "description": "I wrote the new algorithm for prioritizing orders in the screenprinting process and as part of a team, overhauled the process for 20% increase in efficiency, a significant increase in our \"delivered error-free, on-time\" metrics, and near-elimination of facility-created \"rush\" orders.\nThe new process selected orders to batch together on a cart based on numerous factors, including number of screens needed, completion deadline, number of colors, and more.\nImpact: $440k annual production cost savings", + "description": "I wrote the new algorithm for prioritizing orders in the screenprinting process and as part of a team, overhauled the process for 20% increase in efficiency, a significant increase in our \"delivered error-free, on-time\" metrics, and near-elimination of facility-created \"rush\" orders.
The new process selected orders to batch together on a cart based on numerous factors, including number of screens needed, completion deadline, number of colors, and more.
Impact: $440k annual production cost savings", "highlights": [ "20% increase in prioritization efficiency", "$440k cost savings per year", @@ -133,10 +144,11 @@ { "name": "Shopify-Netsuite Integration", "entity": "Rocket Code", - "description": "I built a fully unit-tested, custom, bi-directional, ETL integration layer to allow Shopify act as the store's online storefront.\nThis layer:\n- Took orders from Shopify and sent them to Netsuite for fulfillment\n- Took Netsuite's fulfillment updates and sent them to Shopify for customer updates\n- Took inventory information from Netsuite and sent it to Shopify, transforming it to allow for the automatic creation of products, variants, and collections, and with the use of tags, populate collections such that the custom storefront displayed them as single products (necessary due to the number of variants for the products)\n- Synced gift card information between Shopify and Netsuite to enable customers to use their brick-and-mortar store-created gift cards on the website", + "description": "I built a fully unit-tested, custom, bi-directional, ETL integration layer to allow Shopify act as the store's online storefront.
This layer:", "highlights": [ - "Bidirectional ETL", - "" + "Created robust, bidirectional ETL", + "Responsible for planning, architecture, and implementation", + "Created gift card conversion system" ], "keywords": [ "PHP", @@ -289,15 +301,23 @@ "references": [ { "name": "Chris Impicciche", + "url": "https://www.linkedin.com/in/chris-impicciche/", "reference": "During our time working together, I had numerous opportunities to collaborate with Shauna, despite not being on the same team. She was quick to offer her assistance in Ruby/Rails and provided valuable support whenever needed. I was consistently impressed by Shauna's inquisitive nature, approach to learning new technologies, and friendly demeanor. I appreciate the chance to have worked alongside her and firmly believe she would be a valuable addition to any tech team." }, { "name": "Fatemeh Abniki", - "reference": "Shauna is an exceptionally talented engineer . She consistently demonstrates a high level of expertise, problem-solving skills, and creativity in tackling complex technical challenges. \nMoreover, Shauna is an excellent team player who collaborates effectively with colleagues across different departments. She communicates ideas and solutions clearly, making her a valuable asset in both individual and collaborative settings. Her positive attitude, willingness to learn, and adaptability to new technologies make her a standout performer." + "url": "https://www.linkedin.com/in/fatemeh-abniki-583510224/", + "reference": "Shauna is an exceptionally talented engineer . She consistently demonstrates a high level of expertise, problem-solving skills, and creativity in tackling complex technical challenges.
Moreover, Shauna is an excellent team player who collaborates effectively with colleagues across different departments. She communicates ideas and solutions clearly, making her a valuable asset in both individual and collaborative settings. Her positive attitude, willingness to learn, and adaptability to new technologies make her a standout performer." }, { "name": "Jonalyn Blunt", - "reference": "Shauna is an outstanding engineer; I cannot recommend her enough. I collaborated with Shauna on a weekly basis as the lead UX Designer for a new digital tool we created inside an existing in-house application. The tool was released to overwhelming positive feedback and a high adoption rate, which is a testament to Shauna's great skills as an engineer. \nI was impressed with Shauna's attention to detail, and dedication to the tool — not only to eliminate tech debt and get the application where it needed to be on a foundational level, but being able to think through the experience holistically — foreseeing challenges for users and the tool, and championing to fix the root cause. Shauna is a person you want in the room with you to discuss ideas and to deliver results; she is an exceptional addition to any team." + "url": "https://www.linkedin.com/in/jonalynblunt/", + "reference": "Shauna is an outstanding engineer; I cannot recommend her enough. I collaborated with Shauna on a weekly basis as the lead UX Designer for a new digital tool we created inside an existing in-house application. The tool was released to overwhelming positive feedback and a high adoption rate, which is a testament to Shauna's great skills as an engineer.
I was impressed with Shauna's attention to detail, and dedication to the tool — not only to eliminate tech debt and get the application where it needed to be on a foundational level, but being able to think through the experience holistically — foreseeing challenges for users and the tool, and championing to fix the root cause. Shauna is a person you want in the room with you to discuss ideas and to deliver results; she is an exceptional addition to any team." + }, + { + "name": "Chris Murphy", + "url": "https://www.linkedin.com/in/christopher-murphy-1375155/", + "reference": "I met Shauna at Custom Ink, in fact I helped interview her and was one of several to give a 👍. I never had the pleasure of working on a project with Shauna (different domain/team), but we both seemed to care about the same non-project concerns that we felt were being neglected. That was mainly around our state of documentation at the time (multiple, siloed knowledge bases of varying quality), technical debt problems, and occasional change management issues. We often bounced ideas off each other and I always found her opinions and feedback insightful. I also appreciated the ideas she brought to wider engineering discussions at things like all-hands, hack-a-thons, and show & tell. She's not afraid to speak up about what she cares about, a quality I wish more engineers had to be honest.
As for Shauna's engineering skills, I know she wasn't afraid to dive deep into the systems (some being *very* \"legacy\") that her team owned, to figure out a solution for the project at hand. The tech stack there was typically Ruby on Rails and React, both she's highly skilled in. I think any company would be lucky to have Shana on board and I highly recommend her." } ] }