Product Manager Needed

With things like Kindlepreneur's tool sets, Publisher Rocket, Atticus, and more, I need someone to join the team and help organize and lead the software team in creating improvements to existing tools, as well as the creation of new ones. With a keen eye towards understanding what capabilities or tools we should create, a smidge of creativity, and a strong desire for organization and management, this could be a fun project.

What Does Being a Product Manager Entail?

When it comes to creating new software solutions, or improving existing ones, as is the case here, there are really three positions or groups involved: Product Manager, Project Manager and Software Developers. The software developers are the technical side that will create the project, and the project manager is the one who receives tasking from the Product Manger, and works with the software developers to allocate resources and ensure the developers create the software or tools to the specifications received.

This is where the Product Manager comes into play. The Product Manager will be working directly with myself, to figure out what is best for the users. What tools should be created? How can we improve existing tools? Once they have this in mind, they will work through what it looks like and how it can be done. They'll organize this, and then set forth to communicate with the Project Manager and Software Developers exactly what it is they want. They will tract to ensure what is delivered will work best for the market or community. They will test and check and work to improve until they finally believe the tool or software is exactly what the market will want and best help them.

To explain this further, the Product Manager is someone who is responsible for all facets of product development. It is the product manager's job to come up with a product solution that is valuable to the users, usable by the users, buildable by our software dev team and still viable from a business perspective. They listen to their users/customers/market to understand their problems and how they could possibly solve them. They conduct several experiments and prototypes to test their assumption/hypotheses and various solutions before they actually build the product. They deliver value and test if people are actually using/buying the product.

Basically, the Product Manager will have an awesome programming team at their disposal, and be able to build awesome products or tools to help the target market.

Requirements & Details of the Position:

Now, I know what you're thinking….”Hmm, I'll probably need to be some master coder, or have built software products before.” Nope. Instead its about willingness to grow, excitment in such a case, and a couple of other requirements to foster your growth. While having programming background or previous Product Management is a total bonus, it isn't actually required.

• Expected Number of Hours: 40
• Work from home
• Requires being able to drive to Franklin TN ~1x per month
• Works directly with Dave to create new products and tools

Required Meeting Times:

• Thursday Team meeting at 9:30am CST
• Meet once a month at in Franklin TN
• Morning meetings with the programming team between 6-9am CST

Who We're Looking For

While having a background in programing would help (more so to understand what your programming team would be going through), it is definitely not a requirement. Plus, for those who haven't been a Product Manger, or had direct experience, again this isn't a requirement. However, if you have both, than awesome. But if you're not, then you need to have a strong desire to learn and be motivated and excited about such. We can train and teach you.

• Meticulous organizer
• Analytics mind
• Hates not knowing the status of things
• Hungry to learn
• Extremely dependable

What a Day in the Life Would Look Like as a Product Manager

If you were the Product Manager, here's what a day in the life would look like:

You wake up early at about 6am so as to get a fresh cup of coffee and start your morning. At about 6:30am you have your first meeting with a set of programmers over zoom. In this project, you're currently working with them to finish up on a free online tool that's being made for Kindlepreneur. They've run into a snag and you can see your timeline to completion is moving to the right. They've sent you a beta copy to test, and so you've marked it down to test it and try to break it later in the day.

As that meeting wraps up, you then jump on another morning session with another set of programmers. In this one, you're discussing with them a new project. This will build a chrome app to help with pulling information. They've developed a gantt chart showing you the breakdown and timeline of resources to completion. Hopefully they'll get the User Interface (UI) back to you soon so you can see if it looks good.

Now that your meetings are done with the programming teams, you move over to the creation of a new project that deals with support. Luckily, you've already had a couple of meetings with Dave Chesson, and have already thought out and discussed exactly what needs to happen in this program. Its now time to build out a rudimentary wireframe of the software, and planing out how things will work. Using a program called Balsamiq, you start to lay out its designs and you are writing down the project scope and requirements. If you can complete this, you'll now be able to send a message to the programming company to start building/assembling a new team for this upcoming project.

Now that you've got a good start on that, you look down at your watch, and see its 10am. You decide to go to the gym and pick up lunch on the way back home. After that, you jump on a zoom meeting with Dave to discuss how the projects are going and get feedback on what you have. After the meeting you decide to go over the beta copy given to you in the meeting, and start testing it. As you systematically go through program, you start to find a couple of bugs, and see some areas where it can be improved. You mark this down and send over the information to the programmers via slack.

As it nears 2pm, you decide to check messages from either the support team, or from emails passed on to you, where either the have been messages from users about problems or suggestions about how to improve the program. You collect up the data, and respond where needed. You end your day by sending out messages to the different programming teams with their priorities for the next day.

How to Apply

So, do you want to join a game-changing team, gain great insight into book marketings, and help serve the Kindlepreneur community…all from the comfort of your home?

If so, then just click the link below, fill out the form and we’ll get back to you!