Project Examples
Check out below some of the projects and other areas that I was involved in more detail while at MetTel!
Process and Systems Design
2019 / System Design for Hardware and Software Automation
I was heavily involved in every piece of our entire system design coordinating with our system architect, developers, and stakeholders to make sure that our solution met the business need.
Above are a few examples of the complex processes that my team and I developed that allowed us to scale our ordering systems.
Ranging from new orders for businesses, custom solutions, returns/exchanges of equipment and more. All of these systems were built from the ground up, and integrated with other legacy applications using Outsystems as our orchestrator.
API and 3rd Party Technical Documentation
A significant amount of time of my primary responsibilities involved communication with our external vendors for DIDs, and other technical documentation.
I would draft up our basic approach for the application design identifying the APIs needed from our vendors. This included designing inputs/outputs of our in-house APIs, and documenting responses through a tool like PostMan or Swagger.
Jira Automation, Ownership, and Documentation
Responsible for product backlog ownership, project management, and sprint planning. Following the Scrum framework we iterated on our SDLC processes, through ticket organization, backlog management, and coordinating product increment releases with external teams.
I optimized our processes within our software development lifecycle by leveraging the Atlassian suite to track our development. As the product owner I was responsible for managing our teams sprints, product backlogs, translating all of our business knowledge into deliverable user stories for our development team, and manage project timelines.
By leveraging different SaaS tools which included Slack, Confluence, Jira, and the Microsoft Office Suite, to document our API requirements, troubleshooting documentation, and step-by-step guides for our employees.
Product Acceptance Testing and Support
Each release needed to pass product acceptance testing and approval before release into production environments.
Due to the lean nature of our team size, I, along with my development team took on most of the responsibility of testing our product increment. Prior to internal release, we established our own development environments and tests before each release to our production environment.
Since all features were developed on a bi-weekly basis, we were required to act as tier 1 support during any production errors upon launch. This included drafting up our documentation for our code base, holding weekly Q&A sessions with other departments, and creating troubleshooting guides for employee support.
Christopher Sandoli 