akinsmosu's avatar

PHP/Laravel vs. C#/.NET?

Background

I'm 44, single dad, transitioning from military into full-time software development. For the last 4 years I've been going to school full-time and I'm graduating with my CS degree in December.

Over the last 2 years I've worked part-time for my university as a developer in C#/.NET. I really like Laravel and I'm working on a great project with for the College of Engineering at my school that's going to be in-use when I finish it, but I don't have any professional experience with it.

Question

I don't live near a major tech hub (I'm in Corvallis, OR) and can't really relocate due to family constraints so I'll be looking at remote/hybrid (mostly remote) positions. In today's job market, is it smarter to double-down on my .NET experience even if I don't enjoy it as much or build out a great Laravel portfolio and try to pursue jobs that way?

(additional context: I'm not overly focused on salary because I have some continuing income from the military and benefits aren't a dealbreaker so contract work is ok, even part-time if needed)

0 likes
4 replies
LaryAI's avatar
LaryAI
AI
6 months ago
Level 58

Absolutely fantastic background and very thoughtful question! Here’s a focused breakdown to help you decide between doubling-down on C#/.NET or building up your Laravel/PHP skills for the job market—specifically for remote work.

1. Market Demand & Opportunity

  • .NET/C#:

    • .NET (especially with C#) continues to be a powerhouse in enterprise environments (corporate, government, healthcare, etc.).
    • There are typically more full-time, stable roles, and these companies often have larger engineering teams.
    • .NET remote jobs are plentiful, but some organizations still want “hybrid” for security/compliance reasons.
    • Your experience here is already professional—a BIG competitive edge.

  • Laravel/PHP:

    • Laravel is the most popular PHP framework, loved for developer experience and productivity.
    • PHP jobs are diverse: startups, marketing agencies, SaaS companies, and lots of contract/freelance openings.
    • Remote Laravel jobs are very common (often international teams/asynchronous work).

2. Enjoyment vs. Experience

  • Loving your tech stack keeps you motivated and improves job satisfaction.
  • On your resume, proven .NET/C# paid experience trumps a single big Laravel project if you’re after traditional roles.
  • However, an impressive Laravel portfolio+side projects can absolutely open doors, especially at startups and agencies.

3. Your Unique Situation (Corvallis, OR, remote/hybrid, salary needs)

  • You’re not bound by salary/benefits, and are open to contract work—this is HUGE flexibility! Many Laravel and PHP positions are contract/part-time/freelance.
  • .NET roles often skew towards companies that expect more traditional employment (FT, benefits), though flexible exceptions exist.

4. What Does the Data Say?

  • Browse Indeed, LinkedIn, and We Work Remotely for keywords like "Remote .NET", "Remote C#", "Remote Laravel", "Remote PHP".
  • Filter for your timezone if necessary.
  • You’ll find a higher volume of .NET positions, but Laravel/PHP roles have lower entry barriers for contract/part-time/freelance gigs.

5. Concrete Steps & Recommendation

If you need a strategic answer:
Double-down on C#/.NET as your “bread and butter,” since it gives you a rock-solid foundation and professional credibility—keep applying for remote FT/hybrid jobs here.

But,
Actively cultivate your Laravel portfolio and presence. Ship your college project, post about it, do a couple more smaller freelance/fake projects (could even be apps addressing veteran or dad-life needs!), and start applying for contract/freelance Laravel jobs (you could even target international or upwork-style gigs).

Sample Hybrid Approach (Highly Recommended!):

- Apply for remote/hybrid .NET jobs aggressively, using your paid experience.
- Build and showcase your Laravel project(s) on GitHub/portfolio site, narrating each project’s impact/tech details.
- Pursue small contract/freelance jobs in Laravel (many are remote!), even part-time.
- Optionally: Blend them—there are jobs needing *both* Laravel API and .NET (for microservices/interoperability).

Why this is smart:

  • Keeps all doors open during a tough job market.
  • Grows your professional network in both communities.
  • Lets you “try before you buy” with Laravel income, without risking financial stability.
  • Shows employers you’re versatile and self-motivated.

Final Thought

You never know which path will “hit” first. Your .NET experience will always have value. However, Laravel/PHP can be your ticket to more enjoyable, flexible, and sometimes faster-to-land remote projects. Both are in demand; optimize for jobs you enjoy and your unique life needs.

Good luck, and congrats on your impending graduation! If you want specific code/project advice, or which Laravel portfolio projects stand out, post again—happy to help!

jlrdw's avatar

My advise is go technology first, meaning PHP so you can perhaps do other frameworks if required. If you get a good understanding of PHP and Laravel, another framework is fairly easy to adapt to.

I did java technology for years and liked it. When I very shortly messed with .net, I said no. They seem to want to change things way too much. But of course it's your decision.

1 like
akinsmosu's avatar

Thanks. Yeah, I definitely prefer PHP/Laravel, but it seems like companies now have the luxury of being super-specific about tech stack requirements and C#/.NET is the only stuff I've been paid to do

jlrdw's avatar

Definitely keep your c# skills up, I know how versions in .net core change.

I couldn't believe the code just to upload some images with other data fields. Whereas 15 or so years ago it was much easier.

I won't even go deeply into the learning curve of Spring Framework

Please or to participate in this conversation.