The Ricky Rampersad Branch is hiring · one personal assistant · Chaguanas
Personal assistant to Ricky Rampersad · Apps Script · Salesforce · AI in productionThirty-six server-side files. Forty-four scheduled triggers firing every working day. Two hundred and sixty-one Salesforce fields read and written. The Claude API drafting, marking and reading notes in production. Nobody maintains it full time. That is the job.
A minute and forty seconds. The problem this seat solves, the platforms, the tools, and the one thing we are looking for. The words are on screen the whole way through, so it reads with the sound off. Every file name in it is a real file in the branch’s backend; every figure is illustrative and no client appears.
If you have ever fixed something at work on your own time, because waiting for somebody else to fix it was unbearable — this is the one to read.
“Everyone calls me to fix it.” Right now, when a script stalls, a trigger stops or something is stuck on a server, the whole branch rings the Branch Manager. This seat is the person who keeps every system we have built up and running, so that call comes to you, and gets answered.
The next big thing: HELP 868, the branch’s new WhatsApp line, connected to Claude and to Salesforce. It needs one dedicated person to make it brilliant.
Chaguanas, Central Trinidad Read within 48 hours Read by the Branch Manager alone
Every line of that is in production today, carrying real client work. The person in this seat writes in all of it — and on the first day, in the part of it they choose.
All of it public: the repository is open, and you can read the code before you apply.
Below is the kind of form a branch runs on — ours looked like this once. Tap anything that is wrong with it. You do not have to know how to fix it, and there is no list of right answers. We only want to see what you notice.
We are not going to dress this up, because the one thing that wastes both our time is you arriving to find a different job than the one you were sold.
Real admin, and it matters. If it slips, an agent cannot work and a client waits.
This is the half nobody else will offer you, and the reason this page exists.
You do not need to be a developer. You do need to have already written something. A Google Apps Script. A formula that got out of hand. A Zap. A page. Something you talked an AI through until it worked. Nobody in this branch was hired as a developer and none of us would pass a developer's interview — we learned it on the branch's own work, with AI beside us, and you would carry on from where we have got to, with Apps Script, Google Workspace, Salesforce and Claude already paid for and already connected. What cannot be taught is the instinct: you notice a bad process and you cannot leave it alone.
And who it is not for. Somebody who wants a quiet desk and a fixed list — that is an honourable job and this is not it. Somebody who wants to write code all day and never speak to an agent about a client's file — this branch is an insurance branch first. And somebody who is careless with a number: a wrong figure here goes out in a letter to a real family, so care is not negotiable.
Not a roadmap, not a pilot. These are the things you would have your hands on in your first month.
36 files and about 100,000 lines run the branch: the letters, the reminders, the boards, the claims, the renewals, the billing checks. Deployed as web apps on triggers. This is the single most useful thing you will learn here, and it is plain JavaScript.
We read and write it from our own code — OAuth, SOQL, composite requests, tasks, Chatter posts. Not clicking through screens: querying it, reconciling it, and writing back what the record should say.
Just launched, and the next big thing here. Built on respond.io, connected to Claude over MCP and to Salesforce: it answers on WhatsApp, logs every query with a reference, and hands over to a person. It needs one person to make it brilliant, and that would be you.
Used all over the branch to read a long history and draft a reply, with structured output and hard rules about what it may never say. You will learn to put guardrails on a model, which is a skill the market is paying for right now.
The branch mailbox sends and reads through Graph, with the application permissions to match. Every client letter the branch sends goes out this way.
Guardian's own forms are read in the browser and filled, field by field, from the record — so nobody retypes a policy number. Including a scanned form that needed its pages rotated to make it work.
It goes to clients, so it gets tested. You would write tests, and more than once a test you wrote will stop something wrong reaching a real family. That is the job.
The website is the repository — 338 pages, nearly six hundred commits, and no build step. You commit, it is live. Your work is in the open with your name on it.
A good environment is easy to claim and hard to check, so here is ours to check. Everything this branch has built is out in the open — you can look through all of it, today, before you decide whether to spend fifteen minutes applying.
It lives on a site called GitHub, which is where people keep the things they build. You do not need an account and you do not need to understand all of it. Open it, scroll, and see whether this looks like somewhere you would want to be.
A long file called CLAUDE.md — the branch's own working diary. What we built, what broke, and what we decided never to do again. It is honest about the mistakes. If reading it makes you want to join in, you are probably the person.
One file tracks every document through the branch. Another checks an insurer's monthly invoice against our own records, line by line, and tells us where they disagree. You do not have to follow the code — look at how much of it there is.
The claims form, the motor quote, this very page. Everything a client or an agent touches is in there, exactly as it is served. Nothing is a mock-up.
Nothing in that repository is client data, and that is deliberate — the rule is written down in it. Client records live in a private sheet behind tokens and never touch the code. You will learn that discipline here too.
We are not going to invent an exercise for you. Here are two things genuinely sitting undone in this branch right now. One of them is very likely your first fortnight.
The branch moved almost everything onto its own pages — quotes, claims, renewals, the document log — but nineteen staff forms are still on an outside form builder. Petty cash. The fuel log. Licence renewals. The visitors book. They do not talk to anything, nothing is filed where the branch can read it, and no report comes out of them.
Four of those forms are the administrator's own. You would rebuild them as branch pages that file to a sheet, e-mail who needs to know, and report themselves. There are five or six finished examples in the repository to copy the shape from — that is the point of building them all the same way.
Every page on the branch site carries a view counter. There are 157 of them in place. Not one has ever recorded a single view, because the small script behind them was written and never deployed. So the branch publishes constantly and is honestly guessing about what anybody reads.
This is a one-afternoon job with a permanent payoff. Deploy it, confirm it records, and then every Monday the branch knows what its clients and agents actually open. Small, finishable, and it changes a decision every week after.
If you want to see what finishing one looks like, both are described in CLAUDE.md in the repository, in the branch's own words, including why neither has been done yet.
A branch of agents and managers, with a support team who hold the whole operation together. Every one of them uses the tools you would be building.
We mean this literally. Everything below is work the branch does today, so it is work you would be able to point at and say “I built that, here is the commit”.
Google Apps Script running a real business every day, on triggers, against live data — not a course project.
Reading and writing Salesforce from your own code. On a CV in this market, that sentence opens doors by itself.
Not “I use ChatGPT”. Structured output, rules a model may not break, and a human check before anything reaches a client.
HELP 868: respond.io, Claude and Salesforce, on a real line with real clients and an audit trail. Very few people have actually shipped one.
Your work, in the open, with your name on it. The single most persuasive thing you can hand a future employer.
That you took a process and made it take half the time, and can say by how much. Everything else is a tool. That is the skill.
Ideas are cheap everywhere. What is rare is somewhere they get built.
This branch wrote its own software because nobody was going to write it for us. That is still true, and that is the offer.
We do care where you have worked and what you were paid — the form asks both, plainly, so that the conversation can be honest. But none of that decides it. What decides it is what you do when something is badly designed.
Where you have worked, what you changed there, what you are earning now, and three questions in your own words. It is longer than most application forms on purpose. If fifteen minutes is too long to spend on this, then it is honestly not the job — and we would both rather know that now.
Write it yourself, plainly. Four honest lines about a spreadsheet you built beats a polished paragraph that says nothing.
You have already done the short version of this at the top of the page. If the form reads like you, we ask for the long one, and it is the whole interview. Look through what we have built, find something clumsy, missing, or that would save somebody an hour, and tell us about it — what is wrong, why it matters, and roughly how you would fix it.
A page, a form, a process on this very site. You do not have to write the fix and you do not have to be right. We are reading for whether you can walk into an unfamiliar system, find a real problem and explain it to somebody else. That is the job, so that is the test.
Send it however you like — an e-mail, a voice note, a page of writing. If you happen to use GitHub, you can post it there as an issue instead and we will see it. Most people do not, and it counts for nothing either way.
Twenty minutes with the Branch Manager about what you found and what you wrote. Terms and pay are discussed there, openly, against the figures you gave us. If it is not right for either of us, we say so and that is the end of it, with no hard feelings.
Your name, your figures and your answers reach Mr Rampersad and nobody else — not an inbox the branch shares. If you are employed today, that matters, and we treat it that way.
It is a long form and that is deliberate. We are filling one seat, not sorting a hundred CVs, so we would rather read fifteen minutes of your actual thinking than scan a page of job titles.
Ricky Rampersad is making this hire himself, for his own branch in Chaguanas. Terms and pay are discussed on the call. Prefer to write instead? E-mail him directly or call 678-5821.
It happens, and it is not a wrong turn. This page is one seat in the back office. The branch's other door is the one in front of clients — a licensed advisor, building your own book, paid on what you write rather than on a salary.
Same branch, same tools, same people. Newcomers are trained, licensed and put through a full build before they are contracted, and practising advisors move across confidentially. If that sounds more like you than a desk does, go and look — the conversation is with the same person either way.
And if you cannot decide which you are, say so in the form above. It is a fair thing not to know, and he will tell you straight which door he thinks is yours.
No. Nobody in this branch was hired as a developer and none of us would pass a developer's interview. But you do need to arrive having written something — an Apps Script, a formula that got away from you, a Zap, a page, something you got an AI to help you finish. That is the bar: low enough for somebody entirely self-taught, high enough that you are building in your first month instead of watching. What cannot be taught is the instinct for a bad process, and that is what we are really reading for.
Neither had anybody here. They are learnable in weeks if you have already written anything at all, and you would be learning them on real work with AI beside you rather than on a course. What we would ask at the interview is not whether you know them — it is what you have built with whatever you did have.
It is genuinely a personal assistant's job. There is real admin every day and it has to be right, because an agent cannot work and a client waits if it is not. The difference from every other admin job is that the second half of your time is spent making the first half smaller, and you are given the tools and the authority to do that. If you only want to build, this is the wrong seat.
The website is served straight from the repository, so the pages are public by necessity. Client data is the opposite — it never goes near the code, it lives in a private sheet behind per-client tokens, and the rule is written into the repository's own notes. Keeping those two things apart is one of the first disciplines you would learn.
No. The form goes to the Branch Manager's own address, not to a shared branch inbox, and he is the only person who reads it. We take that seriously because we ask for the same discretion from practising advisors on our other recruiting page.
Discussed openly on the call, once we both know the job is the right one. We will not print a figure here and we will not haggle at the end — you will hear it plainly before you ever have to decide anything.
The branch is in Chaguanas, Central Trinidad, and this is a seat in the branch — the admin is physical as well as digital. Hours are the branch's working day; the specifics are part of the conversation.
You will have read a real production codebase and written a clear technical issue about it, in public, with your name on it. That is a genuinely useful thing to have done either way, and we will tell you plainly why rather than leaving you guessing.