Internal · June 2026
BUILD YOUR
Future
You're building real software.
Today we make sure the world can see that.
Ali · Andy · Rayan · Rahaf
00 · Before we start
THIS IS NOT
Bad News
- Nobody is getting fired. Nobody is leaving.
- CedarPoint is not closing.
- This meeting is an investment in you — your career, your future, your opportunities.
- You've been building real products. It's time to make sure the world knows that.
This is not for CedarPoint's benefit. This is for yours. Personally.
01 · Proof
THIS IS
My Inbox
I didn't apply for most of these. They came to me.
Student. No degree yet. Based in Tripoli, Lebanon.
If it works for me — it works for you.
01 · Proof — LinkedIn works
LinkedIn inbound — KSA Fintech
I didn't apply
Resume reviewed — positive inbound
Profile did the work
I also got my TechBuddy web development offer from LinkedIn — a US company, fully remote. And how did we find Ali, Rahaf, and Rayan? LinkedIn.
01 · Proof — Lebanon is not a blocker
From Lebanon.
Still accepted.
Unified Mentor Program
Shortlisted
Full Stack Dev Internship
Selected
Codyveda Technologies
Accepted
02 · Online Presence
GitHub +
LinkedIn
Two platforms. That's your foundation. Everything else comes after.
GitHub
- Your GitHub is your portfolio — not a backup drive
- A brilliant CV means nothing if GitHub looks empty
- Pin your best repos. Write READMEs that explain what and why
- Projects must be deployed — not just sitting in a folder
LinkedIn
- A gate for inbound opportunities — proven
- Network with real engineers, leads, founders
- I'm not asking you to post for CedarPoint — post for yourself
- One post about something you learned > ten reposts
03 · Portfolio Projects
Solve Your
Own Problem
Don't look for impressive ideas. Look at your own life — what actually annoys you? What do you do manually that could be automated?
That's your project.
When someone asks "why did you build this?" — you have a real answer. That answer is worth ten times more than a perfect Twitter clone.
The 3 Rules
01
Your problem
Real motivation, real answer in the interview
02
Deploy it
Not localhost. Live. If it's not deployed it doesn't exist.
03
Share it
LinkedIn, friends, anywhere. Small audience beats no audience.
04 · Interviews
"We'll think
about it."
vs. "When can you start?" — here's what decides it.
01 — Project Explanation
Can you explain a project you built in 2–3 minutes?
What, how, why, what broke, what you learned. Practice this out loud until it sounds natural. Every CedarPoint project is material.
02 — Think Out Loud
Can you walk through your thinking when you don't know the answer?
Going silent is the worst thing you can do. Say what you know. Say what you'd look for. Show your brain, not just your memory.
03 — Connect to Their Need
Can you connect what you know to what they actually need built?
"You need real-time features — I built the backend for a live driver tracking system. Let me tell you how that worked."
04 · Interviews — Proof
Preparation
gets you here
ByteBloom Solutions — Jan 28
First round interview
Stage 3 — Screening & Technical Review
Pipeline progression
Study the role before any interview. Read the job description like a document. Know what they need before you walk in.
05 · Platforms
What Actually
Works Here
✗ Skip for now
Low approval rates for Lebanese accounts. Payment infrastructure issues. The effort-to-result ratio is bad. Not worth it right now.
Remote contract — $20–$70/hr
Came through visibility
06 · How to Write About Your Work
Ownership
First
Most developers list the stack. That tells recruiters nothing about you. Every developer has a stack.
Worked on TrackMe using Next.js and Supabase
Owned the frontend of a real-time driver tracking system used by logistics operators — built with Next.js and Supabase Realtime, handling live GPS updates across a three-app monorepo
The formula:
What you owned
→
Problem solved
→
Outcome
→
Stack
07 · Your Growth
Ali
Backend · NestJS
You came in not knowing NestJS. That's documented. And what you've done since is real.
You're now writing production backend modules on a live SaaS product that real businesses will use.
The PR feedback you get is detailed and technical — not because you're doing badly. Because you're being treated like a real engineer.
The problems you're hitting now — CORS configuration, module architecture, validation pipelines — these are not beginner problems.
You moved. You might not feel it. But I see it in the code.
What to highlight
- NestJS backend modules on production SaaS
- Real-time API architecture (TrackMe)
- Learned on the job, in a real team
Personal project idea
A small NestJS project you fully own and deploy. Doesn't need to be complex — needs to be yours, live, and explainable in 3 minutes.
07 · Your Growth
Rahaf
Frontend · Next.js
You own half the frontend of TrackMe. Not a component, not a page — half a product.
Real-time UI. Mapbox integration. Multi-app Turborepo setup.
That is mid-level work.
When you sit in an interview and they ask you to walk them through a project — you have something real to say.
Most developers your level are building todo apps. You built a tracking system.
What to highlight
- Half the frontend of a real-time SaaS product
- Mapbox GL JS integration
- Supabase Realtime on a multi-app monorepo
Personal project idea
Something you designed and built solo. No brief. No team. Something you'd actually use. Ship it, post it.
07 · Your Growth
Rayan
Product Designer · Figma
You have a full product design portfolio sitting in your Figma right now and I don't think you fully realize it.
The CedarPoint website. TrackMe. The ERP. Multiple products, real briefs, real constraints, shipped.
You go through real design reviews with feedback that challenges your decisions — not just "looks good."
Most design students have passion projects. You have client work.
The portfolio already exists. It just needs to be packaged.
What to highlight
- 3 products designed end-to-end
- Full design cycle — Figma to shipped
- Design reviews with real feedback
Personal project idea
Redesign something that frustrates you. Document the full process — research, wireframes, final. Shows independent thinking outside a brief.
07 · Your Growth
Andy
Intern · QA · Frontend
You're my friend before you're an intern here — so I'll be straight with you.
You did QA on a real product that real clients use. You found bugs across the frontend and backend. You worked on fixing them. You shipped a finished project.
Yes, you hit some walls. But you're an intern working on real software — not doing exercises from a book.
That's a real foundation. And I think you know you're capable of more than you've shown so far.
What to highlight
- QA on a client-facing product
- Bug detection across frontend and backend
- Shipped a finished project
Personal project idea
Pick a direction — frontend, QA, or something else. Commit to it for 60 days. Build one thing, ship it, post it.
08 · The Plan — Ali
Ali's
Action Plan
Online
Clean up GitHub — pin repos, write READMEs with what and why. LinkedIn headline: "Backend Developer · NestJS · Building real-time SaaS at CedarPoint". Post occasionally about what you learned.
CedarPoint
Document your TrackMe backend contribution — what you built, what problem it solves, what you learned. This becomes your primary experience bullet on LinkedIn and CV.
Personal
Build one small NestJS project you fully own. Deploy it. Doesn't need to be complex — needs to be yours, live, and explainable in 3 minutes.
08 · The Plan — Rahaf
Rahaf's
Action Plan
Online
Push work to GitHub, clean it up. LinkedIn headline: "Frontend Developer · Next.js · Real-time SaaS · CedarPoint". Write one post about your TrackMe work — what you built, a screenshot, what you learned.
CedarPoint
TrackMe frontend is your centerpiece. Write it up: the problem, your role, the stack, the outcome. CV, LinkedIn experience, eventually a portfolio page.
Personal
Build and deploy something you designed yourself. No brief, no team, your idea. Something you'd actually use. Ship it even if small, then post it.
08 · The Plan — Rayan
Rayan's
Action Plan
Online
Behance account this week — non-negotiable. LinkedIn headline: "Product Designer · Figma · UI/UX · CedarPoint". Two case studies from CedarPoint work — not just screenshots, tell the story.
CedarPoint
3 case studies ready: CedarPoint website, TrackMe, ERP. Each needs: the brief, your process, before/after where relevant, the outcome. This portfolio already exists — package it.
Personal
Pick a design problem from your own life. Redesign something frustrating or design something that doesn't exist yet. Document the full process — research, wireframes, final mockup.
08 · The Plan — Andy
Andy's
Action Plan
Online
LinkedIn profile complete this week. Headline: "Junior Developer · QA · Frontend · CedarPoint". GitHub up with your work, READMEs written. Don't wait until you feel ready — you're already past that point.
CedarPoint
QA work on the Client Portal is real experience — write it up: what you tested, what you found, what you fixed. Your finished project gets a proper description. Treat it like it matters, because it does.
Personal
Pick a direction — frontend, QA, or something else. Commit for 60 days. Build one thing in that direction, ship it, post about it.
You're building
real software.
The only difference between you and someone who gets recruited is visibility.
That's fixable. And it starts this week.
I'm available for anyone who needs help with their LinkedIn, GitHub, CV — whatever you need. Don't figure it out alone when you have someone next to you who's already been through it.