Good questions
Straight answers to what hiring managers and clients usually ask before we work together. Don't see yours? Just ask.
Yes. I'm available immediately for 40 hours a week, on contract, contract-to-hire, or full-time Laravel and PHP teams, and I still take on project work. My most recent role was a contract with the engineering team at Integrity Express Logistics, where I owned the financial integrations for their Transportation Management System. That contract is complete.
I'm based in Pendleton, Indiana, on Eastern time, and open to remote. My résumé has the full history, and my recommendation letters are published in full.
Both. At Integrity Express Logistics I was on a software engineering team, and my code was reviewed by the Principal Architect. Some of my biggest changes went through dozens of review rounds before they merged. From 2013 to 2018 I was on the small team that built GroupVitals, where I introduced continuous integration, code reviews, and PHPUnit tests.
I've also built and run products on my own, like Insurance Storefronts. So I can own a project end to end, or pick up tickets in your codebase and follow your process.
It depends on the engagement. For a contract or full-time role, send me the role and the range and I'll tell you quickly whether it's a fit. For a fixed-scope project, I'll quote a fixed price after a short call about what you need.
Mostly Laravel and PHP applications: SaaS products, internal tools and admin panels, API integrations, payment and billing systems, and programmatic SEO. I do my best work where correctness matters, like money moving between systems, data syncing with third-party APIs, and subscription billing.
If it's a web application with a PHP back end, it's probably a fit. If it isn't, I'll tell you.
Yes, and a lot of my work has started that way. Qwire Clear was already underway on Laravel 5 when I joined and took the lead on the back end. Rebel Rates and Campus.Ink were procedural PHP apps that I rebuilt on Laravel. One Upwork client brought me in after letting their previous developer go, with a tight deadline, and we hit it.
I start by reading the code and getting it running, then give you an honest assessment: what works, what's risky, and what I'd fix first.
I'm available now and can start immediately, with 40 hours a week open for contract, contract-to-hire, or full-time work. Send me the role or the scope and I'll tell you the same day whether it's a fit. I reply personally, usually within a day.
Yes. Once the work is paid for, the code, designs, and anything else I build for you are yours, and the contract will say so. I don't hold code or access hostage.
I fit into however your team already works: Slack, email, Jira, GitHub, standups. On project work we'll agree on a rhythm up front, whether that's daily check-ins or a weekly written update. Either way, I flag problems when I find them, not at the deadline, and I reply to messages within a day.
Yes. I'm happy to sign an NDA before we talk details, and I keep client work confidential either way.
Yes. Many of my clients aren't technical. You tell me what you're trying to achieve, and I'll explain the options and tradeoffs in plain language, show you working progress as we go, and handle the technical side.