New Wave Devs

We are a senior engineering team hiring a backend engineer for a long-term role inside a client's product team. The client is a product company with a large user base. We share its name only with engineers who pass our technical call.

Engineers there shape what gets built, not only how, and work directly with product people.

The product's image and video generation runs on ComfyUI workflows, so hands-on ComfyUI is a must for this role.

What matters most to us
• You have built or run ComfyUI workflows yourself, with models deployed locally and custom nodes in the pipeline
• You have built a product that people use every day, and you can point to the parts you owned
• You think about the person using the product. You question a feature when it does not serve them and suggest a better one
• Experience with consumer products built around image or video is a strong plus

What you will do
• Build and run ComfyUI workflows for image and video generation
• Build and scale the backend services around them in Go
• Run background jobs reliably, with queues, retries and idempotent steps
• Turn new models into features people actually use

You should have
• Hands-on ComfyUI, at least on your own projects
• 3+ years of Go in production and 5+ years of backend work overall. 
• Experience owning parts of a production system end to end
• Fluent English for daily work with the client team

The role is full time, 40 hours a week, long term, with a working day that overlaps European business hours. Individual engineers only, no agencies.

How we hire: a call with our CTO about your ComfyUI work, your product work and your code, then a call with the client's team. Both are live, with screen share and without AI assistants.

To apply, open your application with a link to a ComfyUI workflow you built or ran, or one sentence on what it did. Applications without it will not be read.

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.

We are a senior engineering team hiring a backend engineer for a long-term role inside a client's product team. The client is a product company with a large user base. We share its name only with engineers who pass our technical call.

Engineers there shape what gets built, not only how, and work directly with product people.

The product's image and video generation runs on ComfyUI workflows, so hands-on ComfyUI is a must for this role.

What matters most to us
• You have built or run ComfyUI workflows yourself, with models deployed locally and custom nodes in the pipeline
• You have built a product that people use every day, and you can point to the parts you owned
• You think about the person using the product. You question a feature when it does not serve them and suggest a better one
• Experience with consumer products built around image or video is a strong plus

What you will do
• Build and run ComfyUI workflows for image and video generation
• Build and scale the backend services around them in Go
• Run background jobs reliably, with queues, retries and idempotent steps
• Turn new models into features people actually use

You should have
• Hands-on ComfyUI, at least on your own projects
• 3+ years of Go in production and 5+ years of backend work overall. 
• Experience owning parts of a production system end to end
• Fluent English for daily work with the client team

The role is full time, 40 hours a week, long term, with a working day that overlaps European business hours. Individual engineers only, no agencies.

How we hire: a call with our CTO about your ComfyUI work, your product work and your code, then a call with the client's team. Both are live, with screen share and without AI assistants.

To apply, open your application with a link to a ComfyUI workflow you built or ran, or one sentence on what it did. Applications without it will not be read.