I appreciate your perspective here. However, there’s a few issues with the “just do it” approach, and a few with some of the specific things you suggest.
We’ve taken this long to get going, as @becky82 says, because we’ve spent that time here hammering out a specification. That’s a necessary step - to develop a product without a specification is to invite bugs, missing features, and unconsidered use-cases later down the line which could have been solved earlier.
This has been discussed. We’ve concluded that we’re building a similar type of product, but it won’t be exactly like SO - there are some key features and organisational differences that we want to have, because it’ll make our product better.
We probably won’t do that, for a number of reasons, not least because our idea of “reputation” is going to be rather different to the SE idea. We may do something to the same sort of effect, though - sort of like an association bonus, to get users who come over from SE over the initial hurdles.
That’s… up for debate. I don’t think we’ve had a specific discussion about this, but because it’s not a restriction of the software but of community policy, we won’t get to discussing things like this in detail until we’re closer to being able to host communities.
Possible, but a jobs board isn’t part of our MVP plan (and shouldn’t be). In keeping with the spirit of getting it done, we’re looking to build a minimum viable product first, and then add features (which may include jobs) on top of that.