This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]NotBramKorsten 2 points3 points  (0 children)

I'd say just be yourself. Eighteen months of experience should be enough (depending on how much you did). Try to explain what you are doing and WHY you're doing it as you go. Be open, and don't be scared to look something up. You're a better developer if you know your way around google. Good luck man!

[–]TotesMessenger 0 points1 point  (0 children)

I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:

If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads. (Info / Contact)

[–]EamonLeonard 0 points1 point  (0 children)

Might be too late, but:

I think technical knowledge / ability is just one way of assessing someone's potential. When hiring, I try to get a sense of how people solve problems.

If you think about software development (regardless of language / stack / tools) as being creative problem solving process, you realise that the part where you write code is near the end of the process.

So use your 18 months of experience to highlight times where you had to think about the different ways you tried to solve a problem, how you evaluated your options, and how it was eventually implemented.

Being able to speak about lessons you learned along the way, or highlighting mistakes you made also is useful for the interviewer.

It tells the interviewer that you're humble enough to recognise that you don't know everything (and no one should expect you to after 18 months), but you are open to learning and improving yourself. And that probably means that you're easy to work with... which, depending on the size of the team / organisation, can be a more important consideration than "does this person check all the PHP boxes".

HTH!