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

Senior Backend Engineer

  • Seen live on Uberall's site yesterday
  • Senior
  • Remote
Pay
Not stated
Location
Brazil
Open for
12+ days
First seen
Oct 23, 2026

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 Role

As a Backend Engineer, you will be working on our location marketing cloud solution (SaaS) and be a part of a highly-skilled agile team. As an experienced and team-minded professional, you will have a voice in our daily stand-ups that will be recognized and essential in our daily business to provide the best software solution to our enterprise clients and partners.

Your Responsibilities

  • You will lead impactful and innovative projects within our SaaS solution
  • You will play an active role in designing and improving our overall software architecture
  • You will participate in the design, implementation, and execution of distributed services and APIs
  • You will collaborate closely with your team, other squads, and stakeholders like product management
  • You will contribute to the codebase with scalable, high-quality code and deliver solid coverage with automated tests
  • You will ensure outstanding availability and maintainability of our platform by evolving our architecture and tech stack, participating in code reviews, refactoring, and improving integration and delivery systems

Your Profile

  • You are highly proficient in Kotlin or Groovy, and proven coding skills with other JVM languages (such as Java or Scala) are considered a plus
  • You have proven experience in designing scalable software systems, ideally a successful SaaS product
  • You are familiar with containers, microservice architecture, event-driven architectures, cloud computing, and RESTful APIs
  • You have deep knowledge of most of the popular technologies like Spring Boot, Hibernate, JUnit, AWS, Elastic Search, MySQL, Docker, or OpenAPI
  • You are a self-motivated and independent engineer and bring creativity and the ambition to strive in a constructive and multicultural team
  • You have experience with agile methodologies and automated testing
  • You are a great team player with a positive and solution-oriented mindset
  • You are fluent in English, sufficient for success in a remote and largely asynchronous work environment

Something wrong with this posting?