I was Samuel's direct supervisor for almost two years at Appfluence, during which he was doing most of our frontend development and website management. He was quick to respond to requests from the rest of the team, and showed a get-it-done attitude that made everyone enjoy working with him. During most of his tenure at Appfluence, the main role Samuel performed was managing the infrastructure and content of our various websites. This includes deployment, backups, frontend development and some customization of publicly available extensions. Other than some cursory education on best practices and the general organization of our system, Samuel did not require a lot of upfront training to get started. On the other hand, he was careful to check with the rest of the team whenever our specification for the task at hand was vague or incomplete. Besides his main role doing frontend web development, Samuel also pitched in by running parts of our QA system. This job involves tedious and mind numbing tasks to be repeated on a regular basis. He did not, however, complain a single time, and he frequently discovered issues that we had not noticed during development, which speaks to his open minded and positive attitude. If it has to be done, it has to be done. On the other hand, Samuel has also done some server side work for us. For example, he was solely responsible for the Python library that allows users to connect to the Priority Matrix API with minimal effort. Similarly, during the last few months of his stay at Appfluence, Samuel also worked our web scraping system for lead generation and market research using Python. This is a task that requires careful attention to detail and a deliberate drive to keep improving the system until results are good enough. Often, there is no single best approach, and the ideal solution involves cobbling together several independent components to create a coherent system. It's harder than it seems at first sight. Last, but not least, Samuel has a friendly, afable personality that is easy to get along with. Being a largely distributed team, with 3 international locations and several remote workers, it is important to be responsive to requests from colleagues, particularly when the time zones are not aligned. Samuel frequently received unprompted praise from other team members on this regard, which is remarkable in my opinion. We miss him at Appfluence, and I'm sure he'll do great in his next role. I am more than happy to discuss further with any hiring manager that might be considering Samuel.

I was Samuel's direct supervisor for almost two years at Appfluence, during which he was doing most of our frontend development and website management. He was quick to respond to requests from the rest of the team, and showed a get-it-done attitude that made everyone enjoy working with him. During most of his tenure at Appfluence, the main role Samuel performed was managing the infrastructure and content of our various websites. This includes deployment, backups, frontend development and some customization of publicly available extensions. Other than some cursory education on best practices and the general organization of our system, Samuel did not require a lot of upfront training to get started. On the other hand, he was careful to check with the rest of the team whenever our specification for the task at hand was vague or incomplete. Besides his main role doing frontend web development, Samuel also pitched in by running parts of our QA system. This job involves tedious and mind numbing tasks to be repeated on a regular basis. He did not, however, complain a single time, and he frequently discovered issues that we had not noticed during development, which speaks to his open minded and positive attitude. If it has to be done, it has to be done. On the other hand, Samuel has also done some server side work for us. For example, he was solely responsible for the Python library that allows users to connect to the Priority Matrix API with minimal effort. Similarly, during the last few months of his stay at Appfluence, Samuel also worked our web scraping system for lead generation and market research using Python. This is a task that requires careful attention to detail and a deliberate drive to keep improving the system until results are good enough. Often, there is no single best approach, and the ideal solution involves cobbling together several independent components to create a coherent system. It's harder than it seems at first sight. Last, but not least, Samuel has a friendly, afable personality that is easy to get along with. Being a largely distributed team, with 3 international locations and several remote workers, it is important to be responsive to requests from colleagues, particularly when the time zones are not aligned. Samuel frequently received unprompted praise from other team members on this regard, which is remarkable in my opinion. We miss him at Appfluence, and I'm sure he'll do great in his next role. I am more than happy to discuss further with any hiring manager that might be considering Samuel.

I was Samuel's direct supervisor for almost two years at Appfluence, during which he was doing most of our frontend development and website management. He was quick to respond to requests from the rest of the team, and showed a get-it-done attitude that made everyone enjoy working with him. During most of his tenure at Appfluence, the main role Samuel performed was managing the infrastructure and content of our various websites. This includes deployment, backups, frontend development and some customization of publicly available extensions. Other than some cursory education on best practices and the general organization of our system, Samuel did not require a lot of upfront training to get started. On the other hand, he was careful to check with the rest of the team whenever our specification for the task at hand was vague or incomplete. Besides his main role doing frontend web development, Samuel also pitched in by running parts of our QA system. This job involves tedious and mind numbing tasks to be repeated on a regular basis. He did not, however, complain a single time, and he frequently discovered issues that we had not noticed during development, which speaks to his open minded and positive attitude. If it has to be done, it has to be done. On the other hand, Samuel has also done some server side work for us. For example, he was solely responsible for the Python library that allows users to connect to the Priority Matrix API with minimal effort. Similarly, during the last few months of his stay at Appfluence, Samuel also worked our web scraping system for lead generation and market research using Python. This is a task that requires careful attention to detail and a deliberate drive to keep improving the system until results are good enough. Often, there is no single best approach, and the ideal solution involves cobbling together several independent components to create a coherent system. It's harder than it seems at first sight. Last, but not least, Samuel has a friendly, afable personality that is easy to get along with. Being a largely distributed team, with 3 international locations and several remote workers, it is important to be responsive to requests from colleagues, particularly when the time zones are not aligned. Samuel frequently received unprompted praise from other team members on this regard, which is remarkable in my opinion. We miss him at Appfluence, and I'm sure he'll do great in his next role. I am more than happy to discuss further with any hiring manager that might be considering Samuel.