background
  • Home
  • Engineering resources

Engineering resources

Engineers who join your team

The engineering capabilities CYBORG brings to client teams, from full-stack and mobile development to AI engineering, cloud automation, quality and delivery leadership.

Each card is a type of engineer we provide. Share your requirement and we'll propose the right person, with their experience and likely start date. A quotation follows separately.

Software Engineering

5 roles

Full-Stack Engineer

Application features, APIs, databases, integration, testing and bug fixing within an agreed design.

  • React / Next.js
  • Node.js
  • TypeScript
  • Python
  • REST APIs
  • SQL & NoSQL databases

Senior Full-Stack Engineer

Independent ownership of complex features, integrations, data design and production issues. Can connect applications to AI services.

  • React / Next.js
  • Node.js
  • TypeScript
  • Integrations
  • Data design
  • AI service integration

Mobile App Engineer (React Native / Flutter)

iOS and Android apps with React Native or Flutter, including native integrations, login, API connections, and app builds and releases.

  • React Native
  • Flutter (Dart)
  • Kotlin / Jetpack Compose
  • iOS & Android integrations
  • Secure storage
  • App releases

AI Engineering

2 roles

AI Application & Agent Engineer

Applications that use LLMs, connected to business data and tools, with search over your own data and controlled AI agent workflows.

  • LLM applications
  • Retrieval (RAG)
  • Tool & data integrations
  • Agent workflows
  • Guardrails & evaluation

AI Engineering Workflow Specialist

AI-assisted development for engineering teams: coding-agent setup, developer automation, review practices and quality checks.

  • Coding-agent setup
  • Developer automation
  • Review practices
  • Quality checks

Cloud, Quality & Delivery Leadership

4 roles

QA & Test Automation Engineer

Test planning, functional, API, web and mobile testing, automated tests, defect reporting and release checks.

  • Test planning
  • Functional & regression
  • API testing
  • Web & mobile testing
  • Test automation
  • Release checks

Engineering & Delivery Lead

Leads solution direction, planning, stakeholder coordination, technical risks and delivery.

  • Estimation & planning
  • Stakeholder communication
  • Risk management
  • Team coordination
  • Delivery

AI: using it vs. building with it

Using AI coding tools and building AI systems are two different skills. We only propose an engineer for an AI Engineering role if they have done that work before.

Using AI tools to build software

Uses tools such as Codex or Claude Code to write code, refactor, document and create tests.

Building AI systems

Builds applications that use LLMs, search over your own data, connect AI to tools, and run AI agents with proper checks and safeguards.

The engineer stays responsible. AI tools help engineers work faster. The engineer still reviews and tests every change, and remains responsible for technical decisions, code quality, security and the agreed work.

With or without AI tools: your choice. By default, our engineers use AI coding tools. If your company does not allow them, our engineers work without them. Their skills do not depend on AI. Tool permissions, code access and data handling are agreed with you before the engineer starts.

More on how we work: How We Build

How we work together

Dedicated engineers

  • The engineer joins your team and works under your day-to-day direction and processes.
  • You set priorities, review and accept the work, and manage delivery. CYBORG remains responsible for providing the engineer and for all employment obligations.

CYBORG-supervised engineering

  • The engineer, or a small team, works with an agreed level of technical supervision from CYBORG.
  • Technical direction, reviews, reporting, deliverables and responsibilities are set out in the statement of work.

How we choose engineers

We look at what the engineer has actually done, how complex your work is, and how much independence the role needs. Years of experience matter, but they don't decide suitability on their own.

What we agree before starting

  • The engineer works full-time and remotely, Monday to Friday. Working hours and time-zone overlap are agreed with you before onboarding.
  • Leave, duration, notice period and start date are confirmed before the engineer starts.
  • Onsite work, travel, extra hours, dedicated hardware, cloud services, software licences and paid AI tools are agreed separately.
  • Part-time technical or delivery supervision can be arranged for an agreed number of hours each month.
  • Your company's rules decide system and code access, intellectual property, confidentiality, data handling, security, and whether AI coding tools can be used.

Steps to get started

  1. Share your requirement
  2. We shortlist engineers
  3. Technical discussion
  4. Quotation and terms agreed
  5. Engineer starts

Tell us which engineers you need.

Share the roles, how long, and when you'd like to start. We'll reply with the engineers we'd propose and their experience.

Roles, how long and a start date help us reply with the right people.

Your concept is secure. Every submission is covered by our NDA.

What happens next

  1. You get a confirmation email straight away.
  2. An engineer reads your message and replies personally.
  3. If it is a fit, we set up a free call to talk it through.