Six months ago I was nineteen weeks into a consultancy contract that paid well but felt like a dead end. I'd interviewed at maybe four companies that year — three ghosted me after the take-home, one made an offer I had to turn down because the comp was Czech-market rates and the role was a London-team manager. I was tired.
Then a friend invited me to RemoteJobs.team. I'd been on the network for about ten days when Petr posted a Pangea Health opening — senior backend, EU timezones, Go + Postgres. Exactly my stack. Petr was a 1st-degree connection (he'd invited me); the role's hiring manager was a 2nd-degree connection through Petr. I sent Petr a warm-intro request the same evening.
The intro request that worked
Here's the exact message I sent — pulled from my messages thread with a few names redacted:
"Hey Petr — I saw the Senior Backend Engineer post for Pangea and it's exactly my stack. I've been wanting to move out of consultancy into a product role for a while. Could you tell the hiring manager I'd like to chat?"
Three things I think made this land:
- It was specific (which job, which role).
- It explained my motivation in one line.
- It gave Petr a concrete action — "tell the hiring manager I'd like to chat" — rather than asking him to figure out what kind of intro I wanted.
Petr replied within an hour: "Sure thing — let me forward your note to the hiring team and I'll loop you in by Friday." He cc'd me on an email to Pangea's hiring manager the next morning.
The intro request that didn't work
While the Pangea thread was warming up, I sent a parallel intro request to Anna (a different member I'd connected with). She had a friend at Crater Labs who was hiring DevRel. I framed the ask the same way, and Anna agreed — but the Crater Labs hiring manager never replied.
What I missed: Anna's connection to that hiring manager was four months stale. They'd been colleagues a year ago. The warmth had cooled. A "warm" intro from a stale connection lands as "cold" with one degree of separation. Lesson: ask the inviter about how recently they've actually worked with the target.
The conversation chain
For Pangea, the full sequence took six days:
- Day 1 (Mon): I sent the intro request to Petr.
- Day 2 (Tue): Petr emailed the Pangea hiring manager. Manager replied to Petr that evening asking for "a bit more context".
- Day 3 (Wed): I sent my CV + a short note. Manager replied within four hours asking for a 30-min call.
- Day 4 (Thu): 30-min call. We talked about the role, the team's async setup, comp band. They said they'd want a small async-take-home.
- Day 5 (Fri): Take-home delivered (~3 hours of work, well-scoped).
- Day 6 (Mon): Verbal offer. Written offer 24h later.
Petr's intro removed the cold-application bottleneck. He was the trust anchor — both for the hiring manager (Petr vouches for Anna) and for me (Petr's track record made me trust Pangea).
What I'd tell someone in the same spot
Don't sit on this stuff. The single biggest mistake I made in my previous nineteen weeks of consultancy was not asking anyone for help — I was applying through forms and waiting for hiring teams to come to me. The whole point of RemoteJobs.team is that you don't have to.
Three concrete things you can do today, in 15 minutes:
- Update your profile's "Looking for help with" panel with one specific role you want. Make it a sentence, not a paragraph.
- Browse the jobs board and pick one role. Send the poster a one-paragraph warm-intro request.
- If you don't see anything matching, browse the directory filtered by "Hiring remote" and send a speculative intro request to one member.
The network only does its thing when you give it something to work with.