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
Uberall

Lead (Backend) Software Engineer

  • Seen live on Uberall's site yesterday
  • Senior
  • Remote
Pay
Not stated
Location
Hungary
Open for
12+ days
First seen
Oct 23, 2026
Apply on Uberall's site (opens in a new tab)

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Uberall'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 Uberall, so its true age is longer.

Last checked Nov 3, 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

About the GEO Team

GEO stands for Generative Engine Optimization. The GEO team builds products that help multi-location brands understand and improve how they are represented, cited, and recommended across AI-powered search and answer engines such as ChatGPT, Gemini, Perplexity, and Google AI Overviews.

We are building backend capabilities that collect and analyse signals from rapidly evolving AI platforms, measure brand visibility, and turn complex data into actionable recommendations for our customers.

About the Role

As Backend Engineering Lead for Uberall’s GEO team, you will take on a hybrid role that combines people management with hands-on engineering . You will be responsible for the growth and effectiveness of the team, and you will also write code, review pull requests, and shape technical designs alongside them. On this team, leads stay close to the work. Hands-on contribution is a core part of the role, not something you step back from as the team grows.

You will shape the architecture behind our AI-search products, lead the delivery of new capabilities, and help the team navigate a fast-moving and technically ambiguous domain. Working closely with Product, Engineering, and other stakeholders, you will translate customer needs and emerging developments in generative AI into reliable, scalable, and maintainable backend solutions.

Your Responsibilities

People leadership

  • Lead and develop the GEO backend team. This covers hiring, regular 1:1s, performance conversations, and supporting each engineer’s growth.
  • Own delivery with Product. Shape priorities, make sure commitments are realistic, and remove blockers so the team ships steadily.
  • Build the engineering culture of the team: shared standards, constructive code reviews, knowledge sharing, and collective ownership of quality.

Hands-on engineering

  • Contribute regularly to design, code, and reviews as an active member of the team, not only as a reviewer or approver.
  • Guide the design and operation of backend systems that integrate with LLMs and AI-powered search platforms.
  • Establish robust approaches for evaluating the quality and consistency of AI-generated results.
  • Ensure that LLM-enabled capabilities are observable, testable, cost-efficient, and resilient to changing models and external providers.
  • Help the team manage the particular challenges of generative AI systems, including non-deterministic behaviour, latency, rate limits, data quality, and graceful degradation.
  • Stay informed about relevant developments in LLMs and AI search, assessing them pragmatically rather than adopting technology for its own sake.

Your Profile

Must have

  • Proven experience leading an engineering team with genuine people responsibility (hiring, 1:1s, performance, and delivery) while continuing to contribute code and technical design.
  • Motivation to stay hands-on as a lead, balancing management responsibilities with regular engineering work.
  • Strong proficiency in Kotlin or Groovy; proven coding skills in other JVM languages (such as Java or Scala) are a plus.
  • Solid experience with our core stack and architecture: Spring Boot, Hibernate, JUnit, MySQL, Elasticsearch, Docker, AWS and OpenAPI, applied within microservice and event-driven systems.
  • Hands-on experience building or operating production systems that use LLMs, generative AI, or AI-powered external services.
  • An understanding of how to evaluate and monitor LLM-enabled features beyond traditional deterministic testing.
  • Experience designing reliable integrations with third-party APIs and managing concerns such as cost, latency, rate limits, observability, and provider failure.
  • The ability to distinguish between an effective AI use case and one better solved with conventional software.

Nice to have

  • Experience with Python and LLM orchestration frameworks such as LangChain or LangGraph.
  • Experience with prompt management, retrieval-augmented generation, embeddings, vector search, or LLM evaluation frameworks.

No experience training foundation models is required; this is a backend engineering and engineering leadership role.

Something wrong with this posting?