Difference between revisions of "NextJump"

Revision as of 21:16, 16 August 2011

I worked at NextJump [1] during the summer of 2011 in New York City. NextJump provides corporate perks portals for much of the Fortune 500. They also produce savings portals for several membership organizations such as AARP and Mastercard. I was a product development intern. I was hired as a coder, to build website front ends and back-ends in PHP, Microsoft SQL Server, and JavaScript. I also managed our 3-person intern team in the competition to build a mobile version of the product.

I liked this summer because it was the exact opposite of Deutsche Bahn. NextJump prides itself on being small and acting fast. I was also in a coding role, as opposed to last summer. I still tried to be more than a coder and use my product development experience to provide input on the direction of the products I worked on. Since NextJump works so fast, the fine details of development have to be solved as you are implementing the product. Often someone comes to you with an issue that you need to solve and implement that day. I like that I often had that freedom to shape the product as I was building it.

The interns were also challenged to build a mobile web version of the main product. The 10 interns were split into 3 teams. The other teams members agreed that I should be product manager. This was another great experience to managed a team to produce a project. I also made the initial wireframe layout of the site, which the CEO and the Strategy Committee really liked. They also liked our visual design which another member of the team made. Ultimatly a mobile site which blends elements of all 3 sites will be released.

I think NextJump works a bit too fast and has too much pressure to release daily. For example, something could be done in 3 days releasing the code every day, or it could be done in 2 days, releasing only after the second day. I think the later is overall more productive. I still think getting stuff out there and iterating quickly is good. However, a little more care could be put into quality. Also care should be taken that users are not confused by too many changes. Facebook users always initially hate the redesign. If you think about some of the top sales websites, their UI has bairly changed. Amazon has slowly optimized stuff, such as an AJAX results list, but the basic experience has barely changed. NextJump believes that it is still growing and still in the period of constant change.

The code base is also not very clean because NextJump does not say no to anyone - on both sides of the networks. While most companies refuse to make one-off changes, NextJump is always seeking to optimize. This naturally makes the code base a mess.

I also really liked the office environment - it is one big floor of cubes. Everyone is very friendly with each other and knows what the other group is up to. This is in sharp contrast to the 2 other places I worked previously. I also really like the programs they have set up to make sure that everyone stays informed. They have a quick company-wide meeting every Monday. While this can work poorly, they keep it short so it works. I also like the every-other Friday reflections session. I think this is because I like thinking about other parts of the business, but I realize not everyone shares my enthusiasm. What they call "Project Awesome" is also very cool. It's essentially a company-wide Tumblr where everyone can post cool work-related things and other users comment on it.

Also, everyone was very good and did this assigned jobs. This was much better than Deutsche Bahn, as well as State Street. I think this is the environment I want to be in when I work full time. I've also realized that the more a company pay you, the more the company values you AND the more interesting, and I think fun, the job is.

Pictures

flickr > theplaz > NextJump Set

P1020962

[Slideshow]

[Map]