We’re a senior US-based product team building clean, scalable platforms for US and Canadian clients. We’re looking for a hybrid full-stack developer who can own features end-to-end — frontend to backend — and help us ship products the right way.

Our Vision

We’re building a tight, high-output team that creates modern, reliable software without bloated processes or corporate noise. The goal is simple: ship clean architecture, scalable systems, and products that clients can actually grow on. We move fast, think long-term, and care about quality.

What You’ll Bring

- Strong communication and independent execution

- Experience with React / Next.js

- Backend experience with Node.js or Django

- Solid understanding of APIs, databases, and scalable systems

- Ability to align with US time zones

If you want to build serious products with serious people, let’s talk.

When a content type has revisioning enabled, edits performed through the Drupal UI correctly create new revisions. However, updates made via the REST API (PATCH/PUT) modify the current revision in place and do not automatically create a new revision, unless explicitly programmed.

This behavior contradicts the intuitive and UI-based expectation that every content modification on a revision-enabled entity results in a new revision, regardless of the update channel.

What do you think, wouldn't the expected behaviour be to create a new revision for revision enabled content on Rest API PATCH request?