About the role

We are looking for an Architect to own the target-state architecture and migration strategy for moving a quote-to-cash stack from Salesforce CPQ to Salesforce Revenue Cloud.

The mandatory requirements are experience with Salesforce Revenue Cloud, Salesforce CPQ (SBQQ), and Zuora Billing, 10+ years on Salesforce, lead architect experience on a Revenue Cloud or CPQ implementation, and an upper-intermediate English level.

What you will do

  • Own the Revenue Cloud target architecture: catalog, pricing procedures, context definitions, DRO and asset lifecycle, plus the data model and customer and account model.
  • Define the migration strategy: map CPQ (SBQQ) to Revenue Cloud, lead the install base migration (contracts and subscriptions to assets) with full reconciliation, and plan phased cutover with coexistence, go/no-go criteria and rollback.
  • Design the integration between Salesforce quote-to-cash and the external billing system (Zuora), covering the order-to-billing handoff, error handling, retry and replay, and reconciliation.
  • Set technical standards and run architecture reviews, maintaining the ADR log and reviewing code and configuration.
  • Build proofs of concept for the hardest scenarios (pricing procedures, DRO, Zuora handoff) and unblock developers directly.

Must haves

  • Senior architect with 10+ years on Salesforce overall, including lead architect experience on a Revenue Cloud implementation.
  • Experience in production implementation is preferred, and an in-flight CPQ-to-Revenue Cloud migration is acceptable.
  • Strong CPQ architect experience, even if newer to Revenue Cloud, is acceptable.
  • Tools: Salesforce Revenue Cloud, Salesforce CPQ (SBQQ) and Zuora Billing (the most important platform).
  • Target-state Revenue Cloud architecture design.
  • Migration strategy: data mapping, phasing, coexistence and cutover. Integration architecture across Revenue Cloud and billing, with Zuora Billing as the most important platform.
  • Setting technical standards for the team.
  • Deep Salesforce CPQ (SBQQ) knowledge: data model, price rules, product rules, QCP and twin fields, sufficient to decide what to rebuild, simplify or retire.
  • Subscription and usage-based quote-to-cash design: assets, amendments, renewals, co-terming and ramps.
  • Enterprise integration patterns: Platform Events, REST APIs, Named Credentials, idempotency and reconciliation.
  • Customer and account hierarchy design that separates selling, billing and deal scope across complex structures (agencies, parent/child accounts, multiple billing accounts).

Nice to haves

  • Salesforce Data Cloud experience, including integration with Revenue Cloud and billing.
  • Middleware design experience (e.g., MuleSoft).
  • Salesforce DevOps tooling for metadata and configuration data deployment.
  • Has delivered a Salesforce CPQ to Revenue Cloud migration (strongly preferred).
  • Has integrated Revenue Cloud or CPQ with Zuora, and has Zuora platform knowledge including subscription and invoice ownership, customer hierarchy and usage (strongly preferred).
  • Agentforce architecture for revenue use cases.
  • Certifications: Application/System Architect and Revenue Cloud Consultant; Certified Technical Architect (CTA) is a plus.

Perks

  • Growth without limits: build your skills through mentorship, internal TechTalks, challenging projects, and a dedicated annual learning budget
  • Competitive compensation: get recognition that reflects your skills and impact, with regular performance and compensation reviews
  • Flexibility: work 100% remotely with flexible hours that support focus, autonomy, and a healthy work rhythm
  • Meaningful, modern projects: build impactful products using modern technologies alongside global teams and leading brands
  • Collaborative culture: join a supportive environment with zero micromanagement where ideas are welcomed and contributions are recognized
  • Well-being & support: access local well-being programs and people-focused support tailored to your location

Didn’t find the perfect fit?

Subscribe to get notified about new roles that match your skills and interests.

Get role alerts

Hiring process timeline

We designed our hiring process to be fast, transparent, and convenient — so you always know what to expect and can move through the steps without unnecessary delays.

lightning-iconA quick note

After applying, keep an eye on your inbox — including your spam folder. Occasionally, emails from our hiring platform, LaunchPod, may land there.

1

Tell us about yourself

Submit a short application form.

2

Pass a quick test

Pass a 30’- 60’ test.

3

Record a short video

Introduce yourself on video to fast-track your application process.

4

Meet our team

Once you pass the video review, grab a spot on our calendar for a technical interview.

5

Get an offer

Welcome to AgileEngine!

FAQ

Have any questions?

What is the work format and schedule?

We are a remote-first company, so all our positions are remote. Schedules are flexible, but the main requirement is to have an overlap with your client’s schedule to ensure smooth collaboration. Specific details depend on the project and are discussed during the interview process.

What level of English is required?

We look for Upper-Intermediate (B2) proficiency or higher. Since you will be collaborating with international teams and global clients (including Fortune 500 companies), English is a part of your daily work.

Does AgileEngine provide work equipment?

It depends on your location. We provide equipment in Ukraine, Poland, Argentina, Colombia, Mexico, Brazil, Guatemala, Portugal, Spain, and India. In the USA, equipment is usually provided by the client; otherwise, you will be expected to use your own setup.

What opportunities for professional growth do you offer?

We support continuous growth through personalized development paths tailored to each expert. Also, you can expect:

  • An annual learning and development budget
  • Internal workshops, tech talks, and mentorship programs
  • Opportunities to switch projects or grow into new roles over time

What does a typical team look like, and what tools do you use?

Teams vary by project, but you’ll usually work with a mix of experts across different fields, along with a delivery or project manager who supports collaboration and onboarding.

For day-to-day work, teams commonly use tools like Jira and Google Workspace, along with communication platforms such as Google Chat. Depending on the client, you may also work with Slack, Confluence, Notion, or similar tools.

Need help?

Want more details? See full FAQ

If something doesn’t work or you have questions regarding your application process, drop us a line.

    Scroll to Top