Job search
eFinancialCareers Review for Tech Candidates: Separate Engineering Roles, Bank Titles, and Recruiter Listings
A current three-role public audit and completed Java-engineer decision distinguish engineering work, bank ranks, recruiter-client identity and availability evidence.
eFinancialCareers can surface useful software work in banks, fintech companies and investment businesses. Its harder decision is interpreting the lead: a Vice President title can accompany hands-on development, while a recruiter’s company name may identify the advertiser rather than the business where you would work.
We inspected a public New York software-engineer search and three selected US listings on October 20, 2026. Two Citi descriptions and one Selby Jennings advertisement show why responsibilities, location, employer identity and current availability need separate checks. We did not register, activate alerts, apply or contact a recruiter.
Publication update — October 23, 2026: The independently located Citi VP URL now returns HTTP 404, consistent with the earlier Job Not Found observation recorded here. The article still does not establish an exact requisition match to the board listing or the status of every similarly titled Citi position.

Keep a broader comparison through recent roles on LandOffer.ai. Whichever board supplies the lead, read the actual engineering scope before translating a title into your next career level.
What the finance focus adds to a technical search
The platform’s About page describes a financial-services careers site serving employers and candidates across multiple markets. That focus can put banking, trading, margin, financial infrastructure and related technology descriptions together in one discovery routine.
It does not make every search result a software-development job. A financial business can hire developers, production-support specialists, architects, product managers, analysts and technology-control staff. A technology label does not identify what you would build, operate or own.
Choose the engineering work you want to own, such as backend services, data platforms, front-end applications or infrastructure. Add the business domain when it matters. Someone seeking Java development can learn more from a trading-application description than from a broad finance title, while still needing to assess unfamiliar domain knowledge.
Our review does not measure the site’s share of US engineering vacancies, listing accuracy or employer response. The three selected pages support practical comparisons, not a verdict that every finance employer or recruiter uses the same titles and process.
Use location and task filters before interpreting volume
In the native browser, we opened the Software Engineer search, entered New York, selected the US city suggestion and ran the search. The resulting page displayed New York, NY, USA and a 50-mile distance setting. That made the geographic scope more concrete than a global keyword search.
The search exposed several advertisers and technical titles. We deliberately selected a Selby Jennings role from those results, then inspected Citi-listed roles separately through public discovery and the company’s board page. The Tampa AVP example was not a New York search match. It is included to compare role scope and location, not to imply the search returned only New York jobs.
We do not use the headline result count as a measure of distinct, suitable or active positions. A search can contain repeated titles, different levels, recruiter representations and roles outside your intended work. Use those distinctions to decide which leads deserve a full role review and which can leave your shortlist.
Public browsing worked without an account in this visit. The page also exposed Save, alert and sign-in controls; we did not activate them. A sign-in prompt was dismissed during research. This review therefore establishes public discovery and reading, not alert delivery, profile visibility or application handling after registration.
Bank VP and AVP titles still need an engineering reading
The inspected Citi Core Java Developer — Trading / Securities Lending — Vice President description concerned a New York trading application. It asked for Core Java development, Kafka, SQL and testing practices, alongside advising other developers and working with business stakeholders. The listed coding, testing and coaching responsibilities provide a more useful scope comparison than the VP label alone.
The Senior Software Engineer — Assistant Vice President — Margin Technology page described hands-on software development, REST APIs, Java/React/Python, testing and SQL. It identified Tampa and an in-office arrangement. Its introductory discussion of possible hybrid opportunities did not override that role-level location label.
These two examples demonstrate how coding and bank rank can appear together. They do not establish a universal conversion from AVP or VP to a technology company’s engineer levels. Compare decision ownership, technical complexity, expected independence, coaching, management duties and actual requirements.
A senior title can also contain responsibilities you do not want. If the work is primarily incident coordination, controls or stakeholder management, decide whether that fits your target rather than assuming every technical-sounding bank title has the same coding load. Read the description, and preserve any unresolved balance for a later role-specific discussion.
Worked audit: two bank advertisements and one recruiter listing
The table records what the public pages established and what remained open. It is not a representative sample or three verified active vacancies.
| Listing inspected | Coding and ownership evidence | Completed route and uncertainty record |
|---|---|---|
| Citi Core Java Developer, VP, New York; board ID 24914582 | Trading-application delivery, Java/Kafka/SQL and developer coaching | Citi named as advertiser; an independently located matching-title employer URL rendered Job Not Found, so current availability and exact requisition identity were not confirmed |
| Citi Senior Software Engineer, AVP, Tampa; board ID 24914633 | API and application development with testing and SQL | Role-level Tampa/in-office evidence retained; no employer-side submission route or current opening independently verified |
| Selby Jennings Senior Staff Software Engineer, Manhattan; board ID 24887478, reference PR/614433 | Distributed systems, backend infrastructure and architecture responsibilities | Recruiter advertiser verified; client unnamed; headline/body seniority and Remote/Hybrid conditions need clarification |
The Selby Jennings advertisement called the role Senior Staff Software Engineer in its headline but used Senior Software Engineer in the body. It described an unnamed financial-technology organization, not an engineering job at the recruiter itself. Its advertiser profile identified HR & Recruitment.
That evidence identifies the intermediary, not the client, reporting structure or contractual employer. Its Manhattan/Hybrid header and Remote/Hybrid body left permitted hiring states, required office days and the pay structure unresolved. We did not guess the client from the stack or salary range.
The two Citi pages supplied a different issue. Recent relative posting labels appeared alongside earlier anticipated closing dates in the body: May 15, 2026 for the AVP page and August 11, 2026 for the VP page. We did not resolve those conflicts by declaring the roles open or closed from the board alone.
An independently located Citi employer page with the VP title rendered Job Not Found and said the position was no longer open. We preserved that employer-page observation. We did not prove that its requisition identifier matched the board’s identifier, or test a signed-in board handoff, so it is not a blanket conclusion about every similarly titled Citi role.
A recent posting label is not an employer availability check
The audit found readable descriptions, a stale board URL that returned a 410 page, and the separate employer-page result. Those are different evidence states. A recent label, accessible description and Apply control do not prove that headcount remains available or that a candidate will receive consideration.
Save both the board identifier and any verified employer requisition. If you independently find a similar employer page, compare title, team, location and identifiers. Where they differ or cannot be matched, keep the relationship unresolved instead of merging records solely because the title looks familiar.
Likewise, do not count a repost as a new opportunity automatically. It may represent the same underlying role, a different level, a new requisition or a recruiter’s representation. We did not test how often advertisements refresh or how the platform assigns posting timestamps.
The practical outcome can be “requirements worth studying; application availability unresolved.” That is a useful research state. It keeps you from preparing a detailed application packet for a role whose current destination still needs verification.
Worked candidate decision: Java evidence without invented finance experience
Arun is fictional, a New York-area engineer with eight years of Java backend work, Kafka-based event processing and SQL. He wants to keep building software and can consider local office attendance. He has not worked on securities lending or margin calculations, and cannot relocate to Tampa for the inspected AVP role.
He completes a shortlist decision using the three audited descriptions. This is original candidate reasoning, not an employer assessment or a claim that he qualifies.
| Lead | Arun’s completed choice | Truthful proof or missing condition |
|---|---|---|
| Citi VP Java description | Retain as a scope reference; hold an application decision until the current employer requisition is verified | Java/Kafka work is relevant; finance-domain experience and the actual role’s requirements still need comparison |
| Citi AVP Tampa description | Remove from his location-compatible application list | He cannot meet this example’s location arrangement; shared technologies do not solve that constraint |
| Selby Jennings advertisement | Keep as a conditional recruiter lead, not a confirmed client opportunity | Ask about actual level, client disclosure stage, office geography and role scope before deciding whether to share a profile |
| Another posting with the same bank title | Do not merge or count it yet | Establish team, location and requisition identity first |
His completed evidence note reads:
I maintained a Java service that consumed order events through Kafka and wrote transaction records to SQL. I added duplicate-event handling, tests for replay and failure recovery, and operational documentation. I have not implemented a securities-lending platform or a margin-calculation model.
The note identifies concrete engineering ownership while preserving his domain gap. Arun can discuss why duplicate handling mattered, how he tested replay and what he did during failures. He does not relabel an ordinary order-processing service as a trading system or imply experience with financial models he has not built.
His role-level question is also finished: would the team expect him to implement and maintain services, own a domain design, coach engineers, manage direct reports or combine those responsibilities? A VP label alone did not answer it. He needs the current role’s actual scope before comparing it with his desired next step.
Arun’s result is one location mismatch removed, one bank scope reference awaiting current identity, and one recruiter lead held for clarification. He has not applied, received a recruiter introduction or disclosed a resume in this example. The decision saves application effort without pretending that public reading resolves private hiring questions.

Treat recruiter disclosure and candidate sharing as separate decisions
A recruiter listing can provide enough technical detail to deserve investigation while leaving the client undisclosed. Keep the recruiter’s name and reference with the lead. Do not replace that field with a guessed hedge fund, bank or fintech employer.
Before sharing information, establish what the recruiter needs and what will happen next. Client identity, representation permission, duplicate submissions, hiring location and compensation basis are material questions. The public advertisement did not settle them, and this review did not contact Selby Jennings to obtain answers.
Use a concise account of relevant work when you choose to begin that conversation. Share only material you are permitted to disclose. Public code, sanitized explanations and clear contribution statements can support a discussion without exposing employer repositories, credentials or client data.
Read the platform’s privacy policy and any recruiter-specific information before using account or sharing features. We did not test profile discoverability, retention, deletion, recruiter search or private messaging. Public browsing should not be described as a privacy test of an account workflow.
When eFinancialCareers belongs in a tech search
Use the site when financial-services engineering work fits your target and you are willing to read beyond rank labels. The inspected descriptions contained concrete coding and architecture work, but also location conflicts, unnamed-client information and availability questions.
Record the engineering output, advertiser, client where known, location conditions and both board and employer identifiers. Keep unresolved fields visible. Compare the work with evidence you can honestly explain, and verify the current destination before applying.
Explore LandOffer.ai alongside employer career sites and specialist sources. Keep leads that identify technical work you want, then verify the organization and current role before sharing an application.
Sources and Further Reading
- About eFinancialCareers, Software Engineer search and Citi board page.
- Citi VP Java board listing and AVP Margin Technology listing.
- Selby Jennings advertisement and advertiser profile.
- Independently checked Citi employer URL — native Job Not Found observation; exact board identity not established.
- Privacy policy — account decisions remain untested.
Checked October 20, 2026. Public reading only; no account, alerts, application, recruiter contact or private candidate-data sharing. Arun is fictional. Listings and employer pages can change.


