> Markdown version of [/jobs/ext/3615176-backend-engineer](https://www.wearedevelopers.com/jobs/ext/3615176-backend-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Backend Engineer

- **Company:** REMILIA LLC
- **Location:** Irvine, CA, United States
- **Salary:** $115,000.0 - $220,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Code Review, Relational Databases, Software Design Documents, System Programming, WebSocket, Real Time Systems, Indexer, Backend, Web3.js, Front End Software Development, Api Management
- **Published:** October 8, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=2d0fd3a3c5a8033f

## About the Role

* A portfolio of serious backend work you can walk us through in depth
 * Years of experience building and running production systems. You've been the person others go to when correctness or scale gets hard.
 * You've built something where correctness around value mattered: payments, ledgers, marketplaces, virtual economies, entitlements
 * You've built social systems: graphs, permissions, feeds, chat, moderation
 * Strong relational data modeling: schema design, indexing, query design, migrations on live data
 * You write clearly. Specs and design docs are part of the job.

Good to have

 * In-game economies or live-ops: drop tables, sinks and faucets, exploit response
 * Real-time systems (WebSockets, SSE)
 * Web3 identity and assets: wallet signatures, on-chain indexing
 * Founding-engineer or 0 1 experience
 * Systems programming (C/C++/Rust/Zig)

## Description

* Social graph and identity. Build the graph: users, profiles, friends and follows, guilds, roles, permissions and moderation. It has to stay correct under concurrency and abuse, and fast as the graph grows.
 * Financial and cosmetic economy. Take point on implementing currencies, balances, drops, crafting, cosmetics and entitlements, including reconciliation with on-chain assets and commerce. Every transaction must be idempotent, auditable and reversible.
 * Social product. Chat, timelines, feeds and notifications, built as reusable backend capabilities rather than one-off features. rather than one-off features.
 * API model. Implement contract-first, versioned APIs, and help evolve the contracts with the architect so frontends, mobile and third-party clients can build on them.
 * Raise the bar. Bring hard-won experience to design reviews, testing and code review, and mentor others on the team.