Backend Engineer

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

Not verified

Was this benefit information wrong? Tell us.

Market context

U.S. role benchmark (BLS OEWS)

$116,543 U.S. median for this role

Projected growth (BLS Employment Projections)

+9.8% - Much faster than average

Matched to SOC 15-1252 - Software Engineering aggregate by role bucket.

Source: U.S. Bureau of Labor Statistics, OEWS, May 2024 and Employment Projections, 2024-2034.

Role

Role function

Engineering From the posting source checked Jun 20, 2026

Seniority

Mid From the posting source checked Jun 20, 2026

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Backend Engineer TLV Bringg is the infrastructure behind delivery operations for some of the world's largest retailers. Every day, millions of real-time transactions run through this platform. When it works, deliveries land on time. When it doesn't, customers feel it fast - and so do we. We're looking for a Backend Engineer who develops with AI as their primary tool - someone who sees where software engineering is heading and wants to be at the front of it. Someone who wants to set the standard for what great AI-driven development looks like - and do it on a complex, high-stakes system, alongside engineers who care deeply about what they ship. We offer a flexible Hybrid work from our TLV offices, located in Azrieli Towers. What You'll Do - AI-driven development moves from individual habit to shared engineering practice - you lead by example, and the team's baseline rises because you're in it. - Core services become more stable, faster to ship, and better understood - because you own them from architecture through production, not just the ticket in front of you. - Algorithm-driven components that power real-time routing and delivery decisions get sharper - you build them, evolve them, and understand what's actually happening under the hood. - Architectural decisions are better-informed - you're in the room, contributing to system design across a complex distributed environment where choices have real downstream consequences. - Own features end-to-end - from the first design conversation with product through to production, with full visibility

Read the full description at job-boards.greenhouse.io. FewerJobs shows a preview and links to the original posting.