Not the OP but I didn't pick up the senior title till I was 8 years in. I don't know you so you might be _that_ good but there's a lot more to being a senior de

Not the OP but I didn't pick up the senior title till I was 8 years in. I don't know you so you might be _that_ good but there's a lot more to being a senior dev than just being really good at crushing code. A lot of your job is unblocking other teammates and generally rising the productivity of your team as a whole. In other words you are a "10x developer" by virtue of what you do for others rather than just what you yourself can output on your own. There's also stuff that comes from hard earned experience such as _not_ picking x hot new framework (which will likely be abandoned by its maintainer 6 months from now) or deciding when to buy vs build (I've worked with developers who literally tried to rewrite Apples layout engine...). I am not saying you aren't ready but I've not personally encountered anyone 4 years into their career that was. As for an example resume, I am one of the people tasked with reviewing senior developer resumes at my job and here is my advice: One. Page. Seriously. Keep it to one. You will stand out right away by virtue of that. Beyond that we really only care about your relevant skills and recent experience so put an array of your skills front and center and then follow it with a good amount of detail about your current/last position. The rest you can be pretty sparse on because it only gets a glance. Best of luck to you.