1. LandOffer
  2. Blog
  3. All articles
  4. How to Find Software Engineering Jobs at Banks Without Confusing Tech and Finance Roles

Job search

How to Find Software Engineering Jobs at Banks Without Confusing Tech and Finance Roles

Find bank software engineering roles by searching technology job families, then verify the team, systems, users, and deliverables in each posting. Separate hands-on engineering from finance and quantitative work by reading responsibilities rather than relying on titles.

10 min readLandOffer team

A bank can employ software engineers, security specialists, infrastructure teams, data engineers, and product developers alongside investment bankers, traders, risk analysts, and finance professionals. The employer’s industry tells you where the work sits; it does not tell you what you would do each day. If you search only for “software engineer,” you may miss relevant openings filed under technology, applications, platforms, or systems. If you search only “banking,” you may spend time on roles whose main work is financial analysis or client coverage.

The useful approach is to search the employer’s own technology vocabulary, then read each posting for the systems being built, who uses them, and what the role owns. Those details help distinguish hands-on engineering from financial work that also uses code, data, and mathematics. You can browse recent roles on LandOffer.ai, then verify every opening and its terms on the employer’s official careers site.

A candidate sorts role cards into engineering, quantitative finance, and business categories by reading the work described on each card

Start with technology and engineering career areas

Open the bank’s official careers site and look for career areas or job families before trying a single keyword. Common labels include Technology, Engineering, Global Technology, Software Engineering, Digital, Application Development, Infrastructure, Data, Information Security, and Cybersecurity. Some employers place technology under a line of business; others organize roles around capabilities or job categories.

The labels are not standardized. JPMorganChase, for example, presents Technology as a career area and describes software engineering, data science, machine learning, and AI as technology opportunities. Its software engineer program says engineers may join teams supporting the consumer business, wholesale business, or internal functions. That example shows why an engineer can work inside a financial institution without holding a finance job: the employer’s products and operations need software too.

Search multiple nearby terms rather than treating one label as exhaustive. Try “software engineer,” “software developer,” “application developer,” “platform engineer,” “systems engineer,” “data engineer,” “site reliability,” “cloud,” “developer productivity,” and “security engineer.” Use the employer’s spelling and regional terms too. A company may group the same technical work under “applications development” in one country and “digital software engineering” in another.

Citi’s careers search, for instance, currently exposes categories such as Applications Development, Applications Support, Architecture, Data Science, Digital Software Engineering, Infrastructure, and Information Security. This is a useful menu of search vocabulary, not a permanent taxonomy. Check the live page because categories, filters, locations, and open roles can change.

Read responsibilities before deciding what the role is

After a title catches your eye, identify the work rather than infer it. Look for the objects the team builds or operates: customer applications, internal platforms, APIs, payment systems, data pipelines, cloud infrastructure, risk systems, developer tools, or cybersecurity controls. Then note the verbs: design, implement, test, deploy, monitor, troubleshoot, maintain, model, advise, sell, reconcile, or analyze.

A posting that describes designing and testing services, reviewing code, deploying changes, maintaining production systems, and improving reliability is giving you engineering evidence. A posting centered on valuing instruments, preparing market commentary, advising clients, recommending investments, or executing transactions points toward a finance or business function. A role can include both technical and domain responsibilities, so one clue is not enough. Read the day-to-day duties, required skills, reporting line, and team description together.

Bank of America’s live software-developer search illustrates why that second read matters. The results may show “Software Engineer III” alongside “Linear Rates Technology,” or “Software Engineer II” alongside “Enterprise Risk and Finance Technology.” These labels suggest a technical role connected to a particular business domain; the title and organization name alone do not establish the exact work. Open the full requisition and inspect its responsibilities, required tools, level, location, and team context.

Posting signal What it can indicate What to verify in the full description
Software engineering, application development, platform, or systems A technical job family Whether the work is product development, internal tooling, operations, or a mix
Markets, trading, payments, risk, finance, or asset management in the team name A business domain or internal customer Whether you build systems for that group or perform its financial/business work
Python, Java, cloud, APIs, distributed systems, SQL, or CI/CD Technical tools or methods Whether they are central responsibilities or one item in a broad wish list
Quantitative strategist, investment research, portfolio analytics, or pricing Quantitative or financial work may be central Whether the role builds and operates software, develops financial models, or does both

Separate software engineering from quantitative finance

The boundary is not “uses code” versus “does not use code.” Many finance, research, and quantitative roles use programming every day. The more useful question is what the role is accountable for and how its output is used.

Goldman Sachs makes the distinction visible on its engineering careers page. It lists Software Engineering, Systems Engineering, Quantitative Strategists, and Cyber Security as separate areas under its engineering umbrella. The page describes software engineers building applications for internal teams and clients, working with business partners, or contributing to core platforms such as data engineering, machine learning, networking, and developer tools. It describes quantitative strategists as applying mathematics and programming to models, pricing, trading automation, data analysis, and related market problems. Both may involve sophisticated technical skills; their primary deliverables differ.

Use this distinction to guide your search, not to reject a blended role by title. Some software engineers work close to traders, bankers, or risk teams because those are the users of the systems. Some quantitative developers build production software as well as models. A quant research role may emphasize statistical research and market decisions; a quant developer role may emphasize implementing, testing, and maintaining the systems that support those methods. Read the requisition’s verbs and outcomes, then ask the recruiter what proportion of the work is software delivery, research, analysis, or business support if the description remains unclear.

The same caution applies to “risk.” A risk technology engineer may build data platforms, controls, or monitoring tools. A risk analyst may assess exposures, investigate exceptions, or produce reports. “Finance technology” can mean software used by finance teams; it does not automatically mean a finance analyst role. The department label is context. Your decision should follow the stated responsibilities and the team’s output.

Build a search that covers role names and domains

Use two search tracks so that you can find both broadly named roles and engineering teams embedded in a business area.

First, search by technical family. Combine your target title with the employer’s own technology categories: software engineer, software developer, application development, platform, infrastructure, data engineering, cybersecurity, machine learning, or site reliability. Add a specific skill only when it matches your experience, such as Java, Python, cloud, database, or distributed systems. Search a few variants independently; a portal’s keyword logic may not treat several terms as an “OR” group.

Second, search by domain plus a technical term. For example, try payments engineer, risk technology software, markets developer, finance platform engineer, trading systems engineer, or banking technology data engineer. Treat these as discovery queries. A result is relevant only after you read the actual work. If the portal returns business analyst or client coverage roles, refine the terms or use its technology career-area filter.

Use the employer’s filters for country, city, experience level, job category, and employment type. If location flexibility or work authorization matters to you, verify those requirements on the individual listing and application page. Search result summaries can omit important qualifications, location limits, or team-specific details. Save the requisition number, URL, location, title, and date checked in your own notes so that you can return to the exact opening.

A job-search worksheet connects technical keywords and team-domain searches to the specific requisition details a candidate should verify

Evaluate the team, systems, and users

For each promising opening, capture a short evidence record before deciding whether to apply. Start with the requisition ID, exact title, location, and date. Then write down the team or organization, the systems or products mentioned, the users or stakeholders, the main responsibilities, and the required technical skills. Separate what the posting states from what you infer.

For example, a fictional listing might be titled “Software Engineer, Enterprise Risk Technology.” The description says the team builds Java services and data pipelines that ingest control events, exposes APIs used by internal monitoring tools, and participates in production support. Those details support an engineering interpretation even though “risk” appears in the organization name. The listing does not tell you whether the codebase is modern, how much on-call work there is, or whether the team’s culture suits you. Those are separate questions for a recruiter or interview.

A second fictional listing might be “Quantitative Research Associate” and mention Python, pricing models, portfolio allocation, and research papers. It is technical, but the listed outputs point toward quantitative finance and research rather than a conventional software-product role. You might still want it if that is your goal; the point is to make the choice knowingly.

Use focused questions when the posting leaves a material gap. “Is this role primarily building and operating software, developing quantitative models, or a mix?” is more useful than asking whether it is a “tech job.” For a hybrid role, ask what the first six months’ deliverables look like, what systems the team owns, and how much time is spent writing and reviewing production code. Ask about on-call only if the description or team scope suggests production ownership; do not assume every bank engineering job has the same support schedule.

Compare openings without overreading the brand

Compare the actual role evidence across openings. Which one has the systems you want to build? Who are the users? Does the position own design and implementation, or mainly coordinate, advise, or analyze? Are the tools central to the job? What level and location are listed? What operational duties are stated? Do the required qualifications fit your background, and are they firm requirements or preferred experience? Use the posting’s own wording rather than assuming “bank tech” is more stable, better paid, more structured, or less demanding than work elsewhere.

Keep a small, repeatable search log

A simple log prevents a broad search from turning into a pile of nearly identical listings. For each employer and query, record when you searched, which career category and terms you used, the location filter, the requisition IDs worth revisiting, and why each one appears relevant. Mark a result “review” if the title is promising but the responsibilities are ambiguous. Do not treat a search result as an application or assume a saved job has been submitted.

Refresh the search regularly, especially when you are targeting early-career programs or a particular hiring season. Program pages, vacancy pages, and individual requisitions can have different eligibility windows. Check the actual application page for the role’s deadline, degree or graduation rules, location, and required work authorization. Goldman Sachs, for example, says its student recruiting evaluates applications across the season and directs applicants to check role-specific program details; those instructions are specific to that employer and track, not a universal bank process. A general engineering careers page can help you discover the team, but it cannot substitute for the current requisition’s terms.

When a role fits, tailor your resume to the documented work. Show relevant engineering outcomes such as services shipped, reliability improvements, data systems maintained, security controls implemented, or developer workflows improved. Explain the technical contribution and the scale or result you can substantiate. If the team serves a financial domain, show that you can learn the domain and work carefully with its constraints; do not claim banking or trading experience you do not have.

If you are unsure whether a bank role is right for you, you do not need to settle the whole question from the company name. Compare several current postings using the same evidence: responsibilities, systems, users, skills, and team ownership. That turns “I want to work in tech at a bank” into a shortlist of real roles you can evaluate. You can also browse recent roles on LandOffer.ai as one part of your search, then confirm each opening and its terms on the employer’s official careers site.

Sources and Further Reading

These official pages describe employer-specific terminology and examples. Job search pages and categories change; verify the current vacancy and location on the employer’s application page. The fictional examples are teaching scenarios, not real openings or candidate reports. This guide offers a way to classify and compare work; it does not predict hiring outcomes or make claims about compensation, culture, or working conditions.