Overview

Founded in 2010, IP Street has built the world’s preeminent Intellectual Property(IP) analytics and visualization engine, in conjunction with a nationally recognized IP law firm. Our SaaS product helps corporations and financial analysts quickly and efficiently analyze IP information.  We make IP data easy to get, use, and understand!

As with any organization, we’ve continued to evaluate new ways to provide value to our clients. We’re evolving into a “SaaS+” model, which pairs our service with expert consultation to assist our clients in assessment and evaluation.  Our focus remains on the financial and technology markets.

Our technology stack is almost all open-source, with some nifty esoteric search technologies. Most of your work will be in Python and Django, in a Mac-based development environment, deploying to Linux. Other technologies include Postgres, Redis, and Solr. Our client-side code relies on Highcharts and Backbone.

This is a “small b” big data firm. But since we’re a scrappy start-up, we don’t have a big firm’s resources. We compensate by hiring senior people who are self-directed, appreciate real-world development trade-offs, and have a can-do attitude. It’s OK to not know something if you’re eager and willing to learn it. We know that bad code always haunts, so if you enjoy writing good code using a language’s standards and idioms, you’ve come to the right place!

This position is in a small engineering team. Its focus is on server-side work, which includes poking fingers into PostgreSQL, Solr, and other technologies. So, it’s not just coding. We do feature design, development, testing, DevOps, some customer support, and work closely with product management. Did I say that we wear multiple hats every day?

On to the details…

Responsibilities

  • Collaborate with others in product direction, priorities, and feature design
  • Design, implement, and test new product features and bugfixes
  • Make the user experience of our products as powerful, simple, and manifest as possible
  • Do what’s needed to move the company forward!

Qualifications

  • Significant server-side development experience. We’re not hung up on a number, because one year for you could equal five years for someone else. We’re looking for the confidence and awareness that comes from working with server-side web code. Here are some keywords: Subtasks, sentinels and software locks, software farms, scaling, and schema migration.  If you’re a smart person who enjoys working on software systems running on servers, you can check this box.
  • Significant experience developing in Python or a Python-based framework. We’re a Python and Django shop, and there’s no PHP, Ruby, or Perl within 2000’ of our codebase.  This must be serious development, and not, “I occasionally write 20-line scripts.”
  • If you’re very experienced in another language and are eager to learn Python, that could be OK. Can you convince us that you’re looking for a great opportunity to learn?
  • If you don’t know Django, that’s fine — it’s easy to learn.
  • Abilities that are nice to have: Significant interaction with PostgreSQL, Solr, or another type of db/search engine.
  • Some experience in JavaScript would be another plus. This won’t be your focus, though.
  • You’re enthusiastic about modern software development, distributed version control, coding, documentation, testing, and teamwork.
  • You have excellent judgement in attacking complex tasks, and in balancing “good enough, now” vs. “much better, later”
  • You’re self-sufficient, and confident in setting standards
  • Good communication skills

To apply

Salary depends upon experience. Please send your resume to johnd@ipstreet.com.


I’m in work on a Saturday, doing some database munging. We have a large update that requires a bunch of rows to be dropped, and a schema change.

I wish we had a DBA on staff for times like this. Or maybe a kick-ass local consultant whom we could bring in from time to time.

The row drops are taking forever. We don’t use triggers, but we of course have FKs and indexes. I’ll bet a savvy DBA would know some tricks to make the drops go faster. Drop indexes first? Don’t use a transaction? Inhibit table scanning? Something something something.

I know about good db behavior in our application, and measurement techniques, and know enough to know what I don’t know (that’s always most important), and a few performance tricks esp. when using Django. But table munging tricks I’m not so hot on. It’s not want for lack of desire; there are only so many hours in the day.

 

Follow

Get every new post delivered to your Inbox.

Join 9,513 other followers