[pixelmonkey]

I'm the CTO at Parse.ly, you can visit us at https://parse.ly.

We run a fully distributed team. We have commented on our culture around this in these two blog posts--

The How & Why of Parse.ly's Fully Distributed Team:

https://blog.parse.ly/post/3203/the-how-and-why-of-parse-lys...

Fully Remote, But Here For Each Other:

https://blog.parse.ly/post/4736/mission/

We actually recommend "Rework" and "Remote" as two reading materials for new hires when they join the company.

As for financing, Parse.ly is no longer a bootstrapped company, but we do take a "lean" approach to SaaS VC fundraising.

My co-founder wrote a bit about this in this post--

A Different Way — Thoughtful Financing, Or Why We Said "No" to a Lot of Money:

https://blog.parse.ly/post/6282/why-we-said-no-vc-money/

[frankquist]

Slightly offtopic but I went to your homepage to check it out. Immediately loved how it looked, but found it hard to find out what products are actually on offer until I went to the separate product pages. In the first two screens of the homepage, the general gist of your products doesn't become clear to me, only your specific Facebook/AMP product. After the first screen ("Do incredible things with your data") I expected the second screen to tell me what those were, and so I would've thought you offered only AMP/facebook stuff, hadn't I noticed later on that it was a "product update".

Just my 2 cts.

[pixelmonkey]

Thanks for the feedback. Interestingly, we plan on revamping our homepage and flow a bit in early 2018 to make that sort of thing clearer. Appreciate the comment!

[corobo]

Only a cheeky jab but in fairness it was the first thing I saw in your job ads

> Parse.ly is looking for a motivated Business Development Representative [..] The position will be based in our New York City headquarters

Do you have any concerns of having a HQ and remote workers? From what I've seen and heard from mixed businesses the remote workers tend to become second class citizens when it comes to benefits/promotions/salary/etc. How do you avoid that, if you do?

[pixelmonkey]

Great question!

We have two departments, broadly "Business" and "Product". With over 60 full-timers working with the company now, it's important to recognize that these two departments have different cultures, and BDRs joining the Business team end up having a bit of a different experience than, say, a Python programmer joining our Product team.

The "Business" department is centered around sales, marketing, finance, and operations. It only formed as a (large) department of its own in the last 3 years and it has a significant presence in NYC. However, business team hires are even told that "NYC is not HQ" on their first day, and that a better way to think of the office is as the "NYC Internet Cafe". It's a nice Internet Cafe, though! Gigabit Internet, mesh wifi network, and standard issue bamboo sit/stand desks.

The "Product" department is centered around engineering (mostly Python programming), user experience (mostly JavaScript programming) and design (graphic/web). I'm one of the two co-founders of the company and I lead the Product team, and, importantly, I am not based in NYC. This team is 100% remote, and has about 25 people on it. Everyone on this team works either from their (tailored/optimized) home office or from a co-working space. There are actually zero full-time hires on Product that are based in NYC -- this usually elicits some surprise from office visitors.

There is a legitimate concern for some of the Business team hires that if you are not based in NYC but your team lead or some of your team colleagues are, you might suffer from "out of band communication". We try to reduce this by forcing people in the office to use Slack and video conferencing (our conference rooms are set up for GHangouts and Zoom.us) instead of "shout-net" (that is, shouting rudely across the office). This is only a concern on our marketing and support teams, where they have a geographically spread-out team but with a lot of folks in NYC, as well. But they've navigated it well. It doesn't affect our Product team in the slightest because, as I mentioned, we have no team members in NYC and "NYC is just an Internet cafe".

Funny enough, one of our highest-performing salespeople had her best year ever while doing "Remote Year". She wrote about her experience on Remote Year here: https://blog.parse.ly/post/3538/digital-nomad-sales/

We do sometimes use NYC as a retreat location for our Product team. Since it's an easy city to fly to and we have co-working space available via the office, it's often used for week-long hacking sessions of small sub-teams on Product.

p.s. as a result of your comment, I'm going to have the person in charge of hiring Business Development Reps remove 'headquarters' from the job posting -- I think it was just an innocent terminology mistake when drafting the job req.

[corobo]

Thank you for the reply!

Just to note the reason I was asking wasn't to catch you out or anything, I'm trying to encourage a remote work situation at the day job but it always comes down to "we need everyone in the office because communication". Always good to have a few ideas ready to roll in the pocket :)

[hartjer]

Why Rework? I'm hoping I missed something the first time I read it, it seems like it would had been better as an office calendar than a book.

[pixelmonkey]

I think both Rework and Remote are quick and easy reads that espouse a philosophy toward work that is anti-political, individual contributor focused, and no-BS. That's all I really need for a new hire to feel, so it works for me!