I worked with Bryan to develop accounts-payable services for Divvy customers. As we worked together on a project to facilitate automated ACH transfers, he was instrumental in creating a robust design that would ensure data integrity and empower customers to identify and self-correct problems. He has an eye for detail and a strong ability to think through various scenarios to foresee potential problems. While continuing to contribute as an engineer, he took on the additional role of project manager and established a clear line of communication with executive leadership that enabled them to plan our releases with confidence. As our team expanded, he worked with our product manager to identify multiple "quick wins" that our team could take on in order to improve various friction points in the application and delight customers with new reporting and monitoring features. Whenever he sees an opportunity for improvement, he jumps right on it -- like when he saw an opportunity for an engineering internship program and, rather than just throw it out as a suggestion to upper management, immediately worked to get needed approvals and organization, and made it happen with just a few weeks. Along with the energy and innate business and engineering sense that Bryan brings to a project, he has a great sense of humor and seems always to have a smile. He is dependable and has your back. It has truly been a pleasure to work with him.

Bryan was one of a small group of people that were put on a really, really big payment project. Something Divvy had to have done, and done right, to continue to move forward with certain things. Bryan was building this without QA, doing all of that himself. And, he killed it. When I joined the team I was definitely panicked to learn when they wanted it out, and that QA hadn't been involved, but Bryan had everything covered. He worked tirelessly to deliver an amazing product, and there was no frantic dash to QA at the end as he'd done it all up to that point. Then, Bryan ended up moving over to a developer position, also on my team. He joined and quickly came up to speed. He continued to test all of his code thoroughly, testing better than my of the more senior developers. I always knew I could count on Bryan's code to be quality. He also would take the time to explain to me what he'd already tested, any hesitations he had, or uncertainties, and then would be there with me as I tested, going through his changes together. His hands on approach made things go so, so smoothly, and helped us all have better confidence in what was going out, as Bryan tends to get put on pretty impactful projects. Bryan is always willing to help out any way he can, from mentoring and volunteering to dig into weird bugs, to just taking ownership and going through the application himself, to understand it better and test it. He's someone I'd definitely want on my team again, and who I know will be amazing anywhere he works.

I worked with Bryan to develop accounts-payable services for Divvy customers. As we worked together on a project to facilitate automated ACH transfers, he was instrumental in creating a robust design that would ensure data integrity and empower customers to identify and self-correct problems. He has an eye for detail and a strong ability to think through various scenarios to foresee potential problems. While continuing to contribute as an engineer, he took on the additional role of project manager and established a clear line of communication with executive leadership that enabled them to plan our releases with confidence. As our team expanded, he worked with our product manager to identify multiple "quick wins" that our team could take on in order to improve various friction points in the application and delight customers with new reporting and monitoring features. Whenever he sees an opportunity for improvement, he jumps right on it -- like when he saw an opportunity for an engineering internship program and, rather than just throw it out as a suggestion to upper management, immediately worked to get needed approvals and organization, and made it happen with just a few weeks. Along with the energy and innate business and engineering sense that Bryan brings to a project, he has a great sense of humor and seems always to have a smile. He is dependable and has your back. It has truly been a pleasure to work with him.

Bryan was one of a small group of people that were put on a really, really big payment project. Something Divvy had to have done, and done right, to continue to move forward with certain things. Bryan was building this without QA, doing all of that himself. And, he killed it. When I joined the team I was definitely panicked to learn when they wanted it out, and that QA hadn't been involved, but Bryan had everything covered. He worked tirelessly to deliver an amazing product, and there was no frantic dash to QA at the end as he'd done it all up to that point. Then, Bryan ended up moving over to a developer position, also on my team. He joined and quickly came up to speed. He continued to test all of his code thoroughly, testing better than my of the more senior developers. I always knew I could count on Bryan's code to be quality. He also would take the time to explain to me what he'd already tested, any hesitations he had, or uncertainties, and then would be there with me as I tested, going through his changes together. His hands on approach made things go so, so smoothly, and helped us all have better confidence in what was going out, as Bryan tends to get put on pretty impactful projects. Bryan is always willing to help out any way he can, from mentoring and volunteering to dig into weird bugs, to just taking ownership and going through the application himself, to understand it better and test it. He's someone I'd definitely want on my team again, and who I know will be amazing anywhere he works.

I worked with Bryan to develop accounts-payable services for Divvy customers. As we worked together on a project to facilitate automated ACH transfers, he was instrumental in creating a robust design that would ensure data integrity and empower customers to identify and self-correct problems. He has an eye for detail and a strong ability to think through various scenarios to foresee potential problems. While continuing to contribute as an engineer, he took on the additional role of project manager and established a clear line of communication with executive leadership that enabled them to plan our releases with confidence. As our team expanded, he worked with our product manager to identify multiple "quick wins" that our team could take on in order to improve various friction points in the application and delight customers with new reporting and monitoring features. Whenever he sees an opportunity for improvement, he jumps right on it -- like when he saw an opportunity for an engineering internship program and, rather than just throw it out as a suggestion to upper management, immediately worked to get needed approvals and organization, and made it happen with just a few weeks. Along with the energy and innate business and engineering sense that Bryan brings to a project, he has a great sense of humor and seems always to have a smile. He is dependable and has your back. It has truly been a pleasure to work with him.

Bryan was one of a small group of people that were put on a really, really big payment project. Something Divvy had to have done, and done right, to continue to move forward with certain things. Bryan was building this without QA, doing all of that himself. And, he killed it. When I joined the team I was definitely panicked to learn when they wanted it out, and that QA hadn't been involved, but Bryan had everything covered. He worked tirelessly to deliver an amazing product, and there was no frantic dash to QA at the end as he'd done it all up to that point. Then, Bryan ended up moving over to a developer position, also on my team. He joined and quickly came up to speed. He continued to test all of his code thoroughly, testing better than my of the more senior developers. I always knew I could count on Bryan's code to be quality. He also would take the time to explain to me what he'd already tested, any hesitations he had, or uncertainties, and then would be there with me as I tested, going through his changes together. His hands on approach made things go so, so smoothly, and helped us all have better confidence in what was going out, as Bryan tends to get put on pretty impactful projects. Bryan is always willing to help out any way he can, from mentoring and volunteering to dig into weird bugs, to just taking ownership and going through the application himself, to understand it better and test it. He's someone I'd definitely want on my team again, and who I know will be amazing anywhere he works.