Jed Brundidge

OVERVIEW

• Work with product owners to design and develop new features for our flagship application.
• Work with QA to resolve bugs found during testing.
• Participate in all scrum ceremonies for agile development.
• Develop and maintain scalable, reliable, and efficient software solutions by collaborating with cross-functional teams,
• Analyze requirements, propose innovative technical solutions, and participate in the full software development lifecycle.

DAY TO DAY WORK

• Bug Triage - Solving complex problems is the main focus for my day to day tasks. I work with QA and utilize cross-functional communication to determine the exact issues that need to be addressed and then come up with solutions to the bugs that have been discovered through testing.
• Maintenance - Part of my days are spent on maintenance tasks. These tasks would included reviewing code for pull-requests, fixing existing code that can be refactored to adhere to our more modern design and patterns and contribute to wiki resources.
• Scrum ceremonies - Scrum ceremonies are an important part of agile development and I routinely participate in sprint retro, backlog refinement, daily standup, end of sprint demo and story grooming.

OVERVIEW

• Designing and developing enterprise scale software using C#(.Net Framework and .Net Core), Sql Server, React.Js and Kafka.
• Work with 3rd party vendors to build integrations between the businesses on-premise hosted data and our cloud services.
• Participate in all scrum ceremonies for agile development.
• Work with stakeholders, leadership and cross-functional teams to move projects to completion.
• Designing and developing enterprise scale software using C#(.Net Framework and .Net Core), Sql Server, React.Js and Kafka.

DAY TO DAY WORK

• Development - The largest part of the workday would involve writing code. This could be writing new functionality, fixing bugs, writing unit tests, writing acceptance tests and extending current functionality. Stories are prioritized during bi-weekly sprint planning sessions and then specific work and challenges are discussed during the morning standup.
• Design - Design sessions were key to making sure our products were more maintainable and reliable. For new projects the overall architecture was designed through several meetings with enterprise architects. Specific api design was handled through meetings with the development team and would consist of conversations around which design patterns would be best for the issue, which libraries would be best to use for the issue and any pros and cons that might come out of the design decisions.
• Scrum ceremonies - As a company we developed software utilizing an agile philosophy. I routinely participated in sprint planning, daily standup, sprint review, sprint retro and backlog refinement. Some of the things we discussed during these meetings are technical specifics for stories, estimating effort, good/bad of the previous sprint, changes we could make to enhance our process and deciding priority of stories.
• Maintenance - Part of most days were spent viewing request logs and monitors. Some of the limitations between our older systems and the new cloud services we were integrating forced us to fx some errors by hand so we needed to keep an eye on our logs to make sure we were getting to all

• Referred major hardware and software problems and defective products to vendors and technicians for service
• Set up equipment for employee use, performed and ensured proper installation of cables, operating systems and appropriate software
• Developed training materials and procedures, and train users in proper use of hardware and software
• Regarded computer software and hardware operation resolved problems
• Troubleshot minor problems and reported larger technical issues.