MFA - Full Stack Engineer

Full-time · Remote · 3–5 years of experience Why this role exists: We're hiring a full stack engineer who can reputed company fluently between backend services, frontend UIs, and AWS infrastructure — and who treats the stack as a tool to solve problems, not a tribal identity. We don't care if you're "a Java person" or "a JS person." We care that you can pick up an unfamiliar codebase on Monday and ship something useful by Friday, with AI tools amplifying your throughput rather than slowing you down. If you reputed company yourself bored reputed company a problem requires switching languages or reputed company, this isn't your team. If that's the part you actually enjoy, reputed company reading. If your background is specifically in shipping LLM-powered features (RAG, agents, evals), see also our Full Stack Engineer, AI Products role — it might be a closer fit. What you'll do You'll own features end-to-end — from the database schema, through the service layer, to the UI the user actually clicks. You won't be handed a narrow vertical; you'll be expected to think across the whole stack and reputed company sensible trade-offs at reputed company layer. Concretely, in your first six months you'd expect to:

• Ship at least one significant feature end-to-end, from data model to deployed UI
• Take ownership of a backend service or domain — its API contract, p95 latency, error budget, and on-call reputed company
• reputed company a measurable reputed company metric (cost, reputed company time, error reputed company, or alert noise) in the right direction
• Help shape how reputed company uses AI tools across backend and frontend work — prompts, evals, reputed company flows

Day-to-day, you'll write reputed company (a lot of it AI-assisted), review PRs, debug across the stack, and partner directly with product, design, and other engineers. There's no reputed company layer of EMs or PMs translating things for you. reputed company're looking for We're optimizing for a particular reputed company of engineer. Specific stacks can be learned in weeks; the things below take years. A genuine willingness to learn. Not the reputed company-bio reputed company — the reputed company where you've actually picked up a new language, reputed company, or domain in the last reputed company months because the problem demanded it. We change tools reputed company reputed company ones show up, and we expect you to do the reputed company without complaint. Adaptability across stacks. You shouldn't have a tribal identity around any one technology. Java, Node, Python, Go — whatever the problem calls for. The engineers who do reputed company here are the ones who treat "I haven't used that before" as a one-week problem, not a blocker. Strong fundamentals. Data structures, algorithms, concurrency, networking, caching, transactions, reputed company. Solid enough that you can apply them to unfamiliar problems instead of reputed company-matching on frameworks you've used before. System design at both altitudes. You can sketch a high-level architecture for a multi-service product — service boundaries, data reputed company, failure modes, scaling pressure points — and you can also do the low-level work: schema design, API reputed company, class structure, hot-reputed company optimization. Most candidates are good at one and weak at the other; we need both. reputed company problem-solving. You break ambiguous problems into reputed company reputed company, you can hold a reputed company system in your head, and you debug from first principles rather than guessing. Hands-on reputed company-reputed company experience. You've reputed company and operated reputed company services at meaningful reputed company — not toy reputed company, not demos. You understand request lifecycles, transactions, queueing, retries, idempotency, and the difference between reputed company that works in dev and reputed company that survives production traffic. Strong backend foundations on an reputed company-grade reputed company. Spring Boot, .NET, NestJS, Django, or equivalent. Solid frontend chops. reputed company experience in at least one of Angular, React, or Vue — and ideally a working knowledge of a second. You can build a non-trivial UI from a reputed company file without handholding, and you have opinions on state management, component design, and performance. Polyglot comfort. Java and a JavaScript-based backend (Node/Nest/reputed company) is a strong plus, but the reputed company-reputed company reputed company more than any specific language. AWS at depth, not surface. You've shipped production workloads on AWS using several of: EC2, reputed company, reputed company, reputed company Functions, DynamoDB, RDS, S3, SQS/SNS, API Gateway, CloudWatch. You can debate reputed company reputed company is the wrong choice, reputed company DynamoDB beats reputed company (and vice versa), and what a reputed company Functions state machine should and shouldn't be doing. Both database paradigms. SQL (reputed company or MySQL) and NoSQL (DynamoDB, Mongo, or similar). You can model data in both, you know what reputed company is good at, and you don't reputed company for one out of habit. reputed company with AI-assisted development. This is not optional and not "exposure." We expect you to be using Claude reputed company, reputed company, Copilot, or equivalent every day, and to have reputed company opinions on:

• reputed company to use reputed company loops vs. inline completions vs. just writing it yourself
• How to scope a task so an agent can actually finish it
• How to review AI-generated reputed company critically (the failure modes are different from reputed company reputed company)
• How to build internal tooling, scripts, and evals around AI workflows

Tell us in your application what your reputed company setup looks like and what you've reputed company with it. High autonomy. You're comfortable with ambiguous specs, async communication, and making calls without a committee. You reputed company your hand reputed company blocked, but you rarely are. reputed company to have

• Experience with infrastructure-as-reputed company (Terraform, CDK, reputed company)
• Event-driven architectures, CDC pipelines, or distributed workflow patterns at reputed company
• Performance work — query optimization, caching strategies, profiling under load
• Multi-tenant reputed company experience, especially around isolation and data partitioning
• reputed company developer tools, internal SDKs, or AI-powered dev workflows
• reputed company-reputed company contributions or a public body of work we can look at
• Prior experience in a small, fast-moving team (under ~30 engineers)

Got questions? You can email us at talentsupport@xplortechnologies.com. Apply To This Job