What do I do?<p>I prefer crafting projects myself with a staff engineer's approval. I want to reach out for support when I think is needed. I don't like standups, sync up meetings.<p>I prefer to work with engineers who know what they want to do and like to majorly self run.<p>Software Engineer.<p>My boss expects me to lead junior engineers next year.
Well, you should clearly communicate your career desires to your manager, for starters. If you don't want a leadership position and you're being groomed for it, say so. As for meetings, they're for your manager's benefit, so they have visibility on what you're working on and can identify blockages in a timely fashion. More broadly, I would suggest finding a smaller company or start-up that doesn't have a lot of formalized processes and will allow you to run with something.<p>That said, I've got bad news for you: most people like working alone. Everyone wants to "own" the thing they're working on and not depend on others. It's not special, and it's really a baseline expectation of a programmer. What companies want is team players who are often fun, light and friendly, actively work to build trust with a team through socialization, promote good practices and patterns and don't begrudge the fact that a portion of their day is to be spent in meetings, reviewing others' code and generally communicating. These behaviors increase in value in a larger organization with heavy processes in place to compensate for scale and variable talent.
Go into contracting. At some point in my career I decided that I did not like meetings either. While still in a job, I started advertising my skills online, and offering them as a freelancer/contractor. When some of my content caught on, and generated interests with potential employers/clients, I was able to pick and choose on both terms and compensation. It moved me from being a senior with 20-30hrs of meetings per week, to 2-4 hrs of meetings per week.
Become a contractor and focus on staff aug with yourself; charge a high hourly rate and have a focus.<p>I did this for years and it was great: I got to work with good engineers, didn't have to manage or mentor anyone, worked extra when I wanted to, got a good hourly rate.<p>Unless of course you are in the USA and need good health insurance and the exchange doesn't meet your needs. But otherwise, this is a good path for a half decade or more.
Go contractor!<p>You can bill up to four times as much per hour and become respected for competence in your niche.<p>Finding work sucks at first, though after a while you will develop long term relationships which are consistent and flexible.<p>I’ve had my #1 client for ten years and can do as much or little work as I want! I’ve only visited their office once every few years. It’s such a good relationship my client let’s me run my projects however I think appropriate.<p>Just remember, do the work!
You took time and effort to learn engineering, or whatever you do.<p>You have to spend time learning how to communicate, work with team members. Learn how to intereact with others. It is do-able. There are many reasons why you don't like to work as a team, none of the reasons are very good and will hold you back in your career.
As a CTO at a startup I use a flavour of this.<p><a href="http://www.engineeringladders.com/" rel="nofollow">http://www.engineeringladders.com/</a><p>There is a difference between <i>leading</i>, <i>managing</i> and <i>mentoring</i> or <i>coaching</i> juniors.<p>Maybe using a flavour of the above in your conversation with your boss will help?