Manage a department of approximately 13 employees. Two of them being Team Leads, managing majority of the team. Worked with Team Leads to create and uphold development department policies.Develop and document departmental policies. This includes work from home, out of the country work from home, and paid time off policies. Created guides expressing expectations on various work processes. This includes things like working through tickets, recording time it took to complete tickets, and how to perform the self-review portion of performance reviews.Restructured the Build Team's processes. Streamlined the teams' schedule by combining staging build and production build responsibilities to the same person the whole release. Created Production Build release schedule. Created all administration related elements in Jira related to the build schedule: "Releases" across four projects, Sprints for one project, tickets for each release.Created and managed development "On-Call" team, that operates on a weekly rotation. They handle being the development contact for maintenances, both planned and non-planned. They play a key role in patch releases. Created document explaining expectations of the team and some hints at common issues that arise.Manage Patch Releases. Patches typically were urgent code releases due to something being broke. Would do all of the administrative paperwork to document the incident(s) in a central place. Came up with a special Jira ticket type to consolidate information. Made checklists for what needs to occur during release. Scheduled a person from each department to be available for a given patch (I.T., Development, Database, and QA).

Team Lead was in addition to my Senior Software Developer role.Performed performance reviews for those I was the lead for. Approved time-off requests. Updated/created confluence documents for different coding and work standards.Created a new product from scratch that allows users to upload their own data into the system. This acts as a lighter version of the internal tool. First major Angular project for the company. Self-taught Angular v7+ for this project. Initial version was simply uploading files manually. Later enhanced it to automatically process files from both internal and external SFTP sites. After that, enhanced it further to accept data via webhooks and JSON instead of delimited files.Helped onboard new developers. This included configuring computers, applications, and making sure they are aware of development standards.

Specifically for one of our products "Data Loader", which allows the user to upload files for customer data without having to contact an internal team. This can be done manually, through an automated FTP processor, or via webhooks. There are was a time of maybe six months during this period where we had a Project Manager for this product, but once they left, it fell back to me.This was concurrent to my Senior Software Developer/Team Lead roles.In-charge of creating and developing requirements for the product. Manage priority of tickets. Demoed the project, received feedback, and created new tickets based on feedback. Created and managed projects related to the product. These projects were major big enhancements to the product. This included the FTP, Webhook, and "File Editor" projects.The File Editor project was designed for users to be able to view and correct uploaded data so that they didn't need to re-upload the file. This involves making sure data changes adhere to the relevant rules tied to what that field is mapped to. Users could then reprocess the file to pick up any changes to unprocessed data that may have errored or otherwise been skipped the first time the file was processed.

Enhanced our customer merge program to handle merging customers with different degrees of paid subscriptions. This involved accounting for different scenarios of paid, unpaid, and/or suspended. The merging of customers could not interrupt the serving of their subscriptions.Maintain most of the data-driven components of the platform such as:- internal method for ingesting files - customer service tool- customer identification / merging- invoices and renewal generation (based off a schedule)Handle priority/urgent tickets quickly. This was either in the form of data correction, program bugs, and new features.Perform Code Reviews following coding standards. Use "failed" code reviews as teachable moments to help elevate peers.

Certified for length of title. Position didn't 100% follow Scrum. Was in charge of Stand-ups and Estimation ceremonies. This position was in addition to my Software Development roles. Scrum Master role ended when our company bought another company and a full-time Scrum Master was appointed.

Maintained many different components across the large platform. Mostly dealing in finding bugs and fixing them. This allowed me to learn different aspects of the platform more deeply and get a more holistic view of the platform.Worked on our customer identification program, which works for both incoming data and existing data. When running over existing data, the results could be fed into another program that was used to merge like customers together with the resulting customer still adhering to any business logic.Worked on our customer service tool, allowing the customer service department to manipulate customers' data in many ways, while adhering to business rules. This included paid subscriptions.Performed various data fixes/corrections using SQL. Notable projects related to this included making sure data was in correct states for publishing audits.

Complete tasks managed from Jira as a Full-Stack developer. This involved finding and fixes bugs across a platform that contains many different types of apps. Back-end code was mostly Java and SQL, using Hibernate to communicate between the database and the server. Front-end was mostly HTML, CSS, JavaScript (Dojo and JQuery), and Java Servlet Pages.Developed a system to identify customers that are up for renewal for their subscribed magazine. This includes a similar invoicing system for those that were credited with a subscription. This involved learning more about business logic related to paid subscriptions. Leveraged Omeda's other products for allowing clients to select segments of customers and output them to send to printers for mailing or call lists.Finished a tool used for creating and managing Promotion Codes. Was handed the very early stages of it and added more complexity to it. Promotion Codes contain various meta-data that the user could define. If it was used in conjunction with paid products, users could setup different rates based on different criteria (such as geographical location). If it was used on a form, they could also put content to be displayed when the particular Promotion Code was used.

Assisting professor for the Programming Distributive Applications using Java class taught over the 2011 Summer Term. Includes topics such as exception handling, multi-threading, sockets, RMI, JDBC, and JSP.

Packet analysis using pattern recognition of known malware signatures. Maintain and tune a SourceFire IPS using community rules and creating new Snort rules from sniffed traffic. Train co-workers through the use of documentation and guides as to how to use the IPS and tips/guidelines to determining infection based on packet analysis. Packets come from all places on campus including resident halls, VPN, and the campus network.

Developed website "Activity Search" component for local Boys Girls club (Knox County Area Project) using a modified version of the Scrum methodology.Used Python/Django to add a component to an already established website to move a database of activities from a spreadsheet to a MySQL database.Allowed users to search and sort based on activities or organizations from the database and display them on the website.