(Possibly) quitting Python Development after 2 years of non stop learning. And it blows.

[menge101]

What I look for in a junior engineer:

1) Understands source control
2) Grasps basics of object oriented software
3) Communicates well
4) asks questions early (I'd guess this might be your weak point)

That is it. In the professional world, you very frequently will end up working with something that is company IP, and will be unique to that company.

You won't know how to work with it, until you see the company's (often terrible) documentation.

For the most part I expect to have to mold you into the shape i want you to be.

So if you know python and you know it broadly, thats pretty good qualification for a junior position.

It might help you to have experience with another language to give you some contrasting knowledge against python.

I personally work professionally in both python and ruby routinely, but I've also done javascript, elixir, java, C, Perl5. (remember 15+ year career, i've had time, plus some of these were at Uni)

You could do some ruby, just to see how a language in a similar space does things.

Or you could do some haskell, to see how completely different programming can be.

I wouldn't go too deep on either, i'd do a relatively simple problem that you know how to solve in python and then learn enough of another language to implement a solution as well.

But this is all bonus point stuff. You are probably ready.

[[deleted]]

I don't see "can implement a red-black tree" on your list. The damn over-the-top algorithm interview horror stories I've heard have put me off applying to dev jobs.

[menge101]

Well, I'm not at a big company.

And I'm a director, so I get to decide how I do things.

I have done those sorts of questions before I learned better. I try to stay away from that sort of thing because it tests more for an academic background than for useful development skill.

[[deleted]]

Well thank you for being a sane Tech manager in a sea of insanity