Strong Middle Full Stack Engineer; AI-First, QA-Inclusive

Strong Middle Full Stack Engineer (AI-First, QA-Inclusive)

We are looking for a Middle Full Stack Engineer to join Group
107 for a specific client project. The client operates an electric-vehicle car sharing platform serving residential communities, hotels, resorts, and public members across 26 U.S. states — a small, tightly connected set of products (a React Native driver app, a web admin portal, and in-house internal operations tools) that lets members find, book, unlock, and pay for an EV entirely from their phone.

You will own features end to end on a lean team: build them, test them, and care whether they actually work well for the person using them. The client’s constraint is throughput on complex releases, not ideas or headcount — so this role treats AI coding tools as a core part of the craft and helps move the team toward a faster, AI-assisted release rhythm.

Work here is visible: a change you make on Tuesday affects a driver standing next to a car on Thursday.

Please note: working hours follow the US Pacific time zone — roughly 9:00am–5:30pm PDT
. Please make sure this schedule works for you before applying, as reliable daily overlap with the US-based team is required.

• 2–4 years of professional full stack development experience.
• Production experience with React Native — or demonstrable mobile experience and the ability to ramp quickly.
• Solid relational database skills (PostgreSQL and/or MySQL), including writing and reasoning about non-trivial queries.
• Experience with REST API design and integration with third-party services.
• Hands-on experience with AI coding assistants in real project work, and a clear point of view on where they help and where they do not.
• Genuine QA instinct: comfortable writing test cases, running regression passes, and reporting defects precisely.
• Excellent written and spoken English (Upper-Intermediate B2+), able to communicate directly with non-engineering stakeholders.
• Reliable overlap with US Pacific business hours.
• Strong problem-solving with an optimization mindset — improve the build-test-fix loop, don’t just work within it.
• Ability to work independently and own a feature area end to end.
• Willingness to advocate for decisions: push back with reasoning rather than just taking orders, and flag early when something is off track.
• Comfortable planning, scoping, and estimating work in an asynchronous, remote team.

• Serverless / edge functions (Netlify Functions, Lambda, or similar).
• Payments experience (Stripe); billing, invoicing, or accounting integrations (Quick Books).
• IoT, telematics, fleet, or mobility/transportation domain experience.
• Mapping and geolocation work.
• Test automation (Playwright, Cypress, Jest, Detox) and CI/CD pipelines.
• Mobile release process familiarity (Test Flight, App Store Connect, Google Play);
  Jira and Notion.

• Develop features across the stack:
  Node.js services and serverless functions, React admin interfaces, and React Native screens and flows.
• Work with PostgreSQL and MySQL — schema changes, queries, and data correctness in billing and booking logic.
• Integrate and maintain third-party services (payments, telematics, invoicing).
• Own QA for your own work and take part in structured QA cycles on release builds: writing test cases, running regression passes against dev and Test Flight builds, and reproducing and documenting issues clearly in Jira.
• Catch the class of bug that matters most here — billing inconsistencies and vehicle/app access issues — and help build automated coverage where it earns its keep.
• Use AI coding tools (Claude Code, Codex, or similar agentic tooling) as a daily driver: decomposing work into specs an agent can execute, reviewing generated code critically, and closing the loop with tests.
• Help establish team practice around this — prompt and spec patterns, review standards for AI-generated code, and guardrails that keep velocity from costing quality — to shorten the release cycle toward smaller, more frequent, better-verified releases.
• Read a ticket and ask the question behind it: flag when a requested change will confuse a driver or create an operational headache, and propose the better version.
• Take…