Pievienojieties
Atvērtās vakances
Mēs pieņemam darbā lēni un cilvēkus paturam ilgi. Ja neviena no tām neder, bet uzskatāt, ka mums vajadzētu parunāt, rakstiet tik un tā.
2 vakances
Senior Backend Engineer
Pilna slodzeHibrīdsTehranOwn the services behind our real-time and marketplace products end to end — design, implementation, deployment and the pager that comes with them.Pieteikties šai vakanceiWhat you would do
- Design and build backend services in Go and TypeScript, on PostgreSQL, for systems that stay up.
- Take a feature from a problem statement through schema, API, rollout and the metrics that say whether it worked.
- Carry the on-call rotation for what you ship, alongside the rest of the team.
- Review other people's code as carefully as you would want yours reviewed.
What we are looking for
- Five or more years building production backends, including at least one system you operated after launch.
- Fluency with relational data modelling — indexes, transactions and query plans are tools you reach for, not things you read about.
- Comfort with the unglamorous parts: migrations, backfills, timeouts, retries, idempotency.
- Enough English to read and write a design document; Persian for the day to day.
How we work
Three days a week in the Tehran office, two wherever you like. The team that builds a system deploys it and answers for it — there is no handover to somebody who has never seen the code.
Infrastructure Engineer
Uz līgumaAttālinātiRemote (CET ±3)A six-month engagement to harden how we deploy and observe what we run: build pipelines, backups that are actually restored, and alerts somebody would want to be woken by.Pieteikties šai vakanceiThe engagement
Six months, part or full time, extendable. This is a defined piece of work with an owner and an end state, not an open-ended seat.
What you would do
- Take our deployment path from a shell script that works to a pipeline that is boring — staged builds, health checks, one-command rollback.
- Put real observability behind the systems we operate: metrics, structured logs, traces where they earn their keep.
- Prove the backups by restoring them on a schedule, not by checking that the job exited zero.
- Write the runbook the on-call rotation actually opens at three in the morning.
What we are looking for
- Deep Linux, and the patience to read the logs before changing anything.
- Experience running services on plain machines, not only on a managed platform.
- An opinion about what should page a human and what should wait until morning.
Ir kaut kas jāuzbūvē?
Pastāstiet, pie kā strādājat. Godīgi pateiksim, vai esam īstā komanda tam darbam.
Sāciet sarunu
vai rakstiet mums uz hello@larsima.com
