I work in the tech field building backend systems for a large retailer. When our team looks for members, we look at different things:
Technical knowledge: you'll need to know your frameworks and basic sql. Youll need to know how to do the basic infra things like logging into servers, transferring files, setting up basic infra and platform. The reasoning here is that we need team members to help take off the work load off our over capacitied team members, and so if those team members need to show you how to scp a file over, or select the first 40 rows from a table, then its not alleviating any workload.
Problem solving: in large companies, there are many applications that are custom integrated between each other, in either batch or realtime fashion. Our team usually wants people who can think on their feet, and investigate / solve when issues arise, say due to a particular integration that is down. In the spirit of offloading work, its again not work offloaded if your bugging the existing team members everytime your dev site doesnt load or ends in 500. Other types of problem solving include things that can speedup future occurances of the same issue. For example if an app you built like crashed, and say there was quite a bit of research required to identify that it was your app that was the cause, then finding ways to troubleshoot such as writing logs or database entries would be a problem solving solution, so that say next time a similar thing occurred, it would be readily easy to proove or disproove whether or not it was due to the same thing previously.
My team hates those team members that are hell bent on a particular solution and wont budge. We also dont favor those who just "sell" on using something, but never tried it themselves, only to find out it doesnt work well after many hours later of testing. But since we're in retail and not say in r&d areas, that's prob why we're favored more on proven results than experimental stuff.
Of course the type of position (intern, junior, senior) would have different expectations of competency.
JonathanK got a reaction from voiha in Which basic knowledge do I need to get my first junior JAVA job?
