Four desks. Menu hashes (#full-stack-dev, #data-engineer, #cloud-architect) land on the cards below.
ROLE 01 · CommerceFull-stack commerce
OpenCart / PrestaShop / Next on live stores. Checkout, feed, cache, not landing pages.
Need
- You’ve kept a store or catalogue in production
- PHP or TypeScript, no stack religion
- You can write what you didn’t measure as N/A
On the desk
- Modules, themes, marketplace integrations
- CWV and errors, not just UI
- Review on PRs that touch live
ApplyEmail careers@empirex.tech. CV + 10 lines on a system you kept alive.
Remote · Bucharest node · Production
ROLE 02 · DataData & feeds
Sync, comparison feeds, stock that doesn’t lie. ETL only when it earns it.
Need
- You’ve operated a sync or feed that could break price
- SQL / PHP / scripts, observability
- You understand GDPR on catalogue data
On the desk
- Feeds, mappings, retry, alerts
- Stock truth across channels
- You document what’s N/A
ApplyEmail careers@empirex.tech. CV + 10 lines on a system you kept alive.
Remote · Bucharest node · Production
ROLE 03 · SRECloud / SRE
Hosting, LiteSpeed, Redis, 5xx, windows. Not “move it all to Kubernetes” as a reflex.
Need
- You’ve taken over or held a store at night
- Linux, cache, backup, DNS
- You’ve read an SLA, not just uptime as a slogan
On the desk
- Takeovers, cache, incidents
- Observability, not 40 alerts
- Written runbook
ApplyEmail careers@empirex.tech. CV + 10 lines on a system you kept alive.
Remote · Bucharest node · Production
ROLE 04 · SecuritySecurity
Hardening, access, surface. No vanity pentest without a contract.
Need
- You’ve closed a real surface (plugin, user, port)
- You know journal vs noise
- You don’t sell “100% secure”
On the desk
- Config audit, patch, access
- Prod / secrets segregation
- Severity-based incident
ApplyEmail careers@empirex.tech. CV + 10 lines on a system you kept alive.
Remote · Bucharest node · Production