I'm a web developer with hands-on skills in creating full-stack web applications, mainly using PHP, MySQL, and Laravel. When browsing job listings in the Philippines and abroad, I've noticed titles like 'Fullstack Engineer' and 'Fullstack Software Engineer' that sometimes include responsibilities beyond just web development, mentioning languages such as Java, C#, and Python. I'm curious about what these titles actually entail and which job titles are focused specifically on mobile and desktop applications. Essentially, I want to steer clear of positions requiring mobile or desktop app development and focus solely on web app development instead. Here are some of the titles I'm confused about: 1. Fullstack Engineer 2. Fullstack Software Engineer 3. Fullstack Developer 4. Frontend Engineer 5. Software Engineer (Full Stack) 6. Full Stack Web Developer
5 Answers
At my company, the majority of us are labeled as full stack. We have a couple of dedicated front-end devs, but most of the work is backend APIs or internal web apps. Honestly, calling someone 'full stack' often just means they're taking on multiple roles without the salary benefits of having separate specialists.
In general, a 'stack' refers to the layers used in an application, like front-end frameworks paired with back-end setups and databases. So when you see these titles, it’s often adaptable to project needs. Fullstack typically points to web apps, but if the project requires a mobile or desktop component, that’ll be included in the stack as well. Hope that clarifies things a bit!
If your main focus is PHP, you might want to ignore the specific roles unless they indicate a level like Junior or Senior. PHP isn’t typically used for mobile or desktop apps, so you should be mostly safe! Just be cautious of any front-end roles that don't really align with your skills in PHP.
It basically means it's a tough job. You have to wear many hats!
Honestly, I feel like 'full stack engineer' is kind of a misleading title. It usually just means you can handle front-end, back-end, and APIs. A good engineer should at least grasp the basic stack. But if you're talking about complex systems, you often need separate teams for front-end and back-end work to manage everything effectively.
But there are definitely smaller projects where one developer does both front-end and back-end. Having that range of skills is really valuable—especially when designing systems! It helps you understand potential bottlenecks better.
And don't forget, even if you’re mainly into web apps, knowing Java, C#, and the JavaScript ecosystem is super important. PHP is starting to feel a bit dated, so branching out will help with modern dev jobs.
Exactly, the front-end landscape can be pretty hectic. But if you’re interested in back-end stuff for APIs in mobile apps, it’s worth considering that—it could expand your skillset.