Job Search Sourcing

Use this when someone wants to find real openings — a job, an alternance, a stage, an internship — rather than talk about their search in the abstract.

The two sources behave differently

They are not interchangeable. Picking wrong is the most common reason a search comes back empty or irrelevant.

Writing the query

The two sources want the opposite phrasing. This is the single thing to get right.

LinkedIn matches the job title literally. "data analyst" returns a full page. "alternance data analyst" returns zero, because no posting is titled that. Strip the contract word, strip the skills, strip the seniority unless it belongs to a real title. One or two words.

Welcome to the Jungle searches full text, so the contract word belongs in the query. Measured on the same city and role:

• query: "data analyst" → 1 of 20 rows was an alternance.
• query: "alternance data analyst" → 15 of 20 rows were.

So put "alternance" or "stage" in the WTTJ query, and never in the LinkedIn one.

Never put the city in query. That is what location is for, and one location per call.

Alternance, stage, internship

Neither source filters contract type at input, so the query only improves the odds. Always confirm on the rows:

1. Prefer WTTJ, with the contract word in the query.
2. Read type on each row: apprenticeship is alternance, internship is stage, full_time is CDI.
3. Keep the matches and say how many of the fetched rows survived — "15 of the 20 are alternances" is useful; silently showing two is not.
4. On LinkedIn, type will not help — it reports hybrid, on-site, or remote. Fall back to the title, which in France usually carries "Stage" or "Alternance" outright.

For a student in France, WTTJ is the better first call. For anything outside France, or a role posted this week, LinkedIn is.

Running the search

• Search one source first. Only run the second if the first came back thin or the user wants breadth. Every run costs money and time.
• If nothing lands, widen in this order: drop a word from the query → drop the contract filter → widen the location → try the other source. Say which you did.
• Deduplicate across sources by company plus title before presenting anything.

Presenting results

Always name actual roles. "I found 20 jobs, want to see them?" is a non-answer to someone who asked to see jobs. Lead with the count, then list the best four or five even when a results card is on screen — the card is a reference, your reply is the recommendation.

• Lead with how many are worth their attention, and how many rows that came from.
• Per role: title, company, location, contract type, salary if listed, and the link.
• Sort by fit, not by the order the source returned them.
• Flag anything posted today or closing soon.
• Missing salary means the posting did not list one. Never estimate one and present it as fact.

Rules

• Never invent a company, a role, a salary, or a link. Every row you show came from a run.
• If a source returns nothing, say so plainly and say what you would change. Do not fill the gap from memory.
• Do not fetch again with the same arguments hoping for a different answer.