Why Mechanical Orchard
Dear Mechanical Orchard Team,
I’m applying for any Software Engineer related role at Mechanical Orchard. In the past, I’ve worked with teams that partnered with Pivotal Labs (pre-AWS), and those experiences left a strong impression. I appreciated the disciplined, human-centered practices, the clarity of communication, and the practical craftsmanship in the codebases.
I want to be candid, I’m interested in your team’s approach to legacy modernization and the Imogen platform, but your engineering practices make Mechanical Orchard my top choice. Think of this as akin to an “early admission application”. I miss pair programming. I want to work at Mechanical Orchard, in any role related to Software Engineering. I expect to bring my experience in infrastructure, CI/CD, and reliability engineering to help your team deliver modern, behavior-driven systems.
I’m particularly impressed by the Extreme Programming layers; how practices work to support each other, are driven by clear principles, and those principles ultimately flow from values. I was fortunate to participate in early discussions about agile methodologies, even as BDD was born from TDD. These experiences shaped my appreciation for pragmatic, human-centered development guided by repeatable practices (pairing, TDD, continuous integration, small iterative changes) and grounded in shared values. So many agile methodologies focus on project management but overlook the developers.
In my work as a Staff/Senior Software Engineer, I’ve led full-stack projects and DevSecOps initiatives that align well with what Mechanical Orchard delivers. These highlights are especially relevant:
- Designed and implemented a hybrid, local-first video playback architecture (IndexedDB caching + background sync) that reduced streaming costs and improved reliability across hundreds of venues.
- Migrated deployment workflows to Docker and GitLab CI/CD, introduced reproducible devcontainers, and improved rollback and onboarding times for distributed teams.
- Worked closely with external contractors and stakeholders to re-scope and deliver product-focused features while keeping quality and maintainability front and center.
- I strive to write code that clearly communicates its intent to future developers, including myself.
Beyond technical fit, I value collaborative practices: pairing, constructive code review, disciplined testing, and short feedback cycles. I enjoy mentoring and learning from others. I believe in creating environments where engineers can do their best work without burning out. I have experience with both hybrid and remote work and am comfortable with travel.
I’d welcome a conversation about a role here and to discuss how my experiences would be an asset. Thank you for your consideration — I very much enjoyed past collaborations with teams like this and am excited to contribute directly.
Sincerely,
Matt Scilipoti
Matt Scilipoti
matts@scilipoti.name
github.com/mattscilipoti
