As the year wraps up, it’s time for reflection and a little dreaming about what could make next year even better for engineering teams. Imagine this: a wish list not for gadgets or gear, but for tools and practices that drive engineering excellence. Things like: ✅ A unified portal for service ownership ✅ Streamlined onboarding for new engineers ✅ Proactive reliability measures ✅ Metrics that actually matter In our latest blog, we’ve crafted the ultimate Developer's Holiday Wish List for the CTO. If you’re dreaming of a smarter, smoother, and more innovative engineering workflow in 2025, this one’s for you. 🎁 Read the full wish list: https://lnkd.in/gA__Wdvp
Cortex
Software Development
San Francisco, CA 9,610 followers
Cortex is the Internal Developer Portal eliminating “developer tax” with paved paths to production.
About us
Cortex is an internal developer portal built to accelerate the path to engineering excellence. Companies like Docker, TripAdvisor, and Confluent use Cortex to automatically catalog, continuously assess, and confidently deploy high quality software.
- Website
-
https://www.cortex.io/
External link for Cortex
- Industry
- Software Development
- Company size
- 51-200 employees
- Headquarters
- San Francisco, CA
- Type
- Privately Held
- Founded
- 2019
Products
![Click here to view Cortex]()
Cortex
DevOps Software
Cortex is the internal developer portal that cuts noise for developers with paved paths to production. Catalog, score, and drive action to improve software.
Locations
-
Primary
Get directions
San Francisco, CA 94105, US
Employees at Cortex
Updates
-
At Sportradar, driving engineering excellence isn't just a goal—it's a necessity. Scott Dunbar, SVP of Engineering Enablement at Sportradar, shares how Cortex streamlined their development process, eliminating two years of complexity from engineering workflows. “Cortex is helping us drive a culture of engineering excellence by bringing all the complexity in an engineer's life into one single consumable artifact, and really helping the engineer distill down all the metrics, requirements, scorecards, and measures that they need to think about in their daily work.” From automating workflows with tools like the Scaffolder and Service Catalog to empowering teams to bootstrap entire projects from scratch, Cortex is helping Sportradar optimize efficiency and innovation. See how Cortex is transforming engineering workflows at Sportradar: https://lnkd.in/gAtXfNfy
-
Cortex reposted this
Cofounder & CTO at Cortex | Building the internal developer portal powering productive engineering teams
Great post about developer productivity and a refreshing new take on it. "Attribution is hard to do, and requires careful causal modeling and reasoning about systems to understand how work ties into outcomes etc. It requires business context. It cant be solved by generic 'developer productivity' metrics.. ('developer efficiency' is not even the 10th most important problem to solve on this list.)" It's exciting to see the industry begin talking about business context and outcome driven analysis of engineering orgs and systems. I talked about this recently in a talk at AWS re:Invent https://lnkd.in/g7cJmN9t, not specifically around measuring productivity but focused on why platform engineering HAS to be aware of business context+outcomes, not isolated from it.
The myth that software development productivity is hard to measure because it is non-repetitive, creative, knowledge work is the kind of folk wisdom we have gotten away with as an industry for too long.. I recently saw an article from an ex-Amazon engineering leader arguing this. Do you think Sales isn't non-repetitive, creative, knowledge work? It's orders of magnitude harder than development if you measure on these dimensions. Or Marketing? In these areas, where people did not have the tools or techniques to figure out how and where to invest their dollars, the fact that it is creative, non-repetitive, knowledge work did not stop them in their tracks from figuring out how to do it. It's still not easy, its takes a lot of work to do, but the fact that it is creative work has nothing to do with whether this is possible to do. What it requires is the desire to solve the problem and it is in the interest of a lot of people to claim the problem is impossible or unnecessary to solve than to actually try and solve it. The underlying productivity problem we have to solve for product development and engineering is not all that dissimilar from marketing: attributing investments in product and engineering to economic outcomes. Its harder in our world because PD and operations are intertwined and concurrent. ..and outcomes are a complex, time shifted function of outputs. But it is not impossible. Attribution is hard to do, and requires careful causal modeling and reasoning about systems to understand how work ties into outcomes etc. It requires business context. It cant be solved by generic "developer productivity" metrics.. ("developer efficiency" is not even the 10th most important problem to solve on this list.) But I'll repeat.. Its not impossible.. The level of basic literacy among engineering managers on how to use data to reason and advocate about their systems of work and the outcomes they produce is really pretty awful, imo. You cant blame the current crop of leaders who came up in the ZIRP era, though. For most of their careers all they've had to do is figure out how to grow the headcount of people reporting to them. They have not developed the muscles for operating in a resource constrained environment. Or if, like me, they are from an earlier generation, the machinery to do this simply did not exist so they still stick with outdated beliefs about what is possible. So we seem to be stuck in a doom loop of self-delusional, self-congratulatory mediocrity that can only be ignored by inflating the next bubble.. I guess that's where AI comes in..
-
What if your platform wasn’t just functional but a developer favorite? In his The New Stack blog, Justin Reock shares 6 steps to shift from reactive fixes to proactive impact. ✨ Root out real pain points. ✨ Develop Systems Thinking. ✨ Drive developer love with a product mindset. Curious? See how: https://lnkd.in/gzpYmadk
6 Steps To Shift Platform Engineering From Reactive to Proactive
https://thenewstack.io
-
We’re ecstatic to welcome Marion Martorell to our Customer Experience Team! 🎉 "I’m so excited to join a company with a product that is uniquely enhancing visibility into productivity and efficiency. Additionally, I am most excited about joining this group full of talented and motivated individuals truly focused on customer success! I can’t wait to be part of growth and help shape Professional Services!" - Marion on "Why Cortex?" If you're interested in joining Cortex, check out our Careers page https://lnkd.in/gM2gFbdC #hiring #remotework #careers #opportunities #recruiting #business #development #team #sales #engineering
-
-
Meet Jonathan Nolen, Cortex’s VP of Engineering! 🚀 With 6 years at LaunchDarkly and a decade at Atlassian, Jonathan has helped shape tools that fundamentally changed how software teams build, ship, and operate. Now, he’s bringing that passion to Cortex to tackle complexity and drive Engineering Excellence. Why Cortex? It’s the toolkit engineering leaders have been waiting for. 👀 Hear from Jonathan about why he joined and what’s next: https://lnkd.in/g-dHJ-9G Welcome to the team, Jonathan! 💜
Why I Joined Cortex | Cortex
cortex.io
-
Missed IDPCON 2024 or want to rewatch your favorite sessions? You’re in luck! The talks—covering everything from building better Internal Developer Portals to achieving engineering excellence—are now live on YouTube. It was a day packed with learning, collaboration, and big ideas. And yes, plans for IDPCON 2025 are already underway.... 📹 Watch the 2024 sessions: https://lnkd.in/gbbMq2US ✨ Get updates on IDPCON 2025: https://idpcon.com/
The Past, Present and Future of Developer Productivity Theories and Metrics - IDPCON Keynote
https://www.youtube.com/
-
🎥 Platform engineers as product managers? In his lightning talk at AWS re:Invent, Cortex CTO and co-founder Ganesh Datta explains how platform engineering is evolving and why thinking like a product manager can elevate your engineering team’s performance. Ganesh breaks it down (not like that, don't worry): ✔️ Ownership and accountability start the conversation ✔️ Aligning engineering with business outcomes is key ✔️ Driving engineering excellence through actionable initiatives 📽️ Check out the rest of this lightning talk here: https://lnkd.in/gpqwiuT3 and see why platform engineering isn’t just about building tools—it’s about building success.
-
Only Cortex can take THIS (our drive to enable engineering excellence) and THIS (engineering challenges) and turn it into a portal built for world class engineering teams. The new Cortex website highlights how we help teams track ownership, eliminate orphaned services, and elevate accountability—enabling engineering leaders to focus on what they do best. Explore the new site and see what’s possible: Cortex.io.