Interview for the senior positions if they're coming your way, as long as you're not misleading anyone about your actual experience, you'll be fine.

Relevant thread from this week: How fresh grads with zero experience get hired as senior engineers - https://news.ycombinator.com/item?id=30303891

The thing about leveling is there's no standard.

In general, higher titles are more easily attainable at smaller companies. Senior at one company could be equivalent to intermediate at another or staff at a third.

Consequently, deciding where you fall at level-wise, is the job of the company you're interviewing at, not your own. Your job is to talk through, and accurately represent, the experience that you have, and their job is to assess that experience with respect to their leveling framework / matrix.

For reference examples, check out GitLab's [1][2], or progression.fyi [3] for a collection of others.

That said, I would agree with others in this thread on the junior or junior to intermediate guesstimation.

[1]: https://about.gitlab.com/handbook/engineering/career-develop...

[2]: https://about.gitlab.com/job-families/engineering/

[3]: https://www.progression.fyi/

Interview for all the ones you're interested in regardless of title. The definitions of what constitutes one level versus another are wild (even internally at my company the differences can be crazy).

"lied about part-time remote"

I work for a company that has a reputation for doing the right thing. They lie often. My conclusion is that almost every company does, but it's just a matter of if it negatively affected you and you stuck around long enough (both necessary so you could observe it).

Knowing nothing else then what you list, I'd consider you junior to maybe intermediate, it would all depend on how you do in an interview.

I'd echo a couple of comments, apply for roles you think fit your skills. Startups call people with 2-3 years senior all the time and I'd not consider the vast majority of people filling those roles as senior. It all depends on their categorization.

I've seen people create career levels in startups that are totally out of line with reality but they use them. So worry less about title and just make sure based on the job you think you can do the work and deliver. Don't be afraid to reach "up" though, plenty of people with your type of experience can out deliver more senior candidates, it all depends on the person.

I've managed people who were performing at a senior level after 3 years of experience and I've managed people who were performing at a junior level after 10 years of experience. Both categories are outliers but they do exist.

As long as you are truthful and honest in your resume and your interviews I would just let people make their own determination. If you can get a senior level role take it.

Interview for the senior roles, be 100% open and honest and let them make you an offer. Many programmers don't add as much value as you might think, your capability to deliver is highly valuable even if you're still inexperienced with particular technologies.

If you interview for a couple of these position, you'll have a much better idea whether or not you are overselling yourself.

You might discover that you are overselling yourself, but only slightly. If that's the case you may be able to level-up that gap quickly.

You do realize that most recruiters don’t have the first damn clue what engineers do and are just searching for keywords in your online profile right?

yes I know

but I also know that some of them know how to code and actually read my resume, so I'm really wondering if I'm overselling myself

Take what you can get. Let other people worry about it.

I heard some great advice a long time ago. Always let them reject you. Never do it for them.