🎁 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 Marklytics 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, their customers, and their regulators. We work with large industrial businesses across Europe and Asia, from teams in the United Kingdom and India. That constraint shapes the engineering. Data has to be traceable back to its source, numbers have to reconcile, and every output has to survive external scrutiny months after it was generated. When our platform is wrong, our customers do not have a user experience problem. They have a compliance problem. The engineering team is small and deliberately so. Engineers here own systems rather than tickets, talk directly to 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 is genuinely strong on both sides of the stack and wants to be involved in the full scope of what gets built. You will take features from an ambiguous problem statement through to production: shaping the requirement, choosing the approach, building it, testing it and supporting it afterwards. The product will give you strategy and context but will not make your day-to-day technical decisions for you. You will also be one of the more experienced engineers in the room, so expect to set the standard through code review, design discussion, and the quality of what you ship. 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 screens customers spend their working day in, where a confusing interface turns into a wrong number in a report someone has to sign.Build the reporting and export features customers hand to auditors, regulators, and their own boards.Design and implement back end services and APIs in Node.js or Python that are documented, versioned and predictable under load.Own relational data modelling in PostgreSQL, including migrations, indexing and performance investigation.Integrate customer systems through REST APIs, webhooks, and file-based exchanges, handling authentication, rate limits, retries, and partial failure properly, because most of these integrations fail quietly rather than loudly.Work on AI-assisted features that extract and validate information arriving in inconsistent formats and build the checks that make the output trustworthy.Write automated tests at the unit and integration levels, and treat untested code as unfinished code.Deploy and operate services in cloud environments, taking part in release and incident processes.Break vague or oversized requirements into deliverable increments, and explain the trade-offs to people who do not write code.Mentor junior engineers through code review, pairing, and design discussion. Who we are looking for You have four or more years of professional full-stack development on systems that real users depend on.You are a strong coder. The specific technologies matter less than your ability to read an unfamiliar codebase, find the bug, and write code that someone else can maintain.You are confident with React or Next.js and TypeScript and equally confident writing the service behind them in Node.js or Python.You treat data modeling as a design decision rather than an afterthought.You have worked somewhere without much structure and still shipped.You think about the user before the implementation. You want to understand the problem, not just start building.You say what you think, and you can disagree with a decision without becoming difficult about it.You write clearly. A distributed team runs on writing. Bonus points Next.js server components, edge rendering, or deployment on Vercel.Background jobs, queues, or scheduled processing.Document generation, export, or reporting features.Building with LLM APIs in production, including evaluation and cost control.Direct experience working with enterprise customers and their technical teams. How we work Hybrid working from our Chennai office, three days a week, with core overlap hours so you can work alongside UK-based colleagues.Short decision paths. You will have direct access to the people setting product direction, and your questions will not travel through three layers to get answered. .
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.
