{"id":908782,"url":"https://alion.io/job/epiminds-backend-engineer","title":"Backend Engineer","company":{"id":697152,"name":"Epiminds","domain":"epiminds.com","url":"https://alion.io/company/epiminds","size_band":"11-50","is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Teamtailor","truth_index":null},"role":"Backend","role_family":"Backend","seniority":null,"employment_type":"full_time","work_mode":"on_site","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["Stockholm, Sweden"],"countries":["SE"],"hiring_countries":[],"hiring_countries_total":0,"salary":null,"salary_estimate":null,"experience_years_min":null,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"Docker","optional":true},{"name":"GCP","optional":true},{"name":"Google Cloud Run","optional":true},{"name":"Google GKE","optional":true},{"name":"JavaScript","optional":true},{"name":"Kubernetes","optional":true},{"name":"Node JS","optional":true},{"name":"PostgreSQL","optional":true},{"name":"Pulumi","optional":true},{"name":"Redis","optional":true},{"name":"Supabase","optional":true},{"name":"TypeScript","optional":true}],"status":"live","first_seen_at":"2026-09-07T08:42:31Z","employer_posted_date":"2026-09-07","last_verified_at":"2026-09-30T08:35:30Z","board_verified":true,"closed_at":null,"days_open":23,"trust":{"level":"ok","repost_count":null,"flags":[],"days_open":23},"description":"About Epiminds\nWe’re building Lucy, an AI system that investigates marketing performance and carries approved changes through to execution.\nBehind that work is a backend coordinating model calls, external APIs, persistent state, and code running in sandboxes. We’re a small team in Stockholm building the infrastructure this product needs.\nThe Problem\nAgent workloads are difficult to predict. One request can become several parallel investigations. A task can pause for approval and continue later. A worker can disappear after an external API accepts a change but before the result is saved.\nRetrying may duplicate the action. Giving up may leave the work unfinished. Keeping everything ready reduces latency but consumes idle compute.\nThe system has to know what happened, who owns the next step, and what is safe to repeat-while keeping data isolated and costs under control.\nThe Role\nYou’ll own the execution infrastructure, data systems, and reliability behind Lucy.\nYou’ll work across application code, databases, and cloud infrastructure, taking changes from design through deployment and operation. Your decisions will shape how the product handles more work and recovers when things fail.\nWhat You’ll Do\nMake execution durable. Build scheduling, queues, leases, cancellation, and recovery for work that outlives an individual request.\n\nMake retries safe. Preserve execution state and prevent duplicate events from repeating external actions.\n\nRun agent compute efficiently. Improve sandbox startup, worker scaling, resource limits, and cleanup.\n\nBuild dependable data flows. Handle pagination, partial failures, changing provider contracts, and datasets that should be streamed rather than held in memory.\n\nMake failures explainable. Connect traces, logs, and cost data so the team can find bottlenecks and resolve incidents.\n\nWhat We’re Looking For\nYou’ve operated backend systems in production and owned their reliability. You understand database design, distributed state, queues, and the difference between a failed request and a failed operation.\nYou’re comfortable with containers and cloud infrastructure. You can explain what breaks under load, how recovery works, and when a simpler design is enough.\nOur stack includes TypeScript, Node.js, Supabase/PostgreSQL, Redis, Temporal, Cloud Run, GKE, Modal, Docker, and Pulumi.\nWhy Join Now\nExecution is central to the product. You’ll shape how agents run, how their work survives failures, and how infrastructure cost changes as usage grows.\nWhat we offer\nCompetitive salary and meaningful equity.\n\nHealthcare, retirement savings, and wellbeing support.\n\nOffice catering.\n\nHiring process\nRecruiter screening.\n\nTechnical task.\n\nCode interview.\n\nTrial with us in the office.\n\nWe welcome applicants of all backgrounds.","description_format":"text","description_chars":2779,"description_truncated":false,"requirements":{"experience_years_min":null,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":["Equity"],"hiring_locations":[],"hiring_excludes":[],"relocation_offered":false,"industries":["AI Agents","Marketing & Sales AI"],"lifecycle":[{"event":"open","at":"2026-09-14T15:07:56Z"}],"liveness":{"score":44,"band":"fade","label":"Fading","p_open":0.9,"p_active":0.493,"p_room":1,"age_days":22,"expected_fill_days":101,"reasons":["conf:76","win:early"],"computed_at":"2026-09-30T05:45:00Z"},"pay":null,"html_url":"https://alion.io/job/epiminds-backend-engineer","json_url":"https://alion.io/job/epiminds-backend-engineer.json","meta":{"generated_at":"2026-10-01T04:49:51Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","usage":{"tier":"crawler","counted_by":"address","units_charged":1,"used_today":4362,"day_limit":5000,"remaining_today":638,"minute_limit":60,"resets_at":"2026-10-02T00:00:00Z"}}}