As a technical trainer on the Nimble AMS team, my role is to help clients learn the system throughout the build process. I work with clients at the very start, getting them familiar with Nimble as they start to work with the implementation team, all the way up to showing their staff how to use the system right before they go live. I've made training more flexible and use examples more relevant for the particular clients attending the courses. I've worked on getting our training version of Nimble more realistic, and I've been doing the monthly updating as needed.Key Accomplishments- Conducting full-day training with clients over Teams- Increasing revenue with new training classes- Improving training data and materials

As a Security Orchestrator, I was responsible for scheduling penetration tests (ethical hacking engagements) for clients. There was a lot of reaching out to clients and working with resources to get the tests scheduled. I also helped with some Salesforce admin duties, although in a lesser capacity than was floated to me during the interview. This was a contract-to-hire position, and it wasn't a good fit for me.

As an analyst, my duties included helping to create the infrastructure needed to bring in all of the Service Operations teams into Salesforce, including mapping current business processes, developing page layouts, looking at permission set groups, etc. I worked with a consultancy, acted as the Product Owner in their Agile Scrum process, and also was in charge of training users on how to use the system.Key Accomplishments:- Represented the Service Operations team as Product Owner during Scrum, including creating user stories and grooming the backlog in Jira.- Conducted thorough UAT testing of the flow that the consultancy built to our specifications.- Wrote documentation and trained new users.- Passed on my first attempt the Salesforce Certified Administrator and the Service Cloud Consultant exams.

My first role at Newmar involved researching product information for inclusion in Newgle, Newmar's knowledgebase for customers and dealers/technicians. Basic information about products was included, as well as links to manufacturer websites and files associated with the products.Key Accomplishments:- Developed standards and planned improvements to company's community knowledgebase.- Cleaned up data and corrected inaccurate information.

The team leads ran the nightly operations in the shipping department. Following our standard work, we created a game plan for the night, setting us up for success. We provided feedback to the team and helped guide employees in becoming more proficient and accurate. We conducted a nightly team meeting to let everyone know what's going on in the department and at the company.In addition, I oversaw the print crew, helping to determine what orders needed to be released for fulfillment and setting up processes if things needed to change. I developed methods for tracking compliance in a time sensitive market, prioritizing workflow to prevent late shipments. I helped bring the late-order rate on this market to down around .25-.5% from 5% and more.I had also been involved with the search for a new warehouse management system, playing the role of a superuser for the current system and acting as a resource for how we used the current system and what we would need from a new one.As a shipping associate member of the print crew, it was my responsibility to release sets of orders for fulfillment. Each book ordered received a paper pickslip with information for the pickers to use to find the correct book. The print crew printed these slips, monitoring the quality of the output to ensure that the barcodes and information are usable, as well as ensuring that all of the released orders get printed. Technical problem solving and computer skills were very key to being on the print crew, both with keeping the printers working well and with using the current warehouse management system. The print crew also handled order exceptions.The print crew also performed higher functions in the department, such as investigating books that aren't where they are supposed to be or that are listed as having one title when they are actually a different one. The print crew also does regular picking and packing duties.

I worked in the Journals Division, where I was responsible for posting the online versions of twenty academic journals to the web. The deadlines were daily, for articles being made available before they were printed, to weekly, monthly, quarterly, or annually, depending on the journal.The process began with converting the files the author submitted from LaTeX, Word, or other mark-up languages into SGML and (later) XML. I would check the files for missing items (graphics, tables, PDFs, etc.) and then begin to run several scripts on the data to generate the necessary files for online posting. My solid troubleshooting skills were key at this stage, since error messages weren't very helpful in tracking down where the markup had issues.Once these files were ready, I'd upload them to a test server, where I would help check the accuracy of the display, clicking links and making sure everything seemed to be in order. Once the editorial production group gave the okay, I would send the information to the live server, where subscribers could then access the articles. I would also help with typesetting pages on occasion, making edits based on feedback from editorial and production.I played a major role in cleaning up old data for the switch to a new hosting service and platform, and I helped develop the production steps for working with the new system. I would also be the person chosen to give an overview of the electronic production process to people visiting the Press from the journal offices.I was downsized from my position after several journals decided to end their contracts with the Press.