HOME / ABOUT
FIG. A — PROFILE
About
Senior software engineer and technical leader — architecture, performance, security, and end-to-end delivery.
FIG. 03 — PROFILE
Engineering, end to end
Engineering leadership for complex products, platforms, and production systems.
I lead the design and delivery of production systems where product complexity, operational scale, and engineering quality meet. Across 10+ years, I have owned the path from requirements and architecture through implementation, verification, release, and handoff.
My experience spans backend platforms, product interfaces, APIs, integrations, automation, and engineering systems. The technology can change; the standard remains the same: explicit decisions, predictable production behavior, and teams that can extend the system after handoff.
FIG. 04 — DRAFTING LOG
Career log
Each entry logged with period, role, and scope of ownership.
2015 — 2019
Additional software engineering experience
Delivered PHP and frontend work across client projects, custom web applications, integrations, and internal corporate systems.
2019 — 2021
Flint Group — Lead Software Engineer
Built CRM, Laravel automation, queue-driven crawling, and deployment tooling for infrastructure and operations across approximately 10K websites.
2021 — 2024
MotoPress — Lead Software Engineer, Product Engineering
Owned booking-product architecture, REST APIs, authentication, permissions, documentation, releases, and long-term maintainability.
2024 — 2025
WPForms — Senior Software Engineer, Product Engineering
Delivered product and payment features in a commercial PHP product used on 7M+ active installations, including Stripe, PayPal, UX, reviews, and automated checks.
2025 — PRESENT
Growica — Senior Software Engineer
Owns CRM and operations systems for distributed web infrastructure, including React interfaces, provisioning integrations, 54 production-ready components, and production rollouts.
FIG. 05 — PRINCIPLES
How I operate
Three commitments that hold across every engagement.
FIG. 05.1
Make decisions explicit
Clarify constraints, define ownership, and document the trade-offs behind architecture, APIs, integrations, and delivery choices.
FIG. 05.2
Design for production
Use automated checks, smoke tests, monitoring, profiling, and real operational feedback to turn quality into a repeatable delivery system.
FIG. 05.3
Leave leverage behind
Build clear boundaries, useful documentation, and engineering habits that let the team move faster without depending on one person.
FIG. 06 — DOMAINS
Technical domains
The stack, by layer.
Backend & APIs
- PHP / Laravel / Symfony
- Node.js / Express / NestJS
- REST / GraphQL APIs
- SQL / Redis / RabbitMQ
- Queues / integrations
Product interfaces
- React / JavaScript
- TypeScript
- Admin UX
- Component systems
- WordPress / Gutenberg
Platforms & delivery
- Docker / CI/CD
- Cloudflare
- Provisioning
- Monitoring
- Release workflows
Quality & AI-assisted engineering
- Static analysis
- Automated checks
- Full-cycle testing
- Claude / Codex workflows
FIG. ✕ — ENGAGE
Looking for senior engineering leadership?
Architecture direction, performance engineering, and senior technical ownership for teams that need it. Let’s see if it’s a fit.
— EOF