Skip to content
Salvatore Capone

About

Who I am, how I like to work with people, and the skills behind the products on this site.

Download résumé PDFView HTML résumé
LinkedInGitHub

Background

I’m a Lead Software Engineer in Charleston, SC. I’ve spent more than a decade building production software, DoD naval systems, enterprise CMS work for Fortune clients, and API-first products at Hello Alice.

Outside the day job I build things I’m into or that help day to day: a flag football operations platform, a private AI household chef, and a house-hunt board. I’ve also shipped a live marketing site and admin for a local rental business when a real operation needed something practical online. That’s how I stay close to real use, and keep shipping.

I’m curious about roles where building and explaining sit together: clarifying messy requirements, designing something people can trust, and proving it in working software. Solutions Engineering feels like a natural next chapter, not a reset.

Building software is half of it. Helping people use it is the other half.

I have not held a job titled Solutions Engineer. I have spent more than a decade building systems, sitting with clients, gathering requirements, showing what software can do, and shipping products that have to work when real people depend on them. That mix (build it, explain it, make it useful) is why Solutions Engineering interests me.

Discovery & requirements

Figuring out what people actually need, including the problem under the feature request, through conversations, on-site time, and cross-functional work.

Technical solution design

Turning real requirements into architectures that can ship: APIs, data models, CMS platforms, integrations, and paths that balance scope with reality.

Product demonstration

Showing what software can do with working product and clear walkthroughs, from sprint demos to enterprise presentations, not slide decks alone.

Integration & implementation

Connecting systems end to end: payments, email, partner APIs, secure pipelines, auth, and the workflows that make software useful after launch.

Technical communication

Making tradeoffs understandable for engineers, product folks, executives, and clients, without ditching accuracy.

Problem solving

Finding practical answers that balance usefulness, usability, security, and business needs, then building them.

Technical capabilities

What I actually use to ship, grouped by how it shows up in products, not by made-up skill scores.

Application development

Customer-facing and operator-facing web applications built with modern React stacks.

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Responsive web applications
  • Ruby on Rails
  • Payload CMS
  • Adobe Experience Manager (AEM)

Backend & infrastructure

API-first systems, data modeling, authentication, and cloud delivery.

  • REST APIs
  • GraphQL
  • PostgreSQL
  • MySQL
  • Supabase
  • Authentication & authorization
  • Row-level security
  • AWS (ECS, Lambda, S3)
  • Redis
  • Elasticsearch

Integrations & automation

Connecting payments, email, partner APIs, and business workflows into working products.

  • Stripe (Checkout, Connect, webhooks)
  • Email integrations (Resend)
  • Third-party APIs
  • Secure data pipelines / SFTP
  • Workflow automation
  • Payment processing

Deployment & development

Shipping and iterating production applications with modern tooling.

  • Vercel
  • Git
  • GitHub Actions
  • CI/CD consumption across environments
  • AI-assisted development (Cursor, Claude Code)
  • Application deployment