Embedded Developer - Frontend

EXPERIENCE

3–5 Years

START

Immediate Joiners Preferred

WHO WE ARE

Maxinor AI & Tech Services builds and staffs embedded engineering pods for funded startups and

enterprises. This role places dedicated, named developers directly inside a client's engineering

organisation working their sprint cadence, their code review standards, their production system and not a separate vendor team bolted onto the side.

WHY THIS ROLE IS DIFFERENT

Within your first few sprints, you'll be shipping real features into a live product used at scale, and fixing real production bugs.

WHAT YOU'LL WORK ON

✓Building UI components and application features directly from approved PRDs and design

specifications.

✓Taking on frontend engineering work assigned through the client's sprint planning process, start to

finish.

✓Fixing bugs and supporting production incidents - triaging, resolving, and documenting root cause.

✓Integrating with backend REST APIs, handling error states and edge cases, not just the happy path.

✓Writing unit tests for the code you ship and keeping technical documentation current.

✓Participating in code reviews - both giving and receiving against the existing engineering standards.

✓Attending daily stand-ups, sprint planning, and other engineering ceremonies as a full member of

the team.

WHAT WE'RE LOOKING FOR

The non-negotiable bar

You must have shipped production frontend code as part of a team - with code review, sprint

commitments and real users .

✓ 3–5 years of experience in frontend or full-stack software product development.

✓Strong hands-on experience with a modern JavaScript framework (React, Vue, or Angular).

✓Solid REST API integration experience - consuming APIs, handling errors, working with real (not

mocked) data.

✓Comfortable with Git-based workflows: branching, pull requests, resolving conflicts, working in a shared repo.

✓Working knowledge of Docker - can run, debug, and reason about a containerised application

locally.

✓Exposure to at least one cloud platform (AWS, Azure, or GCP) - comfortable navigating deployed

environments, logs, and basic configuration, not just local dev.

✓Comfortable reading and querying both SQL (PostgreSQL/MySQL) and NoSQL (MongoDB) data

stores well enough to trace an issue end-to-end.

✓Actively uses AI-assisted coding tools (Copilot, Cursor, Claude Code, or similar) as part of daily

workflow, and can review AI-generated code critically rather than accept it blindly.

✓Methodical debugging skills - can isolate and fix a bug from a vague report, not just when the repro

steps are handed to you.

✓Can write unit tests and basic technical documentation without being asked twice.

Strong signals (will stand out)

+ Experience directly embedded in or seconded to a client/partner engineering team, not just an

internal product team.

+ Has been on-call or first-responder for a production incident and can talk through how they handled

it.

+ Comfortable working on a complex, data-heavy, or regulated product - fintech, health-tech, or similar.

+ Has worked across the stack enough to unblock a backend issue when needed, even if frontend is

the primary focus.

+ Familiarity with GraphQL, CI/CD pipelines (GitHub Actions/GitLab CI), or basic Kubernetes

BEHAVIOURAL TRAITS WE LOOK FOR

Technical ability gets you in the door. These traits determine whether you thrive in an embedded, client-facing role.

Ships inside someone else's codebase, not just their own

You are comfortable picking up an existing frontend codebase, understanding its conventions, and shipping to those standards from day one.

Treats production incidents as normal, not exceptional

When something breaks live you triage, communicate what you're doing, and fix it and then write down what happened.

Reads a design spec like a contract

You implement what the PRD and design actually specify, including the edge cases and empty/error states

Debugs methodically, not by guessing

When a bug report comes in with a vague repro, you reproduce it, isolate it and fix the actual cause.

Comfortable being measured by someone else's cadence You're joining an existing sprint rhythm, existing code review standards and existing engineering leadership.

Builds context

You're looking for one codebase to go deep on for months, not a rotation across unrelated projects.

Apply here: https://forms.gle/uq5jM61pNT2FB2LG6