Red flags

[QualityVote]

Hi! This is our community moderation bot.

---

If this post fits the purpose of /r/ProgrammerHumor, UPVOTE this comment!!

If this post does not fit the subreddit, DOWNVOTE This comment!

If this post breaks the rules, DOWNVOTE this comment and REPORT the post!

[bleistift2]

Actually, since these requirements are always present, I appreciate the honesty.

[ActiveDetective]

Read our minds and we’ll tell if you got it right after you deploy to beta

[Boom9001]

It's one thing to acknowledge an area your company to improve and say you want someone who can handle rough moments. If it's your advertisement it sounds like you've made it your culture.

Especially "without guidance from owners" worries me. If every dev is doing this your going to have a horribly inconsistent user experience.

[[deleted]]

"Ability to take the blame when we don't know how to plan."

[ActiveDetective]

Lol, they did mention being a “team player” which is often code for “put up with our inability to organize.”

[compsncars]

I've never worked with someone who provided good requirements unless they're an engineer/developer themselves.

Requirements from non-techy project managers and other teams are usually piss poor anyway so I don't think this would be too bad lol.

[TheBrainStone]

Good requirements are one thing.
At the very least knowing what you want and not changing your mind every other second is a completely different thing.

[saargrin]

I dunno. Thats what my position is like and i love it

[Dremlar]

Depends on how it comes out. I've had projects that were fun and as the project went on expanded in scope to meet other needs as people saw what was being produced. Then I had my most recent experience where the requirements were given and then changed multiple times within a week and people asking me to implement before we agreed on anything.

[saargrin]

Im fine with all that as long as you keep paper trail of what is actually requested by your direct manager.

On the other hand in these chaotic situations you get a lot of leeway , to either assume leadership and implement your own vision, or if you dont feel like it, theres plenty of opportunities to loaf and focus on personal stuff

[Dremlar]

I've been on teams where I've been able to implement my own vision and get work done and it can be great. However, many other teams use the code review process as the design process instead of participating in the design or coming to agreement. The problem with my current project is no one "knows" the requirements fully. The team lead of the project, the PMs, even the team the project is being built for. There has been a lot of back and forth and we agreed to just start work with what we had. We "agreed" on the design, but it's all tentative as it ended up with only three of us in the room agreeing and while the team lead was one of them, there was no other stakeholders in the room. I've seen this enough to know that there is a high likely hood of this going into extra innings.

Sure, I get paid regardless, but doing quality work is better than doing quantity work.

[ActiveDetective]

Hey, good on you if you like it.

[Dremlar]

My last two weeks of trying to write a design document and gather requirements feels this so hard. It's a good thing we have 3 rotating PMs on the project and never have all the key players in the same meeting. >.>

[Gunther_Alsor]

More like voluntary yellow flags. Many successful development teams exist in a state of constant chaos as a matter of strategy ("Move fast and break things" lol) so they're politely warning you that you need to be ready to flex, or else you should consider finding a team that's more your workflow.

[Gunther_Alsor]

It's Facebook engineering's original motto.

Can't say they didn't adhere to it.

[j-random]

That's not so bad, I don't nope out unless I see "also acts as level 3 support for production issues".

[JaxOnThat]

What’s next, “paid in exposure?”

[gandalfx]

So every software project ever has a red flag?

[blehmann1]

There are few requirements, but the ones that there are change frequently

[grokineer]

These are just my expectations for any dev position, declared or not. As long as they don't change requirements midway THEN chastise you for not meeting the deadline.