We hire engineers who've been inside the problem.
ZSavvy does not hire people to learn enterprise marketing operations on client engagements. Every person we bring in has personally operated enterprise MAP or CRM infrastructure at scale — and understands the difference between implementing a workflow and engineering an operational system.
We are a small team by design. We expand when the right person exists — not when a job description exists.
Five things that matter more than your CV.
When we hire, it is because someone has demonstrated all five of these — not because they ticked boxes on a job description.
Not conceptual knowledge — actual Marketo, HubSpot, or Pardot instance architecture and operational management. You should be able to explain what broke in a specific instance and how you fixed it.
Salesforce configuration, SFDC-MAP sync architecture, API integration design with documented error handling. You understand the data model, not just the fields.
You design operational systems for durability and resilience, not for on-time delivery of a scope document. The question you ask is 'what happens when this breaks?' not 'when can this ship?'
You document what you build because you understand what happens to systems that aren't documented. Not because a manager requires it — built in by instinct.
We work on complex, ambiguous operational problems. The people who do this well are honest about the limits of their knowledge and systematic about how they fill those gaps.
We are explicit about this so you don't waste your time.
The things that make this a different kind of engagement.
Don't see a role? Tell us anyway.
We expand when the right person exists. Unsolicited introductions from deep practitioners are welcome — and occasionally result in engagements.
Send a brief note describing your background and what kind of work you want to do to careers@zsavvy.com. No CV templates. No cover letter format. Just tell us what you've operated and what you want to build.