Ricky Rampersad Branch Apply

The Ricky Rampersad Branch is hiring · one personal assistant · Chaguanas

Personal assistant to Ricky Rampersad · Apps Script · Salesforce · AI in production

A hundred thousand lines of Apps Script already run this branch. Come and own them.

Thirty-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.

  • 101,508lines of Apps Script
  • 44scheduled triggers
  • 261Salesforce fields
  • 347pages served

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

What runs here

What the branch runs on, this morning.

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.

No CV. No cover letter.

This is the job you have now. Fix it.

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.

36backend files we wrote ourselves
100klines of Apps Script, in production
338pages on the branch site
593commits so far, every one readable
175test files, because it ships to clients
1seat open for the person who builds the next part
Straight, before anything else

The title says Personal Assistant. Read what the job is.

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.

Half the day

The branch's administration, done properly

Real admin, and it matters. If it slips, an agent cannot work and a client waits.

  • Licence renewals, and the deadlines that go with them
  • Petty cash, the fuel log, the visitors book
  • Documents in and out, and the record of where each one is
  • Keeping the branch's own data clean — names, numbers, dates
  • Reports the Branch Manager and head office need on time
The other half

Making that admin not need doing next month

This is the half nobody else will offer you, and the reason this page exists.

  • Keep it running: when a script stalls or something is stuck on a server, find out why, fix it, and write the amendment so it does not happen again
  • Learn the workflow and the rules behind each platform we work on: Salesforce, Apps Script, Microsoft 365, HELP 868 and Claude, and the new ones as they arrive
  • Take a job you do by hand and turn it into a form, a script, a page
  • Write the Apps Script that files it, e-mails it and logs it
  • Wire it to Salesforce so nobody types the same thing twice
  • Put it on the branch app where the team can actually reach it
  • Then measure it, and tell us whether it worked

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.

Who this is for

If any of this is you, we should talk.

Where you are now
  • You can see three things in your office that could be fixed this week, and you have told someone, and nothing happened.
  • You have already written something — a script, a formula that got out of hand, a Zap, a page — because it was the only way to get the job done. Nobody paid you for it and nobody uses it but you.
  • You are the person everyone comes to when the system breaks, and it is not in your job description or your pay.
  • You type the same information into two systems and it bothers you every single time.
  • Your CV says what you were responsible for. It does not say what you built, because you were never allowed to build anything.
What changes here
  • You see something broken, you say so, and the answer is usually “go on then”. The branch runs on things somebody decided to fix.
  • The branch pays for the tools and you use them every day: Apps Script, Salesforce, Microsoft 365, respond.io, Claude. You get the keys, not a request form.
  • When it breaks, it breaks in front of the whole branch and you fix it. That is how everyone here learned.
  • Typing the same thing twice is treated as a defect, not as the job.
  • In a year your CV names systems in production, with public commits anybody can read. That is yours to keep wherever you go next.

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.

The tools, named

Everything on this list is live in the branch today.

Not a roadmap, not a pilot. These are the things you would have your hands on in your first month.

Proof, not adjectives

A job description tells you very little. So here is the whole workshop.

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.

the repository — public, no sign-in
# one link. nothing to install, nothing to sign up for.
# three folders worth opening, in this order
› CLAUDE.md what we built, and what broke
› apps-script/ the 36 files that run the branch
› claims/ a page a real client fills in

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.

Your first job, already waiting

Two real jobs. Nobody has done them yet.

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.

  1. Nineteen forms that are still somebody else's

    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.

  2. 338 pages, and we cannot tell you which one is read most

    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.

What the week looks like

Not a job description. The actual shape of it.

Every morning, before anything elseThe branch's own system sets your day and you sign in on your phone — your list, what is overdue, what was promised to whom. The admin that must happen, happens first.
MondayThe reports that have to go out, out. Then an hour on whatever you are building, because if it is not in the diary it never happens.
Tuesday and WednesdayThe branch meets Wednesday morning. Things break in meetings — somebody says “why do we still do that by hand?” and that sentence becomes your next job.
Any day something goes wrongA letter does not send, a figure reads wrong, a form refuses. You find out why. This is where you will learn fastest, and it is the part that is genuinely hard.
FridayShip something. A form, a page, a script, a fix — and tell the branch what it now does that it could not do on Monday.
Every few weeksSomething you made becomes the way the branch works. That is the whole job, and it does not stop being satisfying.
Who you would sit with

A small team. You would not be a department of one.

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.

What you take with you

Twelve months from now, this is on your CV.

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”.

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.

How we choose

Three gates. None of them is a CV sift.

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.

  1. The form below — about fifteen minutes

    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.

  2. Then: one thing you would fix here

    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.

  3. Then a conversation, and a decision

    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.

Apply

Fifteen minutes. Read by one person.

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.

  1. He reads it himself, within 48 hours.
  2. If it reads like you, he asks you for one thing you would fix here.
  3. Then twenty minutes on the phone, and a straight answer either way.

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.

1You

Getting to Chaguanas

2Where you have worked

Two jobs is plenty. We are reading the third box, not the first two.

How long have you been working?

This is the box that matters most in this section.0/500

3Pay, honestly, both ways

We ask so that the conversation is straight and nobody's time is wasted. You can decline either one and it is not held against you.

If we agreed, when could you start?

4What you can already do

Tick anything you have genuinely used, even badly, even once. Ticking nothing is a real answer and it does not rule you out — it only tells us where to start you.

5In your own words

These three decide it. Take your time on them and write them yourself.

Plain words. A spreadsheet counts.0/700

How you'd approach it, not a finished plan.0/700

Be specific. “Growth” tells us nothing.0/400

6Last things

Best time for a call

Read by the Branch Manager alone. Nothing is sent to anyone else, and nothing reaches your current employer. Your pay answers are used for the conversation and nothing else.

The other door

Came for this and found yourself reading about the agents?

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.

Fair questions

What people ask us.

I am not a developer. Am I wasting my time?

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.

I have never touched Apps Script, or Salesforce.

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.

Is this really a personal assistant's job, or a developer's job with a cheaper title?

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.

Why is your code public? Is that not a risk?

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.

I am employed. Will my current employer find out?

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.

What about pay?

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.

Where is it, and are the hours fixed?

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.

What if I do the GitHub issue and you say no?

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.

Apply — 15 minutes