Solution Architect
The Enterprise Architect will shape the digitization of Ford's global order-to-delivery processes through strategic roadmaps and innovative technical solutions. The role involves bridging the gap between business architecture, such as capability maps, and technical implementation, including PoCs and integration design. Candidates need a strong background in both functional business analysis and hands-on development with Java and cloud environments. This position requires deep experience with architecture frameworks like TOGAF and the ability to collaborate globally.
50k new jobs listed every day. Install TAL to find more jobs like this.
Experience
7+ years
Function
Engineering
Work mode
Onsite, India
Company
Tier 2
What you will work on
The Enterprise Architect will shape the digitization of Ford's global order-to-delivery processes through strategic roadmaps and innovative technical solutions. The role involves bridging the gap between business architecture, such as capability maps, and technical implementation, including PoCs and integration design. Candidates need a strong background in both functional business analysis and hands-on development with Java and cloud environments. This position requires deep experience with architecture frameworks like TOGAF and the ability to collaborate globally.
TAL's take
Strong scope for an Enterprise Architect at a global automotive major, though the role is heavily process-oriented.
Well-defined responsibilities spanning both functional architecture and technical implementation within the Order-to-Delivery domain.
Salaries at Ford Motor Company
19.0 LPA average
Based on 2 Grapevine salary entries for Ford Motor Company.
Other roles
2 - 4 years
25 LPA average
Range: 25 - 25 LPA
Other roles
10 - 12 years
13 LPA average
Range: 13 - 13 LPA
Must haves
- 7+ years IT experience
- 3+ years business/IT architecture experience
- 4+ years technical application development experience
- Experience with TOGAF or similar architecture frameworks
- Hands-on experience with Java, Cloud technologies, Angular/React
Tools and skills
Nice to have: agile, jira, aws, azure.
About the company
Established multinational automotive corporation, considered Tier 2 due to being a traditional manufacturer rather than a pure-play tech company.
Posts mentioning Ford Motor Company
Ford VS JP Morgan
Having offer with ford and JP morgan , Ford pays better than JPmorgan .. considering learning,WLB ,Hike & job security which one to choose
Offer choosing advice
I currently hold 2 offer Company 1 : 19 LPA fixed + 3L performance bonus Company 2 ( contracted to FORD Motors ) : 22.5 LPA fixed + 2.5 performance I didn't want to join company 2 as it's a small company and contract to ford and 4 days work from office. Should I negotiate with company 1 saying about company 2 offer, What to do if they are not able to match it ? Will it be bad of I still join company 1 if they don't match it ?
Ford GDIA (Unstructured Ingestion team) — sharing my experience for anyone considering this.
Was hired after a full-stack/backend-focused interview process. After joining, expectations quietly shifted to owning AI/ML pipelines and LLM workflows — things that were never evaluated or even mentioned during hiring. It felt like the org was still figuring out what kind of engineer it needed, and that confusion landed on the employees. The culture was heavily perception-driven. Stakeholder visibility and escalation optics often mattered more than actual engineering output. Engineers could deliver real work and still be flagged for "lack of ownership" because expectations kept shifting without documentation. What hit the hardest: being held accountable for outcomes of meetings I was never in. And once leadership's trust erodes, the performance process stops being about growth and starts being about building a record. One more thing — the joining bonus clawback is calculated on the gross amount, not what you actually receive after tax. That gap is significant and comes as a shock during exit discussions. If you're considering this team: ask very specifically during interviews what the actual day-to-day engineering expectations are. Don't assume the interview reflects the real role. It didn't for me.