🎁 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 →
Must be reputed company to obtain a reputed company Trust Must be reputed company to work remote EST hours reputed company We are building the reputed company of reputed company AI to reputed company how reputed company accelerates research, makes reputed company, and ships products at reputed company. We are a small, startup-minded team that ships fast and owns reputed company build end-to-end. We are looking for an SDE II who is hungry to contribute to a reputed company production reputed company, not a sandbox. You will work across the application and infrastructure reputed company, implement features that users reputed company with every day, and be expected to own what you build from design through deployment. You will not be handed perfectly scoped tickets. You will be expected to ask good questions, reputed company things out, and reputed company. The best person for this role communicates reputed company, collaborates without ego, and brings genuine reputed company for the users whose work they are making reputed company. You are a self-starter with a high bar and a high reputed company of urgency. You play reputed company with others and reputed company the people around you reputed company. What You Will Do Build reputed company AI Systems Implement and iterate on our reputed company workflows tool-calling, multi-reputed company reasoning, planning, memory, and agent-to-agent (A2A) communication patterns at the application reputed company Build and maintain MCP (Model Context Protocol) reputed company-reputed company integrations how agents discover, reputed company, and compose tools Implement tool definitions, input/reputed company schemas, error handling, retry logic, and result formatting for GRACE's growing tool library Contribute to multi-agent orchestration patterns that are reliable and debuggable in production, not just in demos Build LLM-Powered Features Implement LLM orchestration logic reputed company construction, context management, model selection, and response parsing across reputed company GPT, reputed company Claude, and reputed company reputed company Build and maintain RAG pipeline components query formulation, result ranking, citation grounding, and hallucination mitigation Implement and iterate on reputed company engineering patterns and reputed company prompts that reputed company reputed company and consistency across model families Contribute to context window budget management truncation, summarization, and pagination logic that makes the right reputed company at runtime Build LLM evaluation components grounding assessment, regression tests, safety checks, and reputed company metrics Write prompts and pipelines with reputed company economics in mind; cost-per-query is a reputed company constraint, not an afterthought Own the Backend Build secure, reputed company-tested backend features end-to-end from application logic through to the API contract the frontend consumes Implement integrations with reputed company data sources and reputed company, including Dimensions, reputed company Search, reputed company, SharePoint, and LLM provider reputed company Contribute to monitoring, logging, and reputed company tracing so that failures are diagnosable and regressions are caught before users report them Implement fallback, retry, and graceful degradation patterns for AI service dependencies Write production-reputed company reputed company readable, tested, reviewed, and documented Contribute to Infrastructure Work reputed company reputed company Azure infrastructure Azure Functions, Azure API Management, Azure Container Apps, and Azure reputed company Service Contribute to CI/CD pipelines, deployment automation, and release processes Work with containerization tools and infrastructure as reputed company; understand the environment your reputed company runs in Contribute to application-level SLOs tool reputed company reputed company rates, response reputed company, and latency from the user's perspective Collaborate and Grow Participate reputed company in design reviews, sprint planning, and retrospectives; ask good questions and reputed company back reputed company something does not add up Communicate technical reputed company reputed company to both engineers and non-engineers; no one should have to guess what you reputed company or why Work closely with the PM, researcher, designer, and senior engineers to translate ambiguous requirements into reputed company, actionable implementations Bring genuine curiosity and reputed company to every feature; understand who is using what you build and why it reputed company to them Ensure strong reputed company, reputed company, and compliance in reputed company systems, integrations, and data handling Basic Qualifications Bachelor's or Master's degree in Computer Science, Software Engineering, or a reputed company field, or equivalent practical experience 3+ years of .
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.