Solutions Architect

What you would own

• Technical Discovery: reverse demos with a client's team, then the current-state and future-state systems maps that come out of them.
• The written requirements a build is signed off against, and presenting them at the solutions design meeting.
• The HubSpot architecture itself: object model, lifecycle definitions, pipelines, properties, and the integrations that feed them.
• Deciding what does not get built. A large part of this role is talking a client out of the thing they asked for when a simpler one works.
• Staying with the build through delivery, so the design is answerable to whether it actually worked.

What we are looking for

• You have designed and delivered real HubSpot implementations, not just administered an existing portal.
• You reach for native objects first and can say precisely when a custom object is warranted.
• You are comfortable in a client's messy current state: undocumented systems, a spreadsheet nobody mentioned, two sources of truth for the same number.
• You can explain a technical decision to someone non-technical without flattening it into a slogan.
• You write. The deliverables of this role are documents other people build from.

What would make this hard

• This is currently Roman's role, so you would be taking over work he has done himself and has opinions about. Expect that to be a conversation rather than a handover.
• Our clients are service businesses where attribution is genuinely hard. Clean answers are rare and you have to be able to say so.

How to apply

Tell us about the closest thing you have done to this. We read every application and we come back to you either way.