🎁 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 →
Why This Role Exists Our team ships two production-bound applications — a Lease Accounting Tool (Flask + MongoDB, ASC 842/GASB 87/96) and a Book Close Validation Agent (FastAPI + React + MongoDB) — that are functionally complete but missing dedicated DevOps ownership. Both currently rely on developers manually running test suites and deployments. We need someone to own CI/CD pipelines, containerized deployment, and production hardening so releases stop depending on manual steps. What You'll Own Stand up CI pipelines (GitHub Actions or equivalent) that auto-run the existing test suites (currently 278 automated tests across Unit/Integration/Exception/Edge categories) on every PR — this is our single most overdue gap on the Lease Accounting Tool. Harden and manage Docker Compose-based deployments across dev, QA, and production environments, including zero-downtime rebuilds (docker compose up -d --build) and environment-specific secrets management. Implement shared, production-grade rate-limit storage (Redis-backed) to replace in-memory rate limiting once multiple workers/instances go live. Own secret rotation, TLS termination, and JWT/session secret strength enforcement across environments — currently flagged as follow-up hardening items in our Production Readiness Report. Set up centralized monitoring/alerting (uptime, error rates, MongoDB health) across both applications, building on existing /healthz endpoints. Maintain the dev to QA to main/prod branch promotion workflow, matching our documented Git branching strategy (feature branches into dev into QA into main). Own database backup/restore procedures and rollback runbooks for MongoDB-backed services. Partner with developers to keep the CI drift-gate in sync (e.g. SOP-rule script mirroring between backend and frontend) so what's displayed always matches what actually runs. Must-Have Skills Docker & Docker Compose in production (multi-service, multi-environment) CI/CD pipeline design (GitHub Actions strongly preferred — our repos are GitHub-hosted) Python web app deployment experience (Flask or FastAPI, gunicorn/uvicorn, nginx reverse proxy) MongoDB operations: backups, indexes, GridFS, connection string management across environments Secrets management and environment hardening (JWT/session secrets, env handling, secret rotation) Comfort reading Python test output (pytest) and wiring it into automated pipelines Nice to Have Experience with Redis (for shared rate-limiting/session storage across workers) Prior exposure to accounting/fintech compliance software (ASC 842, GASB, SOX) is a plus, not required React/Vite build pipeline experience (our second app is a Vite + FastAPI stack)
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.