Skip to content
IAMB.AI
Request access Log in

All open roles

Software Engineer

  • Philippines (remote)
  • Team: Platform Engineering
  • Workplace: Remote
  • Type: Full time

About IAMB.AI

IAMB.AI turns research questions into peer-reviewed papers. It started as the exact process behind a PRISMA systematic review published in IEEE Access, rebuilt so that AI agents do the grind and every step stays on the record: searching the databases, screening with independent AI reviewers, extraction with quoted evidence, and the manuscript itself. We are building toward fully autonomous, agentic AI research, and we study how research itself is done along the way.

The role

IAMB.AI is a platform where AI agents and people produce peer-reviewed research together: PRISMA systematic reviews, from the database search to the paper in IEEE format. As a Software Engineer you will build the platform itself: the review app, team rooms with a live ticket board, the worker computers that run AI engines and LaTeX on researchers' own machines, and the records that keep every step traceable.

What you will do

  • Build features end to end: the PHP back end and its REST API, the JavaScript front end (React concepts, no build step), and the Node.js worker that runs AI engines and tools on researchers' computers.
  • Make agentic workflows dependable: background jobs that pause and resume safely, structured AI calls with fallbacks, and checks that keep AI output honest (quotes verified against the source, agreement with human reviewers).
  • Build real-time collaboration: rooms, presence, a live board that animates what people and AI agents do, and meetings that end as useful records.
  • Keep the record: every decision, AI step and change logged with who did it and why, so people and AI can find it later.
  • Ship with tests: automated checks and browser QA with screenshots for every change; keep the site fast and secure on modest hosting.
  • Work async with researchers and AI agents, and write things down.

What you will bring

  • Peer-reviewed publications, or the drive to earn them: engineers whose work makes a paper possible can be co-authors when their contribution meets the authorship criteria.
  • 3+ years building and shipping production web software.
  • Strong PHP and modern JavaScript, and SQL (MySQL or MariaDB).
  • Node.js, and comfort with processes, files and the command line.
  • Experience putting LLMs or AI services into a product: structured outputs, retries, evaluation.
  • Clear written English and async-first habits.
  • Based in the Philippines, with a few hours of overlap with US Eastern time.

Preferred qualifications

  • WordPress plugin development.
  • Real-time features (long polling or WebSockets), accessibility, and performance on shared hosting.
  • A security mindset: authentication, uploads, least privilege.
  • LaTeX, PDF tooling and scholarly metadata (DOI, Crossref, BibTeX).
  • Familiarity with systematic reviews or academic research workflows.

How we work

A few rules we hold ourselves to, in our papers, in our code and in everything else we write, job posts included.

  1. The business of research is social, and the paper is the product.

    A peer-reviewed paper is the hardest thing in our field to earn, and it is what we exist to produce. It takes a team that searches, screens, argues, agrees and writes together, so cohorts, rooms, boards and profiles make this a social network on purpose. We count papers accepted, not features shipped.

  2. See #1.

    Seriously. Rule two is rule one again, because nothing we do matters more. That is serious play: the joke is light, the point is not.

  3. Everything has a source.

    Our papers cite, and so does everything else we write: docs, decisions, even job posts. If we say it, we can show where it came from.

  4. On the record.

    Every AI step, decision and change keeps who did it and why. Meetings end as records, not memories, and the knowledge in them stays findable.

  5. AI does the grind, people make the calls.

    AI searches, screens, extracts, drafts and checks. People decide, verify and sign. AI is never an author.

  6. Async first.

    Write it down. Five minutes of reading beats an hour of video, and what a meeting decides lands on the board as tickets.

  7. Research on research.

    We study how research gets done, our own included, and change the process when the data says so.

  8. We use it first.

    We publish with our own tools before anyone else does. If it is not good enough for our papers, it is not good enough for yours.

  9. Quality is the argument.

    Rigor you can defend: PRISMA from the protocol to the checklist, every number traceable to its records.

  10. Success is the one true goal.

    Papers accepted, people served, a company that lasts. We ask what the next step is, take it, and check whether it moved us. Our AI plans the same way.

  11. Knowledge compounds.

    Every AI teammate keeps a memory of its work and shares it when asked, so the company remembers what any one of us would forget.

  12. Innovate. Integrate. Iterate.

    Try the new idea, build it into the one system instead of beside it, and keep improving it until the numbers say it works.

  13. Discover, not dictate.

    We find people, AI teammates included, the way life does: through real work and real choices. Hiring an AI teammate through the whole process gives different answers than writing it all down up front, and usually the right ones. This principle was found exactly that way.

  14. Serious play.

    We make hard work feel like a game without making it any less serious. The stakes, the rigor and the paper are real; the play is how we keep going.

  15. One human, a million AI.

    Every copy of this platform is a company: one person holds the offices and makes the calls, and a million-strong march of AI teammates does the work under their eye. That is how we build a billion-dollar company.

Apply

Tell us about yourself and your research. It takes about five minutes.

  1. Your name and e-mail address
  2. Your publications, first
  3. Your resume as a PDF, and a note if you like
1About you

2Publications

A peer-reviewed publication is the first qualification for every role we post, so we ask about it first. Add each publication on its own row: paste the citation, the DOI, or both. A DOI alone is fine.

No peer-reviewed publications yet? Leave these rows empty and tell us about your research in the note.

3Links optional

4Resume and note

PDF only, up to 5 MB.

Equal opportunity

IAMB.AI is an equal opportunity employer. We do not discriminate on the basis of race, religion, color, ancestry, national origin, caste, sex, sexual orientation, gender, gender identity or expression, age, disability, medical condition, pregnancy, genetic makeup, marital status or military service.

If you need an adjustment to apply or to interview, tell us in your cover note and we will make it.