Caspar Green
Principal Architect, Integrity Express Logistics
Reviewed my code directly · Oct 2025 – Jul 2026
I am writing to recommend Frank Lindsay without reservation.
I am the Principal Architect at Integrity Express Logistics (IEL). I set the technical direction for IEL's software projects. With our Engineering Manager, I brought Frank onto our Software Engineering team in October, 2025 to help with the final build and launch of our new Transportation Management System, an Enterprise level application at the core of our company's business. I personally review his code, so my assessment is based on close, sustained, firsthand observation of his work over roughly the past nine months.
Frank owns one of the most demanding parts of our codebase: the financial integration layer that connects our platform to external accounting, document audit, and carrier-payment systems. This is code where mistakes cost real money and are unforgiving of shortcuts — accounts-payable and accounts-receivable synchronization, payment reconciliation, credit and debit adjustments, document synchronization, and the correctness edge cases that surround all of them. Over this period he has merged more than 110 pull requests spanning new features, defect fixes, and refactors, with an essentially perfect track record of seeing work through to completion. He didn't just maintain this subsystem; he built much of it, including the accounts payable and receivable dashboards our accounting team uses daily and the machinery behind them.
What distinguishes Frank, and what I can speak to directly as his reviewer, is his engineering rigor. When he built out our most critical third-party integration, he didn't stop at making it work — he validated the external API's specification against real production traffic, captured that traffic to make the behavior reproducible, and stood up a dedicated automated test suite so the integration could be verified. That instinct to make hard things provable is the mark of a senior engineer, and it is not common. He also has the temperament that correctness-critical work requires: several of his most important changes went through dozens of rounds of demanding review before I was satisfied, and he engaged with every round constructively and landed the work cleanly. He does not get defensive under scrutiny, but he does push back with ideas and alternatives where appropriate, and he does not abandon hard problems.
Beyond the headline features, Frank consistently does the unglamorous work that keeps a codebase healthy — timezone and data-correctness fixes, cleanup refactors, and test coverage others skip. He is reliable in the fullest sense: steady output, sound judgment about risk, and a completed-work rate that means when Frank picks something up, I stop worrying about it.
I would gladly work with Frank again, and I recommend him strongly for any role that values technical depth, ownership of complex systems, and the discipline to get correctness-critical work right. Please feel free to contact me if it would help.