I have delivered multiple projects within ambitious timelines. One example of this was learning clojure alongside a mature codebase and delivering a new set of endpoints within a month in order to satisfy a key client. As a result of this I have become the go-to engineer for multiple codebases in multiple languages. I have cleaned up and taken ownership of large legacy codebases in the absence of the original contributors, maintaining 100% uptime. With my previous experience in QA I have designed data pipelines with an eye towards validation and testing. I approach challenging projects confidently and competently, ensuring a high level of performance and reliability.

My recognised technical expertise and ability to solve complex problems within tight deadlines has earned me strategic influence within the wider tech team. This extends to product managers where I have been able to set realistic delivery deadlines, with a discussion of what features were imperative, and what could be delayed in order to meet other business pressures. To guarantee that projects were properly deployed, coded to a high standard, and rigorously tested, I have taken a DevOps approach.

My technical excellence, strategic overview, and ability to take ownership of complex challenges that involve working across multiple technologies and departments means that at present my role is focused on working with the most important clients to ensure delivery of critical features. I am keen to expand this to take more of a leadership role alongside development in my next position.

I introduced QA at JustYoyo, a young startup in mobile payments. I inserted quality into the development and release processes, increasing both internal and external confidence in the product. I implemented an issue tracking system, used this to introduce quality gates before and after development activities, then automated a proportion of the test suite against the product's REST server.

I worked a split role between testing and development during the run-up to a major release, developing a django micro-service which delivered GCM and APNS push notifications. In doing this I familiarised myself with the back-end architecture, and was able to assess the unit testing practices that were in use. This lead to a more detailed understanding of the system as a whole, feeding back into my test strategy.

I instigated continual process improvement by introducing and chairing fortnightly retrospective meetings. Increasing the level of communication within the team also changed way we communicated across the company while helping me to refine the process and training around issue tracking.

As a progression from my first role at Mind Candy I brought quality into the tools development process, and streamlined manual tasks for greater efficiency. I created new background services to integrate first and third party tools. This reduced workload, removed manual steps and shortened iteration times.

I introduced BDD to the team, and formulated system-level tests for their web applications. For this I developed a new test framework: Fattoush. This streamlined test creation and made test deployment more reliable by allowing the same tests to be run either locally, or in parallel across an number of differing remote webdriver sessions, with a simple configuration change.

My base role involved writing and executing test cases and strategies for testing new features or adopting new technologies. I frequently put myself forward for projects where I could apply and expand my knowledge and skills. My ability to automate long and error-prone manual processes quickly saw my role expand to include scripting and test automation as well as writing tools for others around the business. I was tasked with the maintenance of a legacy automation suite, extending it to gather performance data, and then converting some manual test scripts to CodedUI tests.