Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

motinska94's avatar

I just got my first job offer as a laravel developer. And I'm having an impostor syndrome/crysis..

I have a grand total of 3 months of work experience. I was a jr-jr laravel dev back then and I knew pretty much nothing except connecting a route to a view through a controller. Nowadays I mainly work on my own projects and have some freelance gigs from time to time with Laravel.

The thing is; I can build things. I am at a point where I can build pretty much anything there is to build with Laravel. But I'm definitely not a professional. I don't write tests for example. So far I've built many Laravel apps and never written a test in my life. I don't know what service container means, I tried to use websockets once and I failed miserably. And these are only the things that I know that I don't know.

I wasn't even looking for a job but apparently my father told his friend about me and he had a friend who was looking for a backend developer. From what I understood from the 10 minute WhatsApp call interview-like thing I had with the guy, they're a company that makes mobile games and they're using PHP/Laravel as backend.

He asked me "Let's say I have a script for a lotto game written in Laravel, would you be able to understand and edit the code?" And I said "I can write a lotto game from scratch with Laravel in less than a week". So cringe, I know. I wanted to kick myself as soon as those words left my mouth. But apparently that was exactly what he wanted to hear, because he said that me saying that assured him and that he'll talk to the ceo and get back to me tomorrow, and because I said that, he thinks "it'll most likely be positive".

I am wide open to any suggestions you have. Thanks.

0 likes
3 replies
mike_isp's avatar

It's good that you have a sense of what you don't know. I would definitely focus on at least some level of testing. At the very least having tests for your CRUD like actions where you factory some fake data, hit a route (and therefor the controller) and expect the route to return OK and the DB to have or not have the data you expect. That's hugely better than no tests before you get more in depth.

Also, stay humble. The thing about coding for yourself is you'll gravitate towards problems you know you can solve. It can be a different bag of onions when the requirements come from others.

1 like
MAnasShakoor's avatar

I think joining a job is quite important to understand and adopt the industry standards.So, if you get a good pacakage then go for it.It will help you a lot to work like a professional.

Please or to participate in this conversation.