Jamstack Fuels Frontend Engineer Growth
Bucky Moore, Partner at Kleiner Perkins, on Jamstack's big upside case
This points to a shift in where software complexity lives, away from custom backends and toward the user facing layer where product teams compete. As deployment, auth, databases, and scaling get wrapped in managed services, more engineers can stay in React or similar tools and still ship full applications. That is why companies like Vercel and Netlify win by making front end developers productive without asking them to become AWS operators.
-
In practice, the job expands rather than stays narrow. A front end engineer can connect GitHub to a hosting platform, push code, get preview links, rollbacks, CDN delivery, and add search, auth, payments, or content through APIs, without managing servers directly.
-
The comparison is less front end versus back end, and more managed backend versus custom backend. Teams still need deep backend specialists for highly custom systems, but a large share of web work, docs, marketing sites, ecommerce fronts, and many product surfaces can now be shipped by frontend heavy teams.
-
This is also why AWS struggles to match the appeal of Vercel and Netlify at the product level. Cloud providers expose thousands of knobs. Jamstack platforms remove knobs, bundle the defaults, and make the common path feel like editing a React app and pressing deploy.
The likely end state is not that backend engineers disappear, but that more application building starts with the front end and only drops lower in the stack when a company truly needs custom infrastructure. That favors platforms that turn backend capabilities into simple building blocks, and it keeps expanding the economic importance of developer experience as a buying decision.