Activity
Mon
Wed
Fri
Sun
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
What is this?
Less
More

Owned by Toyib

SHIFT

6 members • Free

Land & level up into senior + AI roles across Europe. Honest career coaching, a real AI stack & live EU job intel - from a Dublin engineer.

Memberships

Skoolers

164.5k members • Free

9 contributions to SHIFT
The AI coding tool everyone says you "must learn" changed again this week. Here's what actually matters
If you feel behind because you haven't mastered the "best" AI coding tool, stop. Look at just the last two weeks. The rankings reshuffled again. New agents launched days ago, older ones jumped versions, and there's an open price war on, with some tools costing a fraction of others per task. Blink and the "winner" is different. Here's the trap. If you tie your identity to one tool, you're outdated every few weeks. That's exhausting, and it's the wrong game. Because underneath the churn, the thing that pays isn't tool loyalty. It's the meta-skill. Most developers now use these tools, and a huge share of code shipped today is AI-assisted. The tools are table stakes now. The edge is how you direct them: breaking a problem down, writing a clear spec, reviewing what the agent gives you, knowing when it's wrong. Learn one tool deeply enough to build that muscle. Then you can pick up the next one in an afternoon. The tool is disposable. The skill of directing it isn't. So don't panic-learn every launch. Get fluent in one, stay loosely aware of the rest, and put your energy into the judgment no tool replaces. 👇 Which coding agent are you actually using right now, and are you loyal to it or do you switch based on the task? Curious what this room is running.
1 like • 4h
@Nazam Khan I also use cursor on a daily basics but have you tried the new GPT-5.6 family? I think they are a game changer.
0 likes • 4h
@Nazam Khan The reasoning is really good and fast
Stuck on something? Ask me here
This is your direct line to me. Career decision, CV, interview, salary, a technical wall, "should I take this offer" - post it here and I'll give you a straight answer. No question is too basic. To get the best help, give me the context: - Where you are now (role, level, location) - What you're trying to do - What you've already tried or what's blocking you I read everything in here, so don't sit on a question for weeks. Let's break it in: what's the one career or job-search thing you're stuck on right now? First one to post, I'll answer in full below 👇
1 like • 4h
@Nazam Khan You already know JS and Python, and that's enough to cover the whole stack, so don't box yourself into just frontend or just backend yet. For a first job, go full-stack but keep it simple: since you know JavaScript, lead with React (frontend) + Node/Express (backend) + PostgreSQL. One language across the stack means faster progress and a wider job market. Park Python for later (great for AI/data roles). Then market yourself as "full-stack, frontend-leaning." That focus beats a vague "junior full-stack." Heads-up: fully remote first jobs are the toughest to land as a beginner, so stay open to hybrid for role #1. Remote gets much easier after a year or two. Biggest lever right now: build 2-3 of your own full-stack projects. Want me to help you pick them?
1 like • 4h
@Nazam Khan Let's go. Here are 3 projects that build on each other, and each one adds a skill hiring managers actually look for. Do them in order. 1. Job Application Tracker A dashboard where you log jobs you've applied to, track status (applied / interview / offer / rejected), add notes, and filter. You're literally building the tool for your own job hunt. Skills it proves: user auth (login/signup), full CRUD, database relations, forms and validation. This is the bread and butter of almost every junior role. 2. Expense Tracker with charts Add income and expenses, categorise them, and show spending with simple charts. Pull in a currency or bank-style API for bonus points. Skills it proves: working with a third-party API, data aggregation, and turning raw data into visual UI. Shows you can handle real data, not just text boxes. 3. Real-time collaborative notes (or a simple chat) Two people open the same page and see updates live. Skills it proves: WebSockets and real-time state. This is your 'wow' project. Most beginners never touch real-time, so it makes you stand out fast. Two rules for all three: - Deploy every one of them (Vercel for frontend, Render or Railway for backend). A live link beats a GitHub repo every time. - Write a short README explaining what it does and why you built it. Recruiters read those. Start with #1 this week. Post it here when it's live and I'll review it. Deal?
Real EU roles, real salaries - start here
This is the room you won't find anywhere else: the honest European tech-market picture. Real roles, real ranges in € and £, real company insight - not US numbers that don't map to Dublin, London, Berlin or Amsterdam. I'll be dropping roles and salary intel here regularly. But it works best as a two-way street. So tell me, so I can tailor what I post: - Which city or market are you targeting? (Dublin, London, remote-EU, elsewhere?) - What role and level? - Are you benchmarking a salary right now, or actively applying? Comment below 👇 - the more specific you are, the more useful I can make this section.
1 like • 1d
@Nazam Khan Lets go 🚀
Welcome to SHIFT 🎉 Here's what's happening
The doors are open. Here's how to get moving: 1. Watch the START HERE course in Classroom - 4 short videos, ~5 minutes. 2. Post your intro in 🚀 Start Here: your role, your target role, your #1 blocker. 3. Run the AI Job-Search Prompt in 🤖 AI Stack — your first win in 10 minutes.| Coming soon: our first live coaching call (date going up on the Calendar this week) and the first cohort of the 7-Day AI Job Search Sprint. Glad you're here. Now go post that intro 👇
1 like • 1d
@Nazam Khan 💃
The Warm Outreach Templates That Get You Noticed Before You Apply
Most applications disappear into a stack of 300-500 others. A warm application doesn't guarantee an interview - but it dramatically increases the chances that someone actually sees your CV. The goal isn't to ask for a referral. It's to start a genuine conversation. 1. The opener (start a conversation) Hi [Name] - I came across your post about [specific project, launch, or article]. I really liked [one genuine observation or takeaway]. I'm a [your role] working in a similar space, so it was especially interesting to see how your team approached it. Looking forward to following what [Company] builds next. 2. The soft ask (only after they've engaged) Thanks for getting back to me. I noticed your team is hiring for the [Job Title] role. Would you mind if I applied and mentioned that we'd connected here? Absolutely no worries if you'd rather not - I just wanted to ask, and thanks again for the conversation. 3. After you've applied Hi [Name], I just submitted my application for the [Job Title] role. I'm particularly excited because [specific reason tied to the team's work, product, or mission]. If there's anything you'd recommend highlighting - or anything you think strong candidates typically do differently - I'd really appreciate the advice. The rules that matter - Mention something specific they've actually shared or built. - Show genuine interest before asking for anything. - Keep it under 100 words. - Never ask for a referral in the first message. - Don't send the same template to everyone. - If they don't respond, move on politely. - One thoughtful message to the right person is worth far more than fifty generic LinkedIn connection requests. Then: Comment the company you're applying to 👇 and I'll help you write a personalised first message that doesn't sound like AI.
1 like • 1d
@Nazam Khan 🙌
1-9 of 9
Toyib Ahmed
3
44points to level up
@toyib-ahmed-9447
Software engineer + career coach in Dublin 🇮🇪 Helping engineers level up into senior & AI roles across Europe. Founder @ SyncReel.io

Active 3h ago
Joined Jul 13, 2026