Principal Software Engineer - Platform Engineering

About AlphaSense: The world’s most sophisticated companies rely on AlphaSense to remove uncertainty from decision-making. With market intelligence and search built on proven AI, AlphaSense delivers insights that matter from content you can trust. Our universe of public and private content includes equity research, company filings, event transcripts, expert calls, news, trade journals, and clients’ own research content. The acquisition of Tegus by AlphaSense in 2024 advances our shared mission to empower professionals to make smarter decisions through AI-driven market intelligence. Together, AlphaSense and Tegus will accelerate growth, innovation, and content expansion, with complementary product and content capabilities that enable users to unearth even more comprehensive insights from thousands of content sets. Our platform is trusted by over 6,000 enterprise customers, including a majority of the S&P 500. Founded in 2011, AlphaSense is headquartered in New York City with more than 2,000 employees across the globe and offices in the U. S. , U. K. , Finland, India, Singapore, Canada, and Ireland. Come join us! About The Role: AlphaSense runs a large-scale, Kubernetes-native platform built on a modern microservices architecture, serving the majority of the Fortune 500.

We're now moving it into a cell-based architecture, where each cell is an independent deployment of the platform, and the cell count is heading from dozens toward hundreds, including private and isolated clouds. Platform tooling only takes that so far. The rest of the problem is architectural and it sits in the services: how they're structured, how they're bounded, and what they assume about the environment they run in. This role owns that side of the work. You'll set the architectural direction for how our services scale horizontally across regions, cells and deployment models, and you'll build it rather than specify it. You'll own the environments configuration management framework to operate environments as a fleet, and the services and libraries to make it work. Where the answer is a re-architecture rather than a patch, you design it and you write it. Much of it lands in code other teams own, so influence matters as much as design. The scope is deliberately broad: hundreds of services, several languages, and the latitude to go after whichever scalability limit matters most. Our main languages are Java, Python, React and Rust. We use AI tooling heavily and expect the same from you, along with a view on how the rest of engineering should be using it. What You'll Do: - Drive the service-side changes cell architecture needs: re-architecture, shared library, etc.