Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
Creospan Inc. is seeking a senior technical leader on a data product team. This role sits at the seam of software engineering and data science, owning architecture, interfaces, and the sequencing of work.
You will build APIs, backend services, data stores, and data-processing systems, guiding engineers and coordinating with product management to deliver value across client projects. This is an individual contributor role with no direct reports.
Creospan is a growing tech collective of makers, shakers, and problem solvers, offering solutions today that will propel businesses into a better tomorrow. “Tomorrow’s ideas, built today!” In addition to being able to work alongside equally brilliant and motivated developers, our consultants appreciate the opportunity to learn and apply new skills and methodologies to different clients and industries.
******NO C2C/3RD PARTY, LOOKING FOR W2 CANDIDATES ONLY, must be able to work in the US without sponsorship now or in the future***
This is the senior technical role on a data product team, in a data organization that is becoming a software‑engineering organization and deliberately reinventing how engineering work is performed with AI.
You will be part of the team that builds APIs, backend services, shared libraries, operational data stores, and data‑processing systems.
This is an individual contributor role with no direct reports. Each data product team operates through a three‑way partnership: the product manager owns what gets built and in what order, the engineering manager owns the engineering practice and how engineers grow, and you own how it gets built, including the architecture, the interfaces, the sequencing of the work, and the call on whether a design is ready.
You will be measured by what the team ships, not solely by what you ship yourself. The best tech leads spend their time on decisions that are expensive to reverse and leave the rest to the engineers who will learn from making them.
The role sits at the seam between software engineering and data science and asks for real strength in both: you may not be building models yourself, but you need to be credible with the people who do, and able to reason about whether an offline metric will hold up online, what a latency budget means for an inference path, and when a model is the right tool and when a rule would do.