Solutions Architect

What you would own, end to end

You own the Blueprint. A client has committed to a discovery engagement and agreed to a structured scoping process. You run that process and produce the deliverable the studio's entire build depends on: a Blueprint document that specifies what we will build, how it is architected, what it will cost, and what is explicitly out of scope. Nothing ships without this document being right.

That means sitting with the client's actual workflow, not the idealized version they described in discovery, and making decisions about where to start and what to leave alone. A notary's intake process might have seven steps; the correct first build might address two of them. Getting that scope wrong costs the build team weeks and costs the client trust. Getting it right means a first release that works, ships on time, and earns the next phase.

The work and why it pulls

The problems the studio solves are operational: paper forms that should be digital, inboxes that should be queues, spreadsheets that should be databases, and every one of those has an AI layer that could turn a three-step manual process into one. The Architect's job is to look at the whole picture, decide what order to build it in, and make the platform and integration decisions that keep the team from rebuilding anything six months later.

The work is technically demanding and interpersonally precise. A messy workflow has usually grown to accommodate the people who run it; understanding what is essential and what is accretion requires asking good questions and being willing to deliver a scope that is smaller than the client hoped for. The discipline to keep a first release small and correct is harder than designing a comprehensive system, and it is what separates a Blueprint that ships from one that stalls.

In your first months, expect to run a Blueprint engagement end to end: discovery facilitation with the client, architecture documentation, platform and integration decisions, and the fixed-price quote the build team holds to.

Who you would work with and where it leads

The Architect works at the seam between the client discovery process and the engineers who build. You take the confirmed problem, make the scope and platform decisions, and hand the build team something they can execute without constant clarification. The quality of that handoff determines the quality of the build.

The role grows toward leading the technical strategy across multiple active builds, setting the platform standards the studio builds on, and shaping how the studio approaches new verticals. If you want to be the person whose architectural decisions determine how an entire category of Island businesses gets its operations updated, this is that track.

You can take a messy, paper-based workflow and shape it into a scope and an architecture that a build team can execute. You are technical enough to size a build correctly and disciplined enough to keep it small. You know where a design will break before it does.

How to get in touch

This role is one we are growing toward. Email careers@entoura.studio with a note about your background. Strong candidates stay in mind as the studio grows. If the fit looks right when the role opens, you will hear from us.