Work close to the decisions.
Jivark is small on purpose. That means less distance between the problem, the architecture and the person building it, and more responsibility earlier than a large delivery floor would give you.
Four expectations, applied to everyone.
These shape hiring, reviews and the kind of work we take on.
Think in systems
We want practitioners who ask what a change does to the rest of the platform before asking whether the ticket closes.
Own the outcome
Progress is measured by what the client can now do, rather than by how many items moved across a board.
Learn across layers
Salesforce, data, analytics and AI increasingly overlap. We expect people to understand the system around their specialty.
Communicate early
Raise risks before they become surprises. Client trust is part of the technical job.
Learn the system, own the work, lead the decision.
Titles matter less here than the kind of judgment you can be trusted with.
Learn
Understand platform fundamentals and the business context around your work.
Build
Deliver independently, with quality, testing and clear communication.
Own
Take responsibility for a workstream, its decisions and its production outcomes.
Lead
Shape architecture, mentor others and help clients make better decisions.
Current opportunities.
Roles are listed as they open. Every application is read by someone who has done the job.
Salesforce Developer
Not seeing your role? Send a note anyway. We keep strong profiles on file and reach out when a matching engagement opens.
Tell us what you have built.
We care about evidence of thinking: the problem you faced, your actual role in it, the trade-offs you made and what you would do differently now.
Curious about the work before the role?
Read how we approach architecture, delivery and client relationships, then decide whether it is the way you want to build.