iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
JPMorganChase is looking for engineers who can do more than implement code: its Seattle Tech Center leader says they must understand business problems, work closely with stakeholders, write precise specifications for AI coding tools, and judge whether those tools’ output is correct. The shift changes the mix of engineering skills the bank emphasizes; it does not mean coding fundamentals are no longer important or that every team hires by one uniform rubric.
What changed in JPMorganChase’s engineering workflow?
In an Oct. 1, 2026 interview with GeekWire, Ture Armas described a move away from a strict handoff: business analysts provide complete requirements, wireframes, and acceptance tests, then engineers implement them. Instead, engineers are expected to work closer to the business, understand the domain, and shape specifications that AI coding tools can use.
That is specification-driven collaboration, not simply asking an AI tool to produce code. Someone still has to define what the system should do, make requirements testable, and assess whether the result meets them. Armas’s account describes a direction of change, not proof that every JPMorganChase team has adopted the same process.
| Work stage | Traditional requirements handoff | Specification-driven collaboration |
|---|---|---|
| Business context | Business analysts supply requirements before implementation. | Engineers work directly with business stakeholders to understand and model the problem. |
| Requirements and acceptance criteria | Requirements, wireframes, and acceptance tests arrive as a package for engineering. | Engineers help write precise specifications and checks for AI-assisted implementation. |
| Implementation review | Engineers implement against the supplied requirements and tests. | Engineers must evaluate AI-generated work against the intended behavior and agreed checks. |
| Responsibility for correctness | Engineers remain responsible for implementation quality. | AI can assist with implementation, but engineers still need to validate the result. |
What skills does JPMorganChase want in software engineers now?
Armas said engineers should “fall in love with the business problem” and described the capabilities once labeled soft skills as “the hard skills.” In context, that means the bank values technical judgment alongside the ability to clarify needs, communicate them, and work effectively with business teams.
#1 Best Overall
- Domain understanding: Learn what a business process needs to accomplish before turning it into software requirements.
- Clear communication: Ask useful questions, explain trade-offs, and make expected behavior understandable to colleagues and AI tools.
- Specification writing: Translate the problem into explicit requirements and acceptance checks rather than relying on vague prompts.
- Technical review: Inspect generated code and test whether it satisfies the requirements, including security and reliability expectations.
These skills complement rather than replace software engineering fundamentals. The interview supports a change in emphasis as AI handles more implementation work; it does not establish that coding knowledge is unimportant or that AI is replacing JPMorganChase engineers.
What does the Seattle hiring picture look like?
Kristine Baker, who GeekWire reported runs the center’s day-to-day work, said in the Oct. 1, 2026 interview that the Seattle Tech Center had more than 400 people and about 50 open positions, mostly in AI, cloud, and cybersecurity. Those are interview-reported snapshots, not audited workforce statistics or a guarantee that the roles remain open. Armas said Seattle has a deep talent pool in those areas and that the bank was receiving many responses per position.
Rank #2
The center opened in 2018, according to the same GeekWire report. Armas was named to lead it in July 2026 by JPMorganChase CIO Lori Beer, while continuing as CTO and head of Commercial Bank Lending Technology. He succeeded Mamtha Banerjee, who left the bank in March 2026. The Seattle lead role has strategic and community responsibilities; Baker handles day-to-day center operations, according to GeekWire.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What do public job materials indicate about AI-assisted engineering?
A Seattle Software Engineer III listing on JPMorganChase Careers surfaced with indexed text describing enterprise-authorized AI coding assistance. The posting text also says engineers should validate outputs through peer review, automated tests, and secure-coding standards. This is evidence from one role listing, not confirmation of a company-wide policy or a universal hiring rubric. View the JPMorganChase Careers listing.
Rank #3
How does Seattle fit into the bank’s broader AI work?
In a separate July 15, 2026 GeekWire interview, Lori Beer described an AI software infrastructure group anchored in Seattle. The group’s work includes routing workloads among the bank’s internal data centers, public cloud, and specialty compute, with attention to cost control and avoiding vendor lock-in. This is a distinct initiative; it should not be confused with Armas’s Seattle Tech Center leadership role. GeekWire’s report on JPMorganChase’s AI control layer provides that context.
At the bank-wide level, Jamie Dimon said on the company’s July 14, 2026 earnings call, as reported by GeekWire, that JPMorganChase had about 1,000 AI use cases, with about 50 significant ones. Those are attributed company figures, not an independently audited count, and they do not imply that the Seattle center owns those use cases.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
