Solutions Architect

Solutions Architect

• Influence. They can convince the customer that a certain architecture is going to be better for them. They can also convince Engineering that a specific architecture should become the "easy path" and worthy of extra investment.

• Polish. They can up-level guidance we currently give to a public-facing Standard. Thinks of the output of Solutions as a "product" that will be consumed by self-service customers that could later become larger sales-managed customers.

• Perspective. They connect the dots across the blog, documentation, product, and what customers are experiencing to increase activations.

• Technical depth. Their core job is curating a library of solutions on the Fly.io website and evolving it to balance what's hot in the market and our core business

If Sales org isn't running, how will a Solutions Architect operate within Fly.io? In many ways, its a "product lead Solutions Architect" role, so they will need to:

• Writing about, packaging, and publishing patterns (old and new) to the Fly website that we know about either from our customers or from our own Frameworks teams.

• Apply product-thinking to output of solutions. The solutions will be published on the Fly website so prospects can find the solution and apply it to problems they're facing.

• Partner with customer success to help sell solutions to customers. Iterate on solutions to determine which are more important to our customers.

• Partner with Frameworks teams to develop concrete implementations of solutions within respective frameworks. Relates these implementations to general solutions and architectural patterns.

Your work output will be:

• Publish architectural patterns and Solutions content on the Fly website for self-service; prefer 1 to many communications

• Curate existing content in docs and Frameworks blogs and Github in a manner that's oriented around solutions and patterns.

• Work with customers, potentially poc-ing patterns, as a part of Customer Success processes

Here's what you will not do:

• Not participating in pre-sales processes for now, but this will happen later as the capability of the sales organization grows.

• Create bespoke documents tailored per-customer. For now we want to think of solutions as a product self-service customers feel may be applicable to their problems. Out solutions are our products.

• "Run engagements." We aren't doing professional services and implementation currently. There can be one-offs where we build tools or pocs, but not at any large scale.

• This is not a meeting-heavy role. This is the "Architect" part. You will talk with customers, in service of the desired architecture and moving them toward it.