A lot of the time, Senior is less about technical skills, and more about soft skills. Consider where you are with subjects such as:
Communicating with coworkers,
Time management,
Planning new features,
Debugging (especially difficult bugs),
Testing,
Code review,
Writing documentation,
Handling bug reports,
Shipping code,
Project management,
VCS and CI/CD pipeline.
Which ones are relevant depends heavily on your specialty, field, and tech stack, but it's good to be comfortable with however the above manifests for your wheelhouse.
You should also be comfortable with the idiomatic patterns for the technologies you use.
Beyond this, a senior should be comfortable with the fundamental, underlying principles relevant to their specialty. For example, some senior positions would expect you to understand the impact that a linked-list-based data structure would have on performance in a particular situation, versus an array-based data structure. Others might need you to understand the pros/cons of TCP and UDP, or what the pitfalls are for CRUD APIs.
In short, senior developers understand the whys of practices and patterns, and can use that knowledge to independently devise solutions to sticky problems. A senior will be solving "high-friction problems", where there is little-to-no precedence or documentation to directly inform them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A lot of the time, Senior is less about technical skills, and more about soft skills. Consider where you are with subjects such as:
Which ones are relevant depends heavily on your specialty, field, and tech stack, but it's good to be comfortable with however the above manifests for your wheelhouse.
You should also be comfortable with the idiomatic patterns for the technologies you use.
Beyond this, a senior should be comfortable with the fundamental, underlying principles relevant to their specialty. For example, some senior positions would expect you to understand the impact that a linked-list-based data structure would have on performance in a particular situation, versus an array-based data structure. Others might need you to understand the pros/cons of TCP and UDP, or what the pitfalls are for CRUD APIs.
In short, senior developers understand the whys of practices and patterns, and can use that knowledge to independently devise solutions to sticky problems. A senior will be solving "high-friction problems", where there is little-to-no precedence or documentation to directly inform them.