logo[мetahunt]
> Djinni
senior

Backend Engineer

format:Remotecompany:Outstaff
pythonsqlpostgresql
test task:no
> full description

We build engineering teams for product companies in the US and Europe. This role is for the work most backend adverts never mention, the code that decides where money goes.

 

What you would actually build. Services that take messy commercial data and turn it into a number somebody acts on. A recommended bid, a price, a credit limit, a reorder quantity. Then the unglamorous half that decides whether anyone trusts it: blocking the output when the margin feed is nine days old instead of falling back to a default, making sure an approved recommendation never overwrites a value a human changed five minutes ago, and putting the mismatch in a report before anyone discovers it the hard way.

 

What we need you to have done before. Python as your main production language. SQL you write yourself, with Postgres underneath. And at least one system where your arithmetic had money attached to it: pricing, bidding or auctions, credit and risk scoring, margin and contribution, forecasting, marketplace or advertising analytics. Statistical judgement matters more than statistical libraries here. Knowing how many observations you need before you trust a change is the job.

 

How this goes. You answer the question below. If it lands, you get a live session with our CTO, screen shared, no AI assistance, where you write a small roll-up with a margin cap and we talk about why you made each choice. We ask why three times. That session is the whole interview. No take-home, no unpaid test project.

 

We will also want something verifiable: commit history, an open source repository, a live product you can point at, or a referee who will take a call. One of those is enough. None of them is a no.

The question, and please answer it in your application. Tell us about one number your code produced that money moved on. What went in, how it was computed, and what happened the first time it was wrong.

 

Remote. Ukraine or nearby time zones. English has to carry a live technical conversation with a client who writes code himself and asks follow-up questions.