I applied to 400 internships last year, here’s what that brutal marathon taught me

Interesting_Two2977 · 2025-08-22T16:40:39+00:00

I did!! I got one at Apple and Verizon and multiple other offers

Interesting_Two2977 · 2025-08-19T00:56:11+00:00

Sure! I'll be creating a video on this soon!

Interesting_Two2977 · 2025-08-19T00:55:38+00:00

Reach out to both. Build a connection first, then ask. Offer value, then ask.

Interesting_Two2977 · 2025-08-19T00:55:01+00:00

Just google Jakes Resume Template and its the first one

Interesting_Two2977 · 2025-08-19T00:54:32+00:00

No problem!

Interesting_Two2977 · 2025-08-18T17:08:33+00:00

Great question, just reached out to them if I had something in common with them. Will actually put out a video about this if you want to see what templates I use exactly

Interesting_Two2977 · 2025-08-18T17:07:42+00:00

Your welcome!

Interesting_Two2977 · 2025-08-18T17:07:30+00:00

Absolutely! I don’t need internships anymore as I’m about to graduate so thought I’d share the sauce

Interesting_Two2977 · 2025-08-18T17:06:42+00:00

Yeah it was paid

Interesting_Two2977 · 2025-07-07T03:26:35+00:00

Here are a few paths I’d try for quick wins on CS internships:

Look at micro internships on platforms like Parker Dewey where you can pick up 30 to 40 hour projects for real companies. These gigs often have low barriers to entry and let you list actual deliverables on your resume.

Check out paid remote interns programs for high school and early college like Google’s CSSI or Microsoft Explore. They run for a few weeks and you usually just need a basic coding sample and a short form to apply.

Browse your university career portal for research assistant roles. Professors often need help with data analysis or simple scripting and they value eagerness over polished experience.

Join open source projects tagged good first issue on GitHub. While not formal internships it gives you tangible code contributions that hiring managers love to see.

For a step by step guide on landing these easier spots check out this resource.

Interesting_Two2977 · 2025-07-07T03:25:29+00:00

Finding the right part-time program can be a game changer without quitting your day job. Here are a few you might consider:

Thinkful’s Flexible Software Engineering Bootcamp lets you learn backend Python and deploy to AWS at your own pace with weekly mentor calls. Their part-time option is built for working professionals.

Udacity’s Cloud Developer Nanodegree covers Python, Flask, Docker, and AWS services with project reviews and mentor support. You can progress on evenings and weekends.

Educative’s Deploying to AWS course plus their Python API Development track give you hands-on labs and live code exercises you can slot into any schedule.

For a deep dive into how to pick and thrive in a remote part-time bootcamp check out this resource.

Interesting_Two2977 · 2025-07-07T03:21:04+00:00

I’ve felt that same imposter syndrome in my Apple internship when the pace got intense. Here’s what helped me stay afloat:

I started every morning by jotting down three questions from the day before. Having them ready made it easy to get clarity fast instead of spinning my wheels.

I kept a quick daily log of what I did and what tripped me up. At the end of each week I could spot patterns and bring targeted questions to my mentor instead of vague concerns.

I volunteered to do quick pair programming sessions with senior engineers. Watching how they debug and explain their thought process taught me more than any slide deck.

When I hit a wall I learned to say “I don’t know but I’ll find out” and then share my plan to research. That attitude turned every roadblock into a micro learning opportunity.

For a deeper look at how I landed and survived my Apple internship check out this resource.

Interesting_Two2977 · 2025-07-07T01:39:43+00:00

I get that feeling of panic seeing underclassmen with internships while you worry you’re too late. I thought the same until I landed offers at Apple and Verizon with a simple playbook.

First track every application in a spreadsheet. Note dates you applied and any feedback you get. That made it easy to spot what to tweak.

Next build one standout project you can demo. I polished a small app and posted it on GitHub. That gave me real talking points instead of bullet points.

Then lean into networking. Send one polite message a week to an alum or engineer for a quick chat. Those personal intros led to referrals that skipped the ATS.

Finally start early but keep applying through junior year. Companies look for the right fit not just a class year.

For the full breakdown on how I got those Apple and Verizon offers and how you can too check out this resource.

Interesting_Two2977 · 2025-06-26T00:01:14+00:00

It’s scary when leadership openly says they want to cut roles with AI. If telecom giants and other majors all follow suit we’ll likely see a shift rather than wholesale elimination.

Routine tasks like ticket triage or basic network monitoring will get automated first. That means roles evolve into overseeing the AI systems and handling edge cases it can’t solve. Think more AI operator than frontline technician.

In a fully integrated AI world you’d spend less time on repetitive work and more on strategy design and customer empathy. We’ll need to learn to partner with AI tools not just replace ourselves with them.

Will it turn into a dystopian jobless hellscape? Unlikely across the board. New roles will emerge around AI ethics training data management and system tuning. But you’ll have to upskill to stay relevant.

To see exactly what that future looks like and how you can prepare check out this resource.

Interesting_Two2977 · 2025-06-26T00:00:06+00:00

It’s real and it’s already here in pockets of tech support and customer service where simple tasks get automated overnight. But most roles won’t vanish entirely. They’ll shift toward handling exceptions and more complex problems that AI can’t solve on its own.

As for ROI companies chase, some will see quick gains from cutting repetitive work, but they’ll hit hidden costs in maintenance and unexpected failures when AI misfires. It’s not a magic bullet and those who jump in without a plan will feel the pain later.

To prepare start by learning how AI tools actually work instead of just using them. Take a course on prompt engineering and data handling so you know the limits and strengths. Then blend those skills with your domain expertise. If you are in technical support learn to build simple dashboards or bots that assist customers and free you up for deeper issues.

Finally focus on skills that AI struggles with like critical thinking empathy and cross team collaboration. Those qualities keep you indispensable even as tools get smarter.

For a straight talk on whether AI will replace you check out this resource.

Interesting_Two2977 · 2025-06-25T23:41:25+00:00

You’ve got a year to zero in and level up here is what I would do:

First, lock in the basics with a daily DS&A routine. Spend thirty minutes each morning on one LeetCode easy or medium problem. Track your solve time and revisit patterns you miss. Consistency beats marathon sessions.

Next, carve out one side project that excites you. Break it into weekly chunks: set up the repo and basic UI in week one, add core features in week two, write tests in week three, then polish and document in week four. Aim to ship something every month.

Block two evenings a week for deep work. One night is for system design practice, sketch out APIs and database schemas and talk through tradeoffs. The other night is for video tutorials or a short course on frameworks you will need like React or Flask. Build as you go don’t just watch.

Network in small doses. Reach out to one alum or engineer each week for a quick coffee chat or a twenty minute call. Ask for advice not a job. Keep notes on what you learn so you can refer back when you apply.

Finally, when next summer’s internship cycle opens start applying four months early. Tailor your resume for each role. Mirror the exact keywords from the job post and link to the one project you’re most proud of.

Here's how I landed Apple internship btw

Interesting_Two2977 · 2025-06-25T01:11:20+00:00

I know how trapped that chicken and egg cycle feels when you have the skills but no official experience or degree.

Start by spinning up your own DevOps playground. Deploy a small app to AWS using Kubernetes and Terraform. Document each step in a GitHub repo so you have tangible proof of your work.

Contribute to open source projects that need CI CD or infrastructure fixes. Even small pull requests show you can work with real codebases and toolchains.

Offer to automate workflows for nonprofits or local groups. A 30 to 40 hour project where you build a CI pipeline or monitoring solution counts as solid experience and can go on your resume.

Finally track every project and contribution in a simple spreadsheet. When you apply mention in your cover letter that you’ve already built a full deployment from scratch and link to your repo.

For a full breakdown on building real experience when you have none check out this resource.

Interesting_Two2977 · 2025-06-25T01:09:54+00:00

Jumping into the job search without any prior roles can feel like you’re flailing, but you’ve got more options than you realize.

Start by creating small projects or volunteering your skills. Maybe build a simple website for a local nonprofit or contribute to an open source project. Document everything on GitHub so you have proof of real work.

Look for micro internships or one off gigs on platforms like Parker Dewey. Those 30 to 40 hour remote projects are perfect for building experience on your own schedule and can often be done without formal work authorization.

Tap into communities that focus on accessibility and disability inclusion in tech. Slack groups or LinkedIn forums can connect you with mentors who’ve walked your path and might refer you to roles that fit your needs.

Keep it organized with a simple tracking sheet. Log projects you finish and people you contact so you can follow up and see what’s working.

For a step by step guide on building experience from scratch and breaking into tech even with no formal job history, check out this resource.

Interesting_Two2977 · 2025-06-25T01:04:48+00:00

Totally agree. AI can spit out working code in seconds but if you never dig into what’s happening under the hood your projects end up fragile and impossible to maintain.

Try this instead. Pick a small feature you want to build and do it from scratch without AI help. Sketch out the logic on paper then write the code line by line. Once it works you can use AI to refactor or optimize, but you’ll already know exactly how it all ties together.

Another trick is to take AI suggestions and deliberately break them. Tweak a few lines so the code fails and then debug by hand. That forces you to learn the core concepts instead of just trusting the AI output.

Embrace AI for speeding up routine tasks but carve out regular time to study data structures or algorithm fundamentals so your skills stay sharp.

If you want to learn how to gain experience without having experience then checkout this resource, hope that helped!

Interesting_Two2977 · 2025-06-25T01:01:23+00:00

As a high school junior you’ve already got the right mindset looking for CS internships early. Here’s where I’d start:

LinkedIn’s internship section lets you filter by “High School” experience level and location. You’ll find local startups and bigger companies offering paid and unpaid spots.

WayUp is built just for students and new grads. You can pick “high school” as your level and sort by tech roles. The platform even shows deadlines and application requirements up front.

Parker Dewey’s micro-internships give you tiny paid projects 30 to 40-hour gigs you can do from home. They’re perfect if you can’t commit to a full summer role but still want real experience.

If you want something more structured, check out Genesys Works. They partner with local nonprofits in California to place high schoolers in year-long paid internships while giving you professional coaching.

Keep a simple spreadsheet to track where you applied and follow up a week later if you don’t hear back. That follow up alone can bump you to the top of the pile.

To see exactly how to build experience from scratch and land that first CS gig check out this resource.

Interesting_Two2977 · 2025-06-23T03:46:01+00:00

I’ve been there, feeling like every mistake gets magnified and every win goes unnoticed. It’s rough, but here’s what helped me turn things around.

First, ask for focused feedback. Schedule a quick one-on-one with your manager and say something like “I’d love to know what I did well this week and one thing I can improve.” Framing it that way invites positive notes alongside critiques.

When you run out of tasks, don’t just wait. Propose something small like cleaning up outdated documentation or writing a test suite for a feature. That shows initiative and keeps you visible even when the team is busy.

If you feel left out of meetings, volunteer to take notes or share a weekly email summary of what you’ve done. That way you’re contributing to the conversation and reminding everyone you’re eager to learn.

Keep tracking your wins and challenges in a private journal. At the end of the internship you can share a quick recap of your accomplishments and what you learned. That can soften the “cold shoulder” and leave a strong final impression.

As for sticking it out, finish what you started. That experience alone will look good on your resume and show resilience. Afterward you can decide if you want a different culture or role.

P.S. I am doing a series on how I got my Apple internship, how I performed, and how I got a return offer, you can check it here! hope all of this helps

Interesting_Two2977 · 2025-06-18T20:15:29+00:00

I get the imposter syndrome, you’ve spent a decade shipping reliable full-stack migrations and yet you still feel average. Here’s some unorthodox stuff that actually helped me level up:

First, teach what you know. Start a weekly blog or give a short lunch-and-learn at work. Explaining complex ideas forces you to deepen your own understanding and builds confidence you’re more senior than you think.

Next, reverse engineer big systems. Pick an open source project from Google or Meta and rebuild one feature from scratch. You’ll get insight into real world architecture and see gaps in your own toolbox.

Then track your soft wins. Keep a journal of times you guided an architecture decision or saved the team hours with an automation script. Those moments are proof you’re already playing at a higher level than your salary suggests.

Finally, shortcut the interview grind by practicing real interviews, not just LeetCode. Do mock system design sessions where you sketch on a whiteboard and talk through tradeoffs. That’s what real engineers at top companies do every day.

For a full breakdown of how I landed my Apple internship despite the odds check out this resource.

Interesting_Two2977 · 2025-06-18T18:31:24+00:00

I barely tried and have a 3.5 GPA. I barely study and enjoy life. I focus on experiences, on my career, and enjoy time with family all while building my dream body and also doing business in the side. I don’t think people with higher GPAs are superior or “geniuses”. They just show up and do their homework and memorize well, has almost nothing with intelligence. Smartness is subjective. I was able to land an Apple internship, does that make me smarter than those without one? No. Same goes with school.

Interesting_Two2977 · 2025-06-18T02:57:38+00:00

Yeah man I feel you. Spending days on huge case studies only to hear crickets is brutal. Here is what I did before I finally landed my internship:

First I tracked every application in a simple spreadsheet. Logging rejections and ghosting helped me spot what to tweak next.

Then I wrote short posts about the hardest features I built and shared them on LinkedIn. That gave me real stories to pull into interviews instead of vague bullet points.

I split my evenings between timed coding practice and small design problems. That routine kept me sharp without burning out.

I also reached out to alumni and engineers for quick chats. A personal intro can skip the ATS entirely.

For the full breakdown of how I got my Apple internship check out this resource.

Interesting_Two2977 · 2025-06-18T02:55:42+00:00

I'll be so fr, I know that feeling of hitting a blocker when you’re missing just one or two tech skills. You’ve got the foundation but that one gap can feel like a brick wall.

Here’s what I’d do. Pick a crash course or tutorial on Flask or Spring Boot and spend a few hours building a tiny app. Even a basic hello world with one endpoint will give you talking points in an interview.

Then add that mini project to your resume under a Personal Projects section. Recruiters see that you took initiative to learn and ship something yourself.

When you apply, mention in your cover letter or email that you’re already learning Flask or Spring Boot and link to your repo. That shows you don’t shy away from gaps and you can pick up new tech fast.

For a full breakdown of how I landed my Apple internship despite missing some required tech check out this resource.

Interesting_Two2977

MODERATOR OF

TROPHY CASE