Full-stack engineer

All roles

Full-stack engineer

Engineering Tel Aviv Full-time #1042

Rust on the server, SvelteKit on the client, on a product real businesses open every morning.

About The Role

Torim is two processes behind one address: Rust owns the business logic and the database, SvelteKit renders every screen in four languages, two of them right to left. This role works across both. The code here explains itself, and it is expected to keep doing so.

What you would do

• Build a feature end to end — a migration, the query, the endpoint, the screen, and the tests that hold them together.
• Keep slot arithmetic in one place. Availability that disagrees with itself is the failure this product cannot have.
• Give Hebrew, Arabic, English and Russian equal standing — in the layout, not only in the strings.
• Review other people's changes properly: read the diff, run it, and say what you would have done differently and why.
• Stay with what you ship after it ships — the error rate, the slow query, the support ticket it caused.
  
  

• Three years or more writing software people depend on, and at least one system you stayed with long enough to regret a decision inside it.
• Rust on the server, or a typed language you would happily move from — this is axum, sqlx and tokio, with async as the default rather than an add-on.
• A component framework on the client: this is Svelte 5 with runes, and SvelteKit's server rendering and form actions. React or Vue is the same job in different words.
• SQL you write by hand. There are no query macros here — every call is a runtime `sqlx::query`, so the compiler does not check it and the test that exercises it is not optional.
• Postgres beyond `SELECT`: indexes, transactions, an exclusion constraint, and a query plan you read when something got slow.
• HTTP as a thing you actually know — status codes, cookies, caching, SSE, and what a reverse proxy does to a request.
• Hebrew and English at working level.
  
  

• Rust in production — axum, sqlx, minijinja, or anything that made you learn where the async runtime bites.
• Tailwind, and a design system expressed in tokens rather than in class names.
• Playwright, or browser tests you actually trusted.
• Calendars, timezones and recurrence — here that is chrono-tz, Asia/Jerusalem, and festivals that move opening hours.
  
  

• optional LinkedIn profile For example linkedin.com/in/your-name CV Drop a file here, or tap to choose one PDF or an image, up to 5MB. Anything we should know
• optional A few lines about you, or a link to work you are proud of.