🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
About Remoasset Remoasset handles global laptop procurement and retrieval end-to-end. Companies buy, deliver, and recover devices across countries through our platform instead of chasing vendors, employees, and logistics providers themselves. The product is a B2B SaaS platform covering the full device lifecycle — procurement, fulfilment, warehousing, deployment, and end-of-life recovery — with a customer-facing app, an internal admin portal, and integrations into MDM, ERP, and payment systems. It is real operational software: physical assets, multiple currencies, cross-border logistics, and workflows that cannot silently fail. The role You will own significant parts of the platform end-to-end — schema through API through UI. This is not a ticket-taking role. You will make architectural calls, push back on bad ones, and be accountable for what ships. Expect to work across a TypeScript monorepo (Next.js frontends, Node-based API, PostgreSQL, Redis-backed workers) and on Python/FastAPI services where they are the better fit. We care that you can reason about systems, not that you have memorised one framework. What you will do Design and build features end-to-end: database schema, API contracts, background jobs, and the UI that consumes them Model relational data properly — entities, constraints, indexes, migrations — for a domain with genuinely complex state transitions Build and operate asynchronous workloads: background jobs, queue workers, and scheduled tasks for fulfilment, sync, and reconciliation flows Design and evolve REST APIs consumed by multiple frontends and third-party integrations Own deployment and operational health of what you build — CI/CD pipelines, observability, alerting, and incident response Review code and raise the standard of the codebase through review, refactoring, and written technical direction Mentor mid-level engineers and make onboarding faster for the people who come after you Work directly with product and operations to turn ambiguous requirements into a concrete technical plan What we are looking for (Required) TypeScript — strong, idiomatic, comfortable with advanced types and strict mode Next.js — App Router, server components, rendering strategies, and where the boundaries actually sit Python — production experience, not scripting familiarity FastAPI — building and running real services: dependency injection, Pydantic models, async handlers PostgreSQL — schema design, query optimisation, indexing, transactions, and migration strategy AWS — practical working knowledge across compute, storage, networking, secrets, and IAM CI/CD — GitHub Actions or equivalent; you have built pipelines, not just consumed them Redis — caching, queues, locks, and knowing when not to use it Background jobs, workers, and schedulers — idempotency, retries, dead-letter handling, and what happens when a job runs twice Also valuable Containerised deployments (Docker, ECS/Fargate, or Kubernetes) Infrastructure as code (Terraform, Pulumi, or CDK) Payment integrations (Stripe or similar) and the failure modes that come with them Observability tooling — structured logging, tracing, error tracking Multi-tenant SaaS, RBAC, and auth systems (Cognito, Auth0, or equivalent) Prior work in logistics, supply chain, ITAM, or another operationally heavy domain What tells us you are senior You have owned a system in production through at least one bad incident and changed the design afterwards You can explain a technical trade-off to a non-engineer without dumbing it down You write things down — decisions, runbooks, why the weird thing is weird You disagree early and in writing rather than quietly building something you think is wrong Hiring process Introductory call — 30 minutes Technical conversation — architecture and past work, no whiteboard algorithms Practical exercise — a scoped, realistic problem, reviewed together Final conversation with the founding team
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.