MarkedUp’s Core Values when it Comes to Software Developers

With the first version of our product just about ready to go to market, we’re thinking a lot more about recruiting and how we want to expand our team at MarkedUp.

MarkedUp is a developer-centric company: we’re building products for developers, by developers. Given that, everyone on the team should have no trouble understanding what it’s like to be in the shoes of our customers (Windows 8 developers.)

So naturally, top of mind for us is recruiting developers – specifically .NET and HTML5 / JS developers who want to make a difference at an early stage company and tackle tough problems like large-scale analytics, data visualization, building developer-facing SDKs and services, and more.

MarkedUp’s business is deeply technical, and so thus the culture we’re building follows suit – and everyone we ultimately want to hire should share our values and be as passionate about solving hard problems as we are.

So what really matters most when it comes to building a company that revolves around technology? Breadth or depth of experience? Volume of published work? Contributions to notable open source projects?

Having had to put some of this in writing recently, I thought I would share it more widely – here are what we at MarkedUp consider to be the three most important values for a developer-centric company:

1. Recognize that software development is an inherently social, team-driven experience – everyone on the team should get into a rhythm of regularly communicating and working together on tough issues, whether it’s done remotely / asynchronously / in-person – whatever.

No one codes off in a corner by themselves at MarkedUp; good programmers do their best work when they’re working with effective teams.

We do our best to make sure our developers have suitable tools and processes for managing their projects and work in concert with their teammates.

2. The ability to communicate concisely is a developer’s most important skill, even more than ability to code – everyone on the team should be able to articulate new ideas, improvements, and issues. If you can’t concisely explain a problem or a new idea, how else are you supposed to win the support of your teammates?

Developers at MarkedUp are encouraged to blog about writing software, give talks at conferences and user groups, and contribute to open source projects – because these are all forcing functions that improve a developer’s most important tool: the ability to concisely and understandably communicate technical content.

3. Continuously learn and improve – a developer’s job is to model the complexity of the real world, and to do that well you need to learn more about the world itself and improve the tools you use to model it.

MarkedUp fields a wide range of technical challenges we have to solve everyday, so we invest a lot into helping our team members improve their skills, learn new technologies, and play with new tools.

We even have a little perk to make sure that every employee at MarkedUp gets a Kindle allowance so they can snap up some new books each month and teach themselves something new. Or read a Twilight novel if they’re into that.

4. Pragmatic programmers only – at a company as early stage as MarkedUp, we have to optimize for flexibility and speed of iteration.

Everything must be designed in a way that it can be changed quickly if needed so we can frequently deliver new versions of our products. Performance, “scalable” design, and all of that other /r/Programming stuff only becomes a concern once it becomes a real problem rather than a theoretical problem.

This is how developers at MarkedUp are expected to approach problems: pragmatically. There is no room for design / platform / language dogma in our shop.


And so, off we go – we’ll probably refine this list over time ;)

MarkedUp is currently looking to hire two .NET developers to join our team – if you have any interest in joining an early stage company and make a difference in our product and your career, send us an email with the subject line “.NET developer” at


Comments are closed.