I'm actively looking for a new job, after take a break for 2 months. Currently I'm faced with the "problem" that most of the positions that I find aren't interesting to me, in addition to me to being really sure of what i want to do.

Things that currently interest me:
- functional programming

Things that I would like to avoid:
- C# / Java
- frondend stuff
- golang
- windows


What makes it even harder is that I'm not really good at "selling" myself in an interview :/ Telling someone that I'll probably not be as fast as others, because I'll end up spending time cleaning things up and/or trying/discovery new things. While this is true and in my experience so far leads to a better product and produces results, it's not something that most HR personals like to hear. Anyone any ideas how to frame this better?

I forgot to add that I'm looking for a 80% full remote position

@xanderio You're good at keeping the big picture in mind, taking care of developer experience and maintainability.

Don't mention that this makes you take more time to develop features, that's obvious and does not need to be said explicitly.

@xanderio I would not attempt to frame this better unless I'm (in your position) determined to get that position.

Move fast and break things and similar as a default is an orange flag.

Nonetheless, you could say something along the lines of "I see potential breaking points in systems and like to think about how to avoid breakage in the first place, in a way that others don't need to think about it any more"

@xanderio I'd maybe frame it like this:
Software tends to be around for a long time, so I rather focus on the long term maintainability, instead of the short term quick fixes. This will lead to my teammates having an easier time understanding and developing our software and will result in a better product and happier customers overall.🙂

@xanderio Specific examples can really help. It backs up what you’re saying and you may also find it easier to discuss something concrete.

When it comes to this topic, people on the other side of the table are often concerned that what you’re saying is “I gold-plate things and can’t prioritise” so bring up how you balance long-term vs short-term decisions to reassure them. Examples can be used here too if there are times you got the balance wrong and learnt something from it.

@xanderio Some suggestions and thoughts on this: There's no need to actively and literally tell the HR person that "you will probably not be as fast as others" (which is anyhow only true when viewing the short term, not a framing you are obligated to use!), it suffices to tell them that you do your work diligently and thoroughly (instead of doing the opposite, which would be a hasty and spotty job). A good HR person will also be able to recognize that different people work differently, so implicitly they might very well be aware that what you're implying is that in the short term you might be "slower" than others, but given the right leadership this is no drawback at all, as you wrote yourself already. I think the important point about the framing is just to demonstrate that you are confident that your style of working produces solid results, and that if you are managed correctly within your team, your particular working style will be an advantageous one for your employer. Lastly: There are probably some shops out there that are solely interested in quick results (and will pick their employees accordingly), but this is then simply a place where you would not want to work anyway. :)

@xanderio does this mean you won’t consider 100% remote work?

@xanderio while this is totally you choice, i would like to ask why no golang?

@xanderio I don’t see #php on that list tones of businesses looking for people there

@xanderio You need to look for a job at Mozilla or Redhat to work on linux kernel perhaps.

Sign in to participate in the conversation – a Fediverse instance for & by the Chaos community