Job Description: Full-stack engineers remove the hand-off between the iOS and BFF lanes. One person builds the screen and the endpoint behind it, so a journey doesn't wait between lanes. In our definition, full-stack also means they can do quality engineering when the test queue backs up.

How we pair the fallback. Put an iOS-led and a .NET-led engineer on the same journey, so the pair owns it from screen to system of record. That's the same outcome a full-stack engineer gives us.

Added developers only move the delivery date if testing keeps pace. That's why full-stack here includes quality engineering, and why a story counts as done only when it's built and tested.

If there are fewer than four full-stack candidates, we fill the gap with T-shaped pairs rather than wait.

Technical environment

Mobile: native iOS app written in Swift.

Backend: .NET backend-for-frontend on Azure, including Azure Functions (for example, the identity function app).

Integration: Chanel APIM in front of the systems of record: Salesforce (profiles and permissions, tasks, notes, messaging templates, advisor, client and product relationships), Pioneer (client data and lookups), Product Catalog (Fashion, PEARL), Service Cloud and Data Cloud.

Environments: INT for integration, unit QA and end-to-end SIT; UAT for business acceptance; then production.



System-of-record data and configuration differ between environments.

Tooling: Chanel Jira for stories and sprints; Azure Dev Ops for repositories, pipelines and test cases; Figma designs from Chanel's design agency (AKQA).

AI-assisted development: the team uses an AI coding assistant with Jira acceptance criteria, Figma designs and the existing codebase as context. Every change is human-reviewed. Chanel reviews the code too, including with AI tools.

Ways of working: three-week sprints, feature-aligned pods, a daily US and India overlap, and a Definition of Done that includes testing.

General skills across all roles

Joining a live codebase in its final sprints and contributing in week one.

Working inside a client's tools, environments and access controls.

Treating testing as part of done: a story closes only when it's built and validated.

Disciplined AI-assisted development: small, reviewed changes, no hard-coded values, real contracts as context.

Transparent written updates for a team split across US Eastern and India time.

Fixed-fee discipline: raising scope questions and blockers the day you find them.

Working across the app-to-BFF contract, whatever your primary stack.
Additional Information: SPOC - Keerthi Prasad ()
Mandatory Skills - Under JD
Nice to have skills - Under JD
Clean Room Project - No

📌 Developer (India)
🏢 Objectwin Technology India
📍 India