Infrastructure, with the delivery already behind it
Relay is the one in the cast who cannot work alone. The thing being passed only stays in the air because three pairs of hands agreed on where it was going.
That is not a metaphor we reached for. An order placed inside a partner’s software has to cross the API, the campaign engine and a department inside the agency before a merchant sees anything happen. Every role below owns one hand in that chain, and none of them owns all of it.
Three honest reasons, and no ping-pong table
- Infrastructure with a customer already on it
- MGP is not a hypothetical. Cocomo Media delivers everything the catalogue sells, and has for years, which is a rare thing to build on top of.
- A small team on a large surface
- Catalogue, ordering, fulfilment, storefront, docs. Nobody here owns one screen, and nothing is somebody else's problem.
- Constraints worth having
- Your product lives inside someone else's software, in front of merchants with no patience and no marketing team. That focuses the work.
Four steps, and no silence in between
The same process runs on both sides of the door. You will hear back either way. If we go quiet on you, write to support@cocomomedia.in and say so.
You write to us
One form, one email. Attach the work rather than describing it, and tell us which role you are aiming at.
A conversation
Thirty to forty minutes with the person who would run your work. Mostly about what you have made and why you made it that way.
Something small and real
A short exercise close to the actual job, or a walk through a project you own. Paid if it takes more than an afternoon.
Meet the section
Time with the people you would sit next to, and a straight answer on money, hours and what the first month looks like.
Open roles
Open one to read the job properly. If none of them is yours but you can see where you would fit, the last option in the form is for exactly that.
Build the API that POS and billing platforms integrate once: catalogue, ordering and fulfilment, multi-tenant from the first line.
What the week looks like
- Design and ship endpoints and webhooks a partner engineer can read without booking a call.
- Keep tenancy isolation boring and absolute, because a merchant's data is the whole trust story.
- Work on the queues between an order being placed and a campaign being staffed.
- Write the tests and the sandbox that let a partner integrate in a fortnight.
What gets you the chair
- You have run an API somebody else depended on, and kept it compatible.
- Comfort with queues, idempotency and the failure modes of both.
- You would rather delete a feature than version it badly.
Sit between MGP and the platform integrating it, from the sandbox tenancy to the day their merchants can buy.
What the week looks like
- Walk partner engineering teams through six endpoints and an embeddable storefront.
- Debug the integration from their side of the wire, not ours.
- Turn every question asked twice into documentation nobody has to ask about again.
- Feed the sharp edges back to the platform team with the evidence attached.
What gets you the chair
- You can read someone else's codebase without judging it out loud.
- You write well, because most of this job is written.
- Any POS, billing or commerce integration experience is a real advantage.
Make sure what a merchant bought is what a merchant gets, on time, through the agency behind the API.
What the week looks like
- Route incoming orders to the department that delivers them, and watch the clock.
- Chase the missing input from a merchant who has a shop to run and no time for forms.
- Keep the report honest: what ran, what it cost, what happened.
- Spot the service that keeps slipping and say so early.
What gets you the chair
- You are organised in a way other people can see.
- You are not precious about chasing things.
- Comfort talking to small business owners in their own language.
Design a storefront that has to live inside somebody else's software and still feel like it belongs there.
What the week looks like
- Design the merchant-facing catalogue, checkout and reporting screens.
- Work within a partner's own interface constraints, including the white-label case.
- Prototype in the browser with the front-end team rather than over the wall from them.
- Own the pieces of the design system that both worlds share.
What gets you the chair
- Work that shows systems, not just screens.
- You can design for a shopkeeper, which is a harder brief than designing for a marketer.
- You can build enough to test your own idea.
Own the documentation a partner engineer reads at eleven at night, when nobody is around to answer.
What the week looks like
- Write and maintain endpoint reference, webhook guides and the integration walkthrough.
- Keep the sandbox examples working, which means running them.
- Turn support threads into pages.
What gets you the chair
- A sample of developer documentation you wrote.
- Enough code to test what you are describing.
Send it over
Every field except the obvious ones is optional. The work matters more than the covering letter, so put a link in and keep the letter short.
The agency is hiring too
Same company, different building. If the work you want is campaigns, film, design and copy rather than endpoints, the roles are on the Cocomo Media side.