Nathan Breedlove

• I work in the Legal Organization
• I've created and maintained tools for Amazon Lawyers to manage and audit information & costs regarding legal cases.
• These tools also work with "Outside Counsel"s (3rd party Lawyers) and Firms. Often our Amazon Lawyers/employees will need to work with these Outside Counsels on specific Legal Cases.
• "Backlog grooming" a process where the team of Engineers dissect specific features into "units" or "stories" so that they can be meaningfully understood/scoped and estimated. These "stories" should contain all the information any given engineer needs to start work on it.
• I've served as "On Call", where our team of Software Engineers rotate on schedule. If our tools should break the On Call will be informed (either by Alarms or Customers). It is the duty of On Call to quickly investigate a bug or failure, investigate how severe it is, and code a fix.
• We also have "Design Reviews" where an Engineer on the team has Designed a Feature or new Tool, and presents their research and proposed solutions (with pros and cons listed) to the team for review. I've played both roles in this process. These require initiative from the Engineer to research the "problem statement": what are you trying to solve/fix? The Engineer often must also gather information from customers to acquire information and "acceptance criteria": if we make this tool for you, what MUST it do? Only after the Engineer understands what he is trying to solve in layman's terms can they then research and design the TECHNICAL solution (what software infrastructure/tools should we use? why type of database? if there is a 3rd party tool involved, you need to investigate their APIs and SLAs, etc).

This was a very short lived job. Schneider is an energy company, and this specific plant produced machine parts. I was hired to replace another Software Engineer who had created an app specifically to help the workers in that plant.

However this wasn't a "true" software job in the sense that I didn't have a team of engineers to work with. The job was also far too bureaucratic - I was required to partake in many meetings, but I had little to no utility in & out these meetings. And these meetings would often take majority of my time at the job.

In short I was being paid to be a paper weight, with little time to develop and maintain the app the previous Engineer had created. Turns out he left the position because of these same reasons.

Fortunately an Amazon Recruiter reached out to me and gave me a shot at the big leagues.

• Develop and maintain Software Applications for Enterprise Management (specifically for construction)
• Develop new features from start to finish (designing algorithm/database structure, implementation, testing, source control)
• Debug legacy code (often get on live calls with customers, either helping them use product, or discovering existing bugs in code- which I would immediately tackle and fix)
• Write technical and user end documentation
• Technologies/Languages used: Jira/Confluence, Sage X3, .NET Framework, C#, SQL, JavaScript, HTML, CSS, Angular, and Python.

• I've held many jobs throughout the years
• None with skills directly related to Computer Science
• However I've had experience with jobs that concern interpersonal skills, diligent work, and some management.