1. LandOffer
  2. Blog
  3. All articles
  4. cord Review for US Job Seekers: Direct Messages, External Listings, and Agency Roles

Job search

cord Review for US Job Seekers: Direct Messages, External Listings, and Agency Roles

A bounded public search shows why US job seekers should check position location, company base, listing source, and the actual contact route separately.

9 min readLandOffer team

cord is worth considering for a US job search when a suitable position offers a named hiring contact you can message. Its public search also includes external listings and agency-managed roles, so the whole results list is not a directory of directly reachable employers. Read the position's work location separately from the company's base before deciding whether the opportunity belongs in a US search.

This review inspected public pages on October 21, 2026, including a New York software-engineering search and selected listing details. No account, message, application, or resume upload was used. LandOffer publishes this review and offers job-search tools. If you already browse recent roles on LandOffer, compare the particular position and contact route rather than treating another board's presence as a second confirmed opportunity.

Editorial illustration separating a company's map pin from the actual position's location

Read the listing type before choosing a contact route

cord's candidate product page promotes access to hiring teams in the UK, USA, and remote across Europe. Its search page distinguishes direct company positions, external positions found on the web, and agency-managed positions. Those labels matter more than a general promise of direct messaging.

A direct listing may show a named person, role, activity information, and a Message button. That gives you a visible contact route to evaluate. It does not establish that the person will respond, can resolve every hiring question, or has already reviewed your background.

An external listing is a discovery route whose original recruitment destination needs checking. An agency listing identifies an intermediary, so a useful first question may be which employer and requisition the consultant represents. Messaging a consultant about an unnamed client is different from speaking with the employer's engineering manager, even when both conversations occur inside cord.

During this review, message controls were observed but left untouched. Account requirements, message delivery, recipient access, and replies were not tested. The same boundary applies to external cards with a generic “Message Hiring team” control: the label alone does not verify that a named, active employer representative is reachable.

The New York search did not establish 29 US openings

The actual path was Browse jobs → New York → Software Development → Software Engineer. After loading completed, the public search displayed 29 positions: one direct, 28 external, and zero agency, with Responsiveness as the selected sort. No extra remote, salary, or sponsorship refinement was applied.

Those are observed interface counts for that query on October 21, not a complete US inventory or a count of independently verified openings. The zero agency count applies only to that search; a separate default-search agency example appears below. Initial loading placeholders were not counted as results.

The first two external cards in the New York view were Olo's Fullstack Software Engineer and MongoDB's Senior Consulting Engineer. Both displayed a New York company base alongside Remote in UK for the position. Only Olo's card is used in the worked comparison; its full description was not inspected.

This is enough to reject one shortcut: a New York directory or company-base field does not, by itself, establish a New York work arrangement. It does not establish why the search included those entries, either. This review did not test cord's matching algorithm.

Switching to the direct subset displayed Prolific's Senior Software Engineer. Its card reversed the apparent geography: company based in London, position hybrid in New York. That is a useful reminder that a UK company base does not automatically make a particular role UK-only.

Worked audit: position, company, and source stay separate

The following five deliberately selected observations illustrate different decisions. They are not a random sample, an error-rate estimate, or a ranking of employers. Four cord detail pages were inspected; Olo was a result-card inspection only. Original employer requisitions were not independently confirmed.

Inspected listing Company-base field Position evidence Source and completed reading decision
Google — Staff Forward Deployed Engineer, GenAI, Google Cloud, 443565 Mountain View, USA Hybrid in Warszawa, Poland; no fully remote option on the card Direct: a named contact does not turn it into a US role
Prolific — Senior Software Engineer, 476485 London, UK New York hybrid; body describes regular US-team/customer collaboration Direct: retain for further US-role review
Olo — Fullstack Software Engineer, 456967 New York, USA Remote in UK on the card External: do not classify as US-compatible from company base
IBM — Senior AWS Cloud Full Stack Developer, 482430 New York, USA on the card New York hybrid card, but detailed text describes UK public-sector work and UK clearance requirements External: hold the location conflict
Formula Recruitment — Senior Product Manager, 397060 London/UK context London hybrid; employer not named in the inspected detail Agency: distinguish the consultant from the eventual employer

The Google listing is the clearest company-base-versus-position example. Its company card and work location refer to different countries. A US-only candidate should not infer US remote permission from the company name or base.

The Prolific detail provides positive US-location evidence within cord. Its body says the role is based out of the New York office, approximately one to two days a week. The structured field says up to three remote days per week. Those descriptions should be clarified rather than silently converted into one exact attendance requirement.

The IBM detail needs a different outcome. Its text refers to UK public-sector clients and active UK Government eSC or eDV clearance, while the card labels the position New York hybrid. That discrepancy justifies a research hold. It does not authorize this review to decide someone's clearance eligibility or announce that the underlying role is definitely in a particular city.

For that external listing, the public links inspected included IBM's general website; an exact original employer requisition was not confirmed. A corporate homepage is not the missing job-specific confirmation. Keep the cord ID and title so a subsequent check can address the same record.

The Formula Recruitment detail names George as the consultant and marks the position as agency-managed. It describes the client without identifying its name. The body requests two onsite days in London, while the structured field permits up to two remote days weekly. Neither wording establishes a US work option.

Conceptual illustration of separate direct-employer, external-source, and recruitment-agency routes

Activity and responsiveness are context, not promises

A visible contact is useful because it tells you whom a prospective conversation would address. Prolific's inspected page identified Jake Hansen as a Talent Partner and provided a Message Jake Hansen button. Its response fields showed N/A at the time of inspection. There was no measured response from that person in this review.

Other pages displayed activity and responsiveness figures, but those displays do not predict an individual candidate's outcome. They may describe a different set of prior interactions from the one you are considering. This review did not verify their denominators, calculation windows, or current account-side meaning.

The practical distinction is between a route shown, a message sent, a reply received, and a hiring step agreed. Only the first was observed here. Review the information disclosure before accepting an incoming request; the conversation itself does not establish an agreed interview or offer.

cord's message-request help article, dated March 14, 2023, says accepting an incoming company request opens the conversation and gives the company access to your CV and contact details. That is dated documentation, not a fresh account test. Inspect the current disclosure before accepting; do not assume all profile information remains hidden during a conversation.

Worked candidate decision: one review target, one hold, three exclusions

This case is entirely fictional. Rory Nguyen lives near New York and is seeking a US-based backend or full-stack role. Rory has six years of Python API experience, some React work, and limited GCP exposure. Rory can consider two onsite days a week but is not seeking relocation outside the US. These preferences are illustrative, not a legal assessment of eligibility.

Rory applies those declared preferences to the five observed records:

Record Rory's completed decision What remains to do
Google 443565 Exclude from this US-only search because the position is Warsaw hybrid Do not replace its geography with Mountain View
Prolific 476485 Review further: New York work and a named company contact fit the search route Check current employer identity, technical fit, attendance, and the live disclosure
Olo 456967 Exclude under the displayed UK-remote restriction Do not assume “remote” includes New York
IBM 482430 Hold because the card and description do not resolve location consistently Find the exact employer requisition before preparing an application
Formula 397060 Exclude under the displayed London arrangement Do not count it as a directly named US employer

This decision produces one further-review target, one hold, and three exclusions. It does not produce one qualified application or one verified open requisition. Rory's limited GCP experience also stays visible rather than being rewritten as production ownership.

Rory's complete unsent example for the possible Prolific conversation is:

Hi Jake, I read the Senior Software Engineer listing on cord, reference 476485. My relevant experience is six years building Python APIs, with some React work and limited GCP exposure. The role's customer-facing product work is the part I would like to understand better. Could you confirm the current employer requisition and New York attendance expectation? The description mentions approximately one to two office days weekly, while the structured field says up to three remote days. I can consider two onsite days, so I would clarify that before proceeding. I would also like to understand the depth of GCP experience expected at entry. Thank you.

The message is an editorial example, not a real draft in cord or contact with Jake. It names the record, preserves the skill gap, and asks two decision-relevant questions without claiming an application, response, or referral entitlement.

An original offline record check verifies the five fictional routing decisions and rejects three mistaken shortcuts: using US headquarters as the work country, discarding a US position solely because its company is UK-based, and ignoring the IBM conflict. It checks this finite example only; it does not test cord's search, permissions, or hiring decisions.

Use cord where the contact route adds something

cord is most useful to a US seeker when the role itself fits the required geography and a relevant contact route is actually identified. Prolific's inspected New York listing demonstrates the kind of public evidence worth reviewing further. The Google and UK-remote examples demonstrate why company familiarity and broad location navigation are insufficient.

External discovery and agency conversations can still be useful, but evaluate them on their own terms. Confirm the exact external requisition, or identify whom the agency represents and what the work arrangement permits. Do not treat a generic button, checked timestamp, or company profile as that confirmation.

Before adding another search source, inspect a few specific roles and record position location, company base, source type, and unresolved questions separately. You can also browse recent roles on LandOffer and keep the same evidence standard across sources. Choose the route that gives you a relevant, verifiable next step.

Sources and Further Reading