🎁 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, 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 This is an early career engineering role for someone who writes application code and takes quality seriously inequal measure. You will split your time between building features and building the automated test coverage that keeps them working, with close support from senior engineers. This is a development role, not a QA seat. You will ship real product code from your first month. The reason testing sits in the job at all is that our customers use our output as evidence, so a regression that reaches production is not a cosmetic problem for them. If you want to become a strong full stack engineer and you understand that testing is part of engineering rather than something handed to somebody else, this is a good seat. 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 front end components and screens in React or Next.js with TypeScript that customers use to enter, review and correct their data.Implement API endpoints and back end logic in Node.js or Python, with guidance and review from senior engineers.Write and maintain unit and integration tests using Jest, Vitest, PyTest or equivalent frameworks.Build and maintain end-to-end test suites in Playwright or Cypress, keeping them fast and free of flakiness, because a flaky suite is one everybody learns to ignore.Carry out API testing using Postman or automated equivalents.Write clear, reproducible defect reports, and verify fixes properly before closing them.Support regression testing ahead of releases, and help move work out of manual checking and into automation.Take part in code review, both giving and receiving feedback. Who we are looking for You have one to two years of professional software development experience. Substantial internship work counts.You are comfortable with JavaScript or TypeScript and React, and you have written some back end code in Node.js or Python.You understand SQL and relational database fundamentals.You have used at least one automated testing framework on real work, not only in a tutorial.You understand why unit, integration and end-to-end tests exist separately and what each one is good at.You investigate before you escalate. When something breaks, your instinct is to find out why rather than to pass it on.You can take direct feedback on your code without taking it personally. Bonus points CI pipelines that run tests automatically on every change.Contract testing, test data management or performance testing.Any cloud platform exposure, on AWS, Azure or GCP.Any hands-on work with LLM APIs, even from side projects.A degree in Computer Science or Information Technology, or a portfolio of work that shows the same thing. 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.