Derek Meegan is a software engineer at Browserbase. He builds internal agent infrastructure and developer tooling, following customer engineering work that connected enterprise users’ needs with browser-automation products.[1]
Start with Serverless Browser Agents with Playwright, Lambda and Browserbase →
GitHub 
X · derekmeegan Career
Meegan studied information systems and economics at Temple University and began his career at Grant Thornton. His personal timeline lists work there from June 2021 to June 2025, followed by Browserbase. At Browserbase, he first helped define customer engineering and built tools for benchmarking, debugging accounts and capturing support knowledge. He now maintains an internal agent platform and cloud development environment.[1]
Contributions
His browserbase-lambda-playwright template runs Python Playwright code in AWS Lambda while the browser runs remotely on Browserbase. A request starts a job and returns immediately; DynamoDB stores the job’s progress, and a separate endpoint retrieves its status and result. Docker packages the Playwright runtime; the browser remains remote.[2]
Ideas
The template includes infrastructure definitions, example clients and separate scraper and status functions. That structure makes browser automation part of a service rather than a script that must finish while an HTTP request waits. Meegan’s portfolio also includes an agent that summarizes Uber Eats history and a serverless prediction-market monitor, reflecting an interest in connecting automated collection with a concrete user-facing result.[2][1]
Tools, writing & talks
Tools
Start here
A Python template with remote browser sessions, asynchronous jobs and persistent status tracking.
Start with the template if you already know Python and basic AWS services. Read the asynchronous architecture before deploying, then follow the listed AWS, Docker and Browserbase prerequisites.
Creator and repository owner[2]
Writing, research & talks
Browserbase's Derek Meegan explains why a 99%-per-step browser agent succeeds about 36% of the time over 100 steps. He walks through a health insurance portal architecture that uses deterministic tools, OCR checks and separated authentication.
Catalog workOriginal source