🎁 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 →
Marklytics builds enterprise data platforms for manufacturers and industrial groups. Our software collects operational data from complex, multi-party supply chains, verifies it, and turns it into the records our customers are required to produce for their auditors, customers and regulators. We work with large industrial businesses across Europe and Asia through our teams in the United Kingdom and India. This requirement shapes the way we engineer our products. Data must be traceable back to its source, numbers must reconcile, and every output must survive external scrutiny months after it was generated. When our platform is wrong, our customers do not simply have a user-experience problem they have a compliance problem. Our engineering team is intentionally small. Engineers own systems rather than tickets, communicate directly with the people who use what they build, and are trusted to make architectural decisions. There is no separate team waiting to fix your code once it reaches production. The Role We are looking for a senior full stack engineer who defaults to AWS. You will design and ship cloud-native services end to end, from data model through API to interface, and own the infrastructure they run on. This is a build role. The platform is live and growing, and the work ahead is new capability rather than maintenance. You will be one of the more senior engineers in the India team, which means the architectural calls you make will outlive the feature you made them for, and you should expect to justify them in writing. In practice the week is built around leaving you alone to work. A short standup each morning, a product and engineering demo every two weeks, and otherwise uninterrupted time to build. What You Will Do Build the services that ingest data from customer systems in whatever shape it arrives, and make it reconcile before anyone downstream depends on it. Build the interfaces customers use to review, correct, and sign off on that data before it goes to their auditors. Architect serverless and container-based systems using Lambda, ECS or Fargate, API Gateway, Step Functions, SQS, and EventBridge: choosing between them on cost, latency, and operational burden rather than habit. Model and tune data across Aurora or RDS PostgreSQL and DynamoDB, including schema design, indexing strategy, query optimization, and zero-downtime migrations. Work on AI-assisted features that extract, classify, and validate information arriving in inconsistent formats, and build the guardrails that make the output trustworthy enough to put in front of an auditor. Own infrastructure as code in AWS CDK or Terraform, so that every environment is reproducible and every change is reviewed. Build and maintain CI/CD pipelines with automated testing, staged rollout, and a rollback path that has actually been tested. Implement authentication, authorization, and multi-tenant isolation using Cognito or an equivalent identity provider. Instrument services with CloudWatch, X-Ray, or OpenTelemetry so that incidents are diagnosed from telemetry rather than from theories. Bring cost discipline to design decisions and raise expensive patterns before they reach production, not after the invoice. Review other engineers' code with substance, write design notes, and mentor engineers earlier in their careers. Who We Are Looking For You have four or more years building and operating production web applications, and you have been on call for something you built. You are strong across the stack. Not a front end engineer who tolerates APIs, and not a back end engineer who avoids the browser. You have real production depth in AWS beyond EC2 and S3, and you can explain what you built, which services you chose, and what you would choose differently now. You are comfortable in PostgreSQL. Schema design, indexing, and query performance work are familiar territory, not something you delegate. You treat infrastructure as software. Manual console changes make you uncomfortable. You say what you think. If something is being built the wrong way, you make the case rather than quietly working around it. You write clearly. A distributed team runs on writing, and vague writing becomes expensive quickly. Bonus Points AWS Certified Solutions Architect, Associate or Professional, or AWS Certified Developer. Event-driven and asynchronous processing at scale. Multi-tenant B2B SaaS, particularly where tenants have conflicting requirements. Building with LLM APIs in production, including evaluation and cost control. Security fundamentals in practice, including least privilege IAM, secrets management and depen .
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.