Senior Solutions Architect
About Upsun (formerly Platform.sh )
Upsun is the cloud application platform humans and robots love. It is built for today’s hybrid teams, where AI agents write and test code and humans focus on solving the problems that really matter. Developers, DevOps engineers, and platform teams use Upsun to build, ship, and scale confidently without wrestling with backend infrastructure. We give you your time back. You get:
- Predictable performance, even at scale
- Secure, compliant environments by default
- Real-time observability and profiling built in
- Cloning, configuration, and provisioning in seconds
- AI-ready features that plug directly into your stack
The name says it all. "Up" means uptime, reliability, and acceleration. "Sun" reflects our follow-the-sun-support, a 24x7, globally distributed support team keeping the lights on while you rest. Our core belief is that software should power brighter solutions and greater innovation.
Upsunners are a remote, global workforce, and we thrive in a multicultural team. We are committed to open source and an open, welcoming environment. Our team spans the globe and the experience spectrum.
What's our commonality, our cultural fabric? A curious spirit and a thirst for knowledge; an eagerness for innovative ideas and cultures. We believe we can build anything together in an environment that frees you to do your best work.
Our values:
🌿 We make a positive impact.
✨ We aim for the stars.
💚 We care for each other.
Impact of a Senior Solutions Architect
As a Senior Solutions Architect, AI- Native SDLC, you will make Upsun Dispatch real inside our most important customers. AI helped engineers ship more code — it didn't help teams ship more product. Upsun Dispatch closes that gap, built on the idea that the workflow is the primitive, not the agent. Your job is to understand how customers ship today, design workflows and architecture that fit their environment rather than an idealized one, and prove it with working implementations.
You own the technical relationship across the full arc, before signature and after it. The model isn't the hard part, and neither is our platform — the hard part is the customer's reality: their branching strategy, their review culture, their security reviewers, the twelve-year-old monolith nobody wants to touch, and the unwritten rules about who is allowed to approve what. A generic platform doesn't survive contact with that. You understand it deeply enough to design something that fits, and you're technical enough to prove it rather than describe it.
This is a founding role in a young product line. The architecture you design in one account becomes the pattern we ship to every account. Early on, you'll be close to the first deployments, because that's where the learning is; as our delivery capability builds out, your weight shifts further toward the front of the cycle and toward the patterns that let others deploy.
What to expect
-
Win the Technical Decision: Own the technical relationship on your opportunities — discovery, architecture and security review, proofs of value, and the conversation where an engineering leader decides whether to trust us.
-
Grow the Accounts You Own: Expand from the first workflow to the second and third, inside both new logos and our existing customer base.
-
Build the First Working Version: Build workflows, custom steps, and integrations yourself against each customer's GitHub or GitLab, Jira or Linear, Slack, and existing CI.
-
Drive the Market Feedback Loop: Be the shortest path between a customer's problem and our roadmap — translating customer signal into structured input for product and engineering.
-
Make the Next Deployment Cheaper: Capture each deployment as a reusable pattern — a reference architecture, a workflow template, a documented approach that partners and other architects can run without you.
-
Technical Leadership: Handle security questionnaires, architecture reviews, com