For every feature we usually have two developers working on it, one frontend and one backend, working on the same feature branch.
Would Jujitsu cause a problem in this context?
`jj git push` does an equivalent to `--force-with-lease`, so if there are remote commits that are later than what your current bookmark points to, it won't overwrite them. You can `jj git fetch`, it'll update your bookmark, and you can choose to put your new commits onto the updated sequence of commits wherever they belong.