Backend Platform Engineer, AI Enablement (Rails)

Cialfo

Full Time

Delhi, IndiaPosted 2 days ago

Resume Keywords to Include

Make sure these keywords appear in your resume to improve ATS scoring

GoRailsAWSGCPAzurePostgreSQLMySQLREST

Job Description

About Manifest Global Manifest Global is building the infrastructure for global human capital mobility - connecting students, schools, universities, and employers across 50+ countries. Our portfolio spans Cialfo (AI-powered college counseling, 2,000+ schools), BridgeU (university guidance for international schools globally), Kaaiser (trusted study abroad counseling across India and Southeast Asia), and Explore (AI-powered university outreach, 1,000+ university partners). Together, we move talent across borders at scale. $80M raised. Still early. About This Role Most backend roles ask you to ship endpoints and migrations. This one asks you to ship those and extend the platform that lets the rest of the engineering team - and the AI agents working alongside them - ship them too. That platform already exists. Shared conventions, the skills library, safe contribution zones, spec-to-endpoint workflows, AI-agent infrastructure powering Saige and Explore - all live, all in production, all being used today. You'll own its next chapter: deepening it, scaling it, and raising the ceiling on what each engineer can do without re-deriving the same patterns. If the most interesting question in your career right now is "how do I build leverage for a team, not just output for myself?" - keep reading. What will you own You own the backend - not just the code you write, but the system that lets everyone around you contribute to it. That means shipping production Rails services, designing APIs other teams build against, and owning the data layer end to end. And it means extending the workflows, conventions, and guardrails that let QEs generate test scaffolds independently, PMs and analysts ship config and feature-flag changes safely, and AI agents operate inside the codebase reliably. The measure of success here is not your personal output. It is how much the team around you can do because of what you built. Concretely, that looks like: <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Shared AI conventions that keep tooling output consistent across the codebase - for backend code generation, schema changes, and migrations - whoever or whatever is driving</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">A backend skills library that encodes Rails patterns, service contracts, domain models, and query patterns into workflows anyone on the team can invoke</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Safe zones and guardrails that let PMs and analysts ship config changes, feature flags, and scoped data changes without creating engineering cleanup</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Spec-to-endpoint and ticket-to-migration workflows that compress the path from intent to working backend code</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">AI-agent backend infrastructure - runtimes, tool-calling layers, retrieval pipelines, evals - that powers Saige, Explore, and what comes next, and scales with each new feature</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">A feedback loop with engineers, QEs, and PMs building against the platform every day - you hear where things break and you fix them</li> </ul> What success looks like <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">30 days. You've mapped the existing platform, the conventions, the skills library, and the AI workflows the team is already using. You know where they're sharpest, where they're starting to bend under load, and where the next wave of investment should go.</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">90 days. You've shipped meaningful additions to the skills library, tightened conventions where they were drifting, and closed gaps the team has been working around. Other engineers are reaching for your work instead of writing from scratch.</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">6 months. The backend platform is materially more capable than when you joined. Saige and Explore's AI surfaces hold up under heavier production load because of infrastructure decisions you made. PMs and analysts are shipping more inside safe zones, with less cleanup. The engineers and agents building against the platform move faster - and they know why.</li> </ul> About You <h3>Qualifications</h3> <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Bachelor's degree in Computer Science, Engineering, or a related field - or equivalent practical experience</li> </ul> Experience <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">5+ years of backend engineering experience on production systems</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Strong production Rails experience - services you've owned and shipped, not contributed to at the margins</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Real fluency with PostgreSQL or MySQL, including query optimization at scale</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Experience designing and maintaining RESTful APIs that other teams build against</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Daily fluency with AI-assisted coding tools (Claude Code, Cursor, Codex, or similar) - and a track record of making them work consistently for other people, not just yourself</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">The instinct to treat a non-engineer touching your platform as a capability to design for, not a risk to manage</li> </ul> Strong nice-to-haves <ul> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Hands-on AI/LLM backend work - retrieval pipelines, agent runtimes, tool-calling, evals, prompt versioning</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Developer experience or platform engineering background - internal SDKs, shared libraries, opinionated documentation</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Cloud experience (AWS, Azure, GCP) and serious testing discipline (RSpec, Capybara)</li> <li style="font-family: arial, helvetica, sans-serif; font-size: 10pt;">Evidence of cross-functional thinking - something you built that made a non-engineer's life easier</li> </ul> Why Manifest We're building the infrastructure for global human capital mobility - the rails that move students, schools, universities, and employers across 50+ countries. Cialfo is in 2,000+ schools. Explore is trusted by 1,000+ universities. BridgeU runs across the UK, Europe, and the Middle East. Kaaiser has guided students across India and Southeast Asia since 1997. The opportunity is real. $700B flows annually in remittances from migrant workers. 85M workers will be missing from developed economies by 2030. We're building the operating system that changes that. $80M raised from Tiger Global, SIG, and Square Peg. Still early. The team has already built the infrastructure for AI-native engineering - shared conventions, a live skills library, AI-assisted workflows across engineering, QE, product, and design. Saige is in production. Explore's AI capabilities are in production. This isn't an aspiration we're hiring you to bring to life. It's an operating system we're hiring you to extend, scale, and make permanent.