About the role

We are looking for a Salesforce Revenue Cloud Developer to build a quote-to-cash solution, migrate Salesforce CPQ capabilities to Revenue Cloud, and support related integrations and data migration.

The mandatory requirements are 5+ years of Salesforce CPQ, Revenue Cloud training or hands-on experience, Apex, LWC, Flow, SBQQ data model knowledge, Revenue Cloud APIs and integration patterns, and upper-intermediate English.

For candidates based in India: At least 4 hours of overlap with US Pacific Time (PT) is required.

For candidates based in the USA: At this moment, we will not sponsor any new applicant for employment authorization or offer immigration support for this position (e.g., F-1 STEM OPT, F-1 CPT, J-1, E-3, O-1, or any other form of work authorization requiring immigration support or sponsorship).

What you will do

  • Rebuild product catalog, pricing, configuration and quoting in Revenue Cloud using Apex, LWC and Flow, working from the existing Salesforce CPQ setup.
  • Configure and build Revenue Cloud capabilities including Product Catalog Management, Product Configurator, pricing procedures and waterfalls, Dynamic Revenue Orchestrator (DRO), asset-based amendments and renewals, and Revenue Cloud APIs.
  • Deploy the solution through a repeatable pipeline and validate it end to end in test environments.
  • Build and support the Zuora order-to-billing integration, including error handling and reconciliation.
  • Map, load and reconcile CPQ contract, subscription and related data in Revenue Cloud, using the CPQ (SBQQ) data model to support the migration.

Must haves

  • Senior-level Salesforce developer with 5+ years of Salesforce CPQ experience, plus Revenue Cloud training or some hands-on Revenue Cloud experience.
  • A Senior CPQ developer who is working on a Revenue Cloud project that is still in flight is acceptable.
  • Salesforce development with Apex, LWC and Flow.
  • Revenue Cloud build exposure, such as Product Catalog Management, Product Configurator, pricing procedures and waterfalls, DRO, and asset-based amendments and renewals.
  • Strong working knowledge of the Salesforce CPQ (SBQQ) data model to support the migration.
  • Revenue Cloud APIs and integration patterns.
  • Upper-intermediate English level.
  • For candidates based in India: At least 4 hours of overlap with US Pacific Time (PT) is required.
  • For candidates based in the USA: At this moment, we will not sponsor any new applicant for employment authorization or offer immigration support for this position (e.g., F-1 STEM OPT, F-1 CPT, J-1, E-3, O-1, or any other form of work authorization requiring immigration support or sponsorship).

Nice to haves

  • Zuora integration experience and Zuora platform knowledge (strongly preferred for one or two of the 4 developers; not required on every seat).
  • Has delivered a Salesforce CPQ to Revenue Cloud migration (a plus).
  • Data migration experience (a plus).
  • Certifications: Revenue Cloud Consultant, Platform Developer I/II.

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