> What's wrong with that?
You said it yourself: "Each part of the phrase sounds like something an experienced developer should strive for". Nobody will ever write the opposite. So it signals nothing.
You said it yourself: "Each part of the phrase sounds like something an experienced developer should strive for". Nobody will ever write the opposite. So it signals nothing.
If a candidate is totally junior and still writes that they are are a junior an "experienced software architect with a proven track record of delivering high quality and performant..." but fails to back it up, they end up being judged next to people who actually do have this experience.
In that case, it could be better to emphasize the "willing to learn quickly"/"excellent team member"/soft skills aspect to set expectations right, and/or develop better technical skills so a candidate can actually claim that. So, it's only really beneficial to write if you actually do have experience, and thus could be a worthwhile signal to include at least once in the resume to show you're at that level.