Perla › Manifest › a job in tech
Manifesting a Job in Tech standup, then the real work
You picture the badge, the laptop sticker collection, the Slack status that says you are heads-down. This script skips the interview entirely and drops you straight into an ordinary Tuesday already doing the work.
- A full script for a job in tech, written in the present tense and ready to read tonight.
- Shorter versions — one for falling asleep, one for the morning, and one line to carry with you.
- How to use it: A tech offer comes from a working portfolio, a technical interview and an application sent — never from a sentence, and this page isn't pretending otherwise.
- The common mistake: Rehearsing the interviewer's face, the exact question, the exact answer that impresses them, turns this into a performance aimed at someone else's verdict, which isn't the point of a script like this.
The script
Read it slowly, in the present tense, as though it has already happened. It is written to be spoken aloud, but silently is fine.
Standup is nine minutes, not fifteen, because nobody drags it out here. I say what I did yesterday, what I am doing today, and the one thing blocking me, and then we all go back to our screens without ceremony. My badge is clipped to my laptop bag, worn soft at the edges already, not new anymore. I open a pull request from a teammate and actually read it properly before approving it, leaving one comment that makes the code better instead of just rubber-stamping it. The ticket I am working today is unglamorous, a bug that has been quietly annoying users for a week, and there is real satisfaction in closing it and watching the report go from red to green. Someone pings me a question in the middle of the afternoon and I know the answer, not because I memorised it but because I have simply been here long enough now. I eat lunch away from my desk sometimes, other days I don't, and neither feels wrong. At five, or whenever my day actually ends, I close the laptop on a day that moved something real forward, not a day I spent proving I deserved to be in the room.
Shorter versions
Two for the ends of the day, and one line to carry through the middle of it.
The pull request is merged, the ticket is closed, the red report went green today. Nothing is paged, nothing is on fire. I close the laptop lid and it stays closed. Tomorrow's standup will come when it comes. Tonight the only thing my brain is doing is the ordinary, satisfied kind of quiet after real work.
I make coffee and glance at Slack without dread, just information. Standup is short today, nine minutes, and then the actual work starts, the ticket, the review, the small fix that matters more than it looks. I am not proving anything to anyone in this room anymore. I am just doing the job, properly, the way I do most days.
Standup, nine minutes, then the ticket that has been quietly annoying users all week.
How to use it
A tech offer comes from a working portfolio, a technical interview and an application sent — never from a sentence, and this page isn't pretending otherwise. Use it the night before that interview, or in the ten minutes before a technical screen, to make the ordinary week on the other side feel more real than the room does. The projects and the practice problems are still yours to build; nothing here substitutes for them.
The mistake to avoid
Rehearsing the interviewer's face, the exact question, the exact answer that impresses them, turns this into a performance aimed at someone else's verdict, which isn't the point of a script like this. Skipping the unglamorous groundwork instead, the practice problems, the actual portfolio, in favour of picturing the badge and the standing desk, is the quieter version of the same mistake. Stay with your own ordinary competence in the scene; the applications do the rest of the work.
Questions
Do I need a computer science degree to get a job in tech?
Not always — plenty of people move in through bootcamps, self-teaching and portfolio projects, though the exact bar depends on the specific role and company.
What actually helps more, a portfolio or certifications?
For most tech roles a portfolio of real, working projects tends to carry more weight than a stack of certificates, though this varies by specialism.
Why doesn't this script mention a specific tech stack or tool?
Because tools change fast and a script tied to today's framework ages badly — the ordinary competence underneath it is what actually stays true.
Have this written about you
The script above is written for anyone. Perla asks about your actual situation, writes it as a present-tense narrative and reads it back to you — in a calm voice or your own, recorded once. One ritual instead of ten apps.