Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Amo

Data Engineer, Places

  • Seen live on Amo's site 2 days ago
  • Mid level
Pay
Not stated
Location
Paris
Open for
12+ days
First seen
Oct 23, 2026

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Amo's site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Amo, so its true age is longer.

Last checked Nov 2, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

What You’ll Do

  • Build pipelines for place and location-related data.
  • Work with noisy real-world signals and large geospatial datasets.
  • Improve quality, reliability, and observability of derived datasets.
  • Define metrics and feedback loops for data quality and attribution.
  • Prototype in Python, SQL, notebooks, or similar tools.
  • Integrate scoped production experiments with amo’s backend systems.
  • Run offline evaluations and A/B tests where relevant.

Must Have

  • Strong Python and SQL.
  • Production experience with Python or Scala.
  • Experience with PySpark, Spark SQL, Spark Streaming, Parquet, and Iceberg.
  • Experience with large datasets and data pipelines.
  • Experience with geospatial data, POI datasets, place matching, or similar real-world entity data.
  • Comfort with metrics, experimentation, and data quality measurement.
  • Comfort working near backend systems and reading production code.

Nice To Have

  • Experience in maps, mobility, local search, POI data, or geospatial systems.
  • Experience with ranking, recommendations, embeddings, or entity resolution.
  • Experience with Flink or similar stream processing systems.
  • Experience reading or making scoped changes in Rust-backed systems.

Life at amo

To ensure that everyone is set up for success within our way of working, we work together onsite 5 days a week.

We wanted to make sure coming to the office was as comfortable as possible for you

  • We chose a location in central Paris, near Opera (Metro lines 3,8,9 and RER A).
  • We have a beautiful Parisian-style office with high ceilings, balconies, and huge windows. So a lot of natural light!

Because life outside of work should also be stress-free, we cover

  • Health care (100% coverage).
  • Maternity Leave, Paternity Leave, Second Parent Leave (salary maintained at 100%).
  • Vacation days: 8-9 weeks (total) per year - (European summer? 🥹😎).
  • 5 weeks of paid time off (by the state);
  • 1-2 additional weeks (RTT, based on our company contract);
  • ~11 bank holidays.

We shut down entirely twice a year, two weeks in summer and one week in winter to allow everyone to truly recharge and to avoid prolonged slowdowns (especially in the summer). These pauses are part of your total vacation time, giving everyone a real chance to unplug and recharge. No Slack, no email, no FOMO.

Something wrong with this posting?