Skip to main content
AI SoftwareCorporation

Engineering careers

Do your best engineering on systems people rely on

The work spans software engineering, cloud, data and AI, quality and consulting, on systems that businesses run on every day. It suits engineers, consultants, delivery leads and analysts who enjoy hard problems, clear ownership and work that others can build on.

In a bright studio, one colleague sketches on a whiteboard while another looks on and two more walk in reading papers.
People lean over a table while one of them sketches on a large sheet of paper with a marker.

Team norms

Habits that shape the job

These habits describe the job honestly, including the parts that ask the most of you. They apply to everyone, whatever their role or seniority.

  • Ownership, with backup

    You own your work from design to production, but you never carry it alone. Pairing and a clear escalation path mean help is close when a problem gets hard.

  • Write it down

    Design notes, decision records and written updates put context where the whole team can find it. They make handovers, time off and onboarding far less painful.

  • Direct, kind feedback

    Code reviews, retrospectives and one-on-ones exist to help people improve. Feedback is specific and respectful, and it flows in every direction, including upward.

  • Blameless when things break

    Incidents happen. We look at the conditions that allowed a failure, fix them and share what we learned, instead of searching for someone to blame.

  • A pace you can sustain

    Good engineering needs rested engineers. We plan realistically, protect time for focused work and treat late-night heroics as a sign the plan needs fixing.

  • Curiosity with judgment

    New tools and models arrive constantly. We try them on real problems, share what we find and adopt only what proves itself in practice.

Disciplines we hire for

Find where your experience fits

These are the areas we recruit in, not a list of current openings. If your background matches one of them, we would like to hear from you.

Seen from behind, a woman annotates printed charts at a shared meeting table while colleagues take notes beside a laptop and coffee cups.

Software engineering

Server-side and client-side engineers who build APIs, integrations, and web and mobile apps, and who care as much about how code behaves in production as how it reads in review.

Typical skills

  • TypeScript, React and Next.js
  • Node.js, Java, .NET, Python or Go
  • API and integration design
  • Legacy code modernization
  • Automated testing

Quality engineering

Specialists who make quality measurable through test strategy, automation frameworks and performance checks that give teams the confidence to release often.

Typical skills

  • Test strategy and risk analysis
  • Playwright, Cypress or Selenium
  • API and contract testing
  • Performance and load testing
  • Accessibility testing

Cloud & platform

The people who build the foundations other teams ship on: cloud infrastructure, delivery pipelines and observability, with security and cost controls designed in.

Typical skills

  • AWS, Azure or Google Cloud
  • Terraform and infrastructure as code
  • Kubernetes and containers
  • CI/CD pipelines
  • Monitoring and incident response

Data & AI

Data and applied AI engineers who turn raw data into dependable pipelines and AI features, from retrieval and document processing to evaluation in production.

Typical skills

  • Python and SQL
  • Data pipelines and modeling
  • LLM integration and retrieval
  • Evaluation and model monitoring
  • Machine learning fundamentals

Consulting & architecture

Architects and technology consultants who assess systems, weigh options against evidence and turn decisions into roadmaps that delivery teams can act on.

Typical skills

  • Architecture and modernization reviews
  • AI and cloud strategy
  • Technical due diligence
  • Cost modeling and business cases
  • Clear written recommendations

Delivery & product

Delivery leads, product managers and business analysts who keep scope, priorities and stakeholders aligned, so the team builds the right thing in the right order.

Typical skills

  • Agile delivery and planning
  • Product discovery and backlogs
  • Stakeholder and risk management
  • Requirements and business analysis
  • Clear written communication

Hiring process

Four steps, each with a clear purpose

Details vary by role and seniority, but the shape stays the same. Before each conversation, you will know who you are meeting and what it is for.

  1. Step 1: Introduction

    Share your background and the kind of work you are looking for, through the contact form or a listed role. If there is a potential match, we invite you to a first conversation.

  2. Step 2: First conversation

    An informal, two-way conversation about your experience, your goals and how we work. Your questions matter as much as ours.

  3. Step 3: Skills conversation

    A practical discussion with people from your discipline, based on realistic problems rather than trivia. We care about how you reason through design, quality and trade-offs.

  4. Step 4: Decision and offer

    We share a clear decision and the reasoning behind it. If we make an offer, the role, expectations and terms are set out in writing before you commit.

Open roles

Current openings

Roles appear here only while we are actively hiring for them.

No open roles at the moment. You can also write to us at [email protected].

Next step

Tell us about the work you want to do

Introductions are welcome at any time. Share your background, your discipline and the kind of problems you want to solve.