Work · Josh Lane

This is a selected record of systems I have built, organizations I have led, and public technical work. LinkedIn has the complete employment history.

EasyPost
2019–present
1. Chief Technology Officer
  2026–present
  Define and execute company-wide technology strategy across platform, data, infrastructure, and post-sales operations, aligning investment to leverage, margin expansion, and long-term growth. Own end-to-end customer experience after the sale, including reliability, support, and operational systems.
  Transform EasyPost from a fragmented product portfolio into a unified, decision-driven platform with strong data integrity and reduced complexity. Establish decision systems (rate intelligence, policy-driven routing, financial-grade data pipelines) as core platform primitives.
  Reallocate capital and engineering investment toward high-leverage, high-margin capabilities; eliminate low-return complexity. Partner with the executive team on company direction, including monetization, enterprise readiness, and risk posture.
2. Vice President of Engineering
  2025–2026
  I led a 130+ engineer organization across Core API, Enterprise, Platform, and international subsidiaries.
3. Senior Director of Engineering
  2024–2025
4. Director of Engineering
  2023–2024
5. Senior Engineering Manager
  2022–2023
6. Engineering Manager
  2020–2022
7. Senior Software Engineer
  2019–2020
  I built warehouse logistics, inventory, order integrations, and fulfillment software.
Across engineering management and platform leadership, I was responsible for infrastructure, finance systems, shared services, and developer tooling. That included redesigning financial data pipelines to shorten revenue-recognition time, decomposing a monolithic application into services, and improving reliability and developer throughput.
EasyPost leadership biography
Fastly
2016–2019
1. Senior Software Engineer, SRE
  2018–2019
  I worked on infrastructure development and site-reliability tooling.
2. Senior Software Engineer, Internal Engineering
  2017–2018
  I worked on internal data pipelines and the systems used to operate the platform.
3. Senior Software Engineer, API
  2016–2017
  I worked on backend APIs and web application firewall development.
The implementation work crossed Ruby, Go, Varnish, NSQ, Kubernetes, Chef, and Terraform. The more durable thread was the progression from product-facing software into the infrastructure and operational systems beneath it.
Engine Yard
2011–2015
1. Engineering Team Lead
  2012–2015
2. Software Engineer
  2011–2012
I contributed to the design and implementation of the Engine Yard Core API, extending it for multi-cloud support and technical acquisition integration.
The official Ruby client and command-line utility, ey-core, support application deployment and environment management, including a mocked mode for testing integrations without live API calls.
Engine Yard Core API client
HubSpot
2010–2011
1. Software Engineer
3M / Brontes Technologies
2008–2010
1. Software Engineer and QA Automation Engineer
Brontes was acquired by 3M in 2006, before my time there.
EMC
2007–2008
1. Quality Engineering Co-op
UPS
2005–2007
1. Supervisor
2. Package Handler

Speaking

Sapporo RubyKaigi

Sapporo, Japan · September 14, 2012 · Engine Yard

Release Early and Release Often: Reducing deployment friction

I presented Engine Yard’s approach to automated testing, continuous integration, and deployment. The main cloud codebase could be released at least daily while retaining a rigorous testing and release process.

Conference program and abstract · Event report (Japanese)

Software projects

My open-source tools and contributions and Labs experiments have their own pages.