Member of Technical Staff II (C++)
Adobe · Bengaluru · 2–3 yrs experience · Posted 2026-07-06
Tech stack: C++
Apply on the company site · Get a referral for this role
Adobe salary & ratings · Adobe interview process · More live openings
About the role
The Opportunity Adobe Cloud Drive (ACD) brings a user's cloud content to the desktop as a native, mountable drive on macOS and Windows. Files show up in Finder and File Explorer as if they were local. Content streams on demand, edits work offline, and changes sync back to the cloud with conflict resolution. ACD is built on ACP.local (ACPL), Adobe's cross-platform client framework for cloud documents. ACD has shipped. Our focus now is keeping it reliable at scale. We're looking for an early-career engineer to own day-2 sustainment: sync stability, error paths, status icons, and performance. You'll work closely with senior engineers who will mentor you on the codebase and platform internals. It's a great role for going deep on cross-platform C++ and learning how a real sync engine works. What You'll Do Triage, reproduce, and fix bugs on the Windows and macOS clients. Focus on sync correctness, crashes, and recovery after restarts or network loss. Harden error handling in the CloudFileProvider. This is the process that bridges the OS file layer (macOS FileProvider, Windows Cloud Filter API) and Adobe's cloud services. Improve status icons, overlays, and sync-progress indicators. Users should always know if a file is cloud-only, downloading, pinned, or in conflict. Fix edge cases in the sync engine under senior guidance. Areas include listing, placeholder hydration, move/rename/delete handling, and conflicts. Debug issues in the SQLite layers, including database corruption and migration. Own regression triage and post-GA fixes: performance edge cases, crash follow-ups, and small enhancements. Keep CI/CD healthy. Keep test and fault-injection jobs green on Mac and Windows, and add coverage for what you fix. Update docs and runbooks as you close out issues. What You Need to Succeed A Bachelor's or Master's in Computer Science, Mathematics, or equivalent experience. 2-3 years of working knowledge of C++ and an interest in cross-platform, systems-level work. A solid grasp of data structures and algorithms. Familiarity with asynchronous, event-driven programming. A debugging mindset. You're comfortable reading logs, stack traces, and crash reports. A self-starter who works well on a strong team and follows through. Clear communication and a habit of writing tested, maintainable code. Nice to Have Exposure to macOS FileProvider, Windows Cloud Filter API, or any sync client (OneDrive, Dropbox, Google Drive, and similar). Experience with SQLite or other embedded databases. Understanding of sync engine design, conflict resolution, or three-way merge. Awareness of how clients use cloud services: REST APIs, ETags, retries, and change notifications. Experience on Windows, iOS, or UWP. Familiarity with CI/CD and automated testing for native apps.
Qualifications
- A Bachelor's or Master's in Computer Science, Mathematics, or equivalent experience.
- 2-3 years of working knowledge of C++ and an interest in cross-platform, systems-level work.
- A solid grasp of data structures and algorithms.
- Familiarity with asynchronous, event-driven programming.
- A debugging mindset.
- You're comfortable reading logs, stack traces, and crash reports.
- A self-starter who works well on a strong team and follows through.
- Clear communication and a habit of writing tested, maintainable code.
- Nice to Have
- Exposure to macOS FileProvider, Windows Cloud Filter API, or any sync client (OneDrive, Dropbox, Google Drive, and similar).
- Experience with SQLite or other embedded databases.
- Understanding of sync engine design, conflict resolution, or three-way merge.
- Awareness of how clients use cloud services: REST APIs, ETags, retries, and change notifications.
- Experience on Windows, iOS, or UWP.
- Familiarity with CI/CD and automated testing for native apps.
Responsibilities
- Triage, reproduce, and fix bugs on the Windows and macOS clients.
- Focus on sync correctness, crashes, and recovery after restarts or network loss.
- Harden error handling in the CloudFileProvider.
- This is the process that bridges the OS file layer (macOS FileProvider, Windows Cloud Filter API) and Adobe's cloud services.
- Improve status icons, overlays, and sync-progress indicators.
- Users should always know if a file is cloud-only, downloading, pinned, or in conflict.
- Fix edge cases in the sync engine under senior guidance.
- Areas include listing, placeholder hydration, move/rename/delete handling, and conflicts.
- Debug issues in the SQLite layers, including database corruption and migration.
- Own regression triage and post-GA fixes: performance edge cases, crash follow-ups, and small enhancements.
- Keep CI/CD healthy.
- Keep test and fault-injection jobs green on Mac and Windows, and add coverage for what you fix.
- Update docs and runbooks as you close out issues.