Concrete and Apache Permission Issue

Permalink
We are experiencing a permissions issue with concrete5. We have a remote user that needs sftp/scp access to our web server's concrete installation. If I chmod -r 775 the concrete directory and do a recursive change ownership of the concrete installation to developer:www-data, the user can upload, edit, erase the files his team needs. The problem comes, however, as soon as the concrete installation itself starts modifying and making changes to the installation files. When concrete modifies a file, it appears to change the permissions on the file to 755 and change the user and owner both to www-data.

So my question is there a way to modify this default behavior of concrete? Or, is there a better way for the developer to upload entire custom written theme files, custom modules, etc. to the concrete installation folder.

Thank you for any assistance.