- Location
- Brno
- Workplace
- Hybrid
- Type
- Internship
- Department
- Engineering
- Seniority
- Senior
- Source
- Lever
Description
The Role
We’re looking for a Senior .NET Engineer to be the first engineer on our new Internal Apps team, acting as the technical force multiplier behind the teams that keep our platform running.
Our Data and Support teams keep CMG’s reference data accurate and keep live deals running smoothly. They know exactly what they need but often lack the tools to do it efficiently. You’ll change that. Working directly with these internal power users, you’ll turn their ideas into well-built, well-supported tooling: admin interfaces, APIs, internal MCP servers that connect to AI agents, and agent workflows that automate the repetitive parts of their day.
As the first engineer on the team, you’ll help shape how it operates, from how requests come in to how tools are built, shipped, and supported. This role suits someone who is comfortable across the stack and does their best work with a lot of autonomy. You’ll navigate the organization, make decisions on your own, and know when something needs to go up the chain and what context to bring with it.
Our Data team is based in the US, so you’ll need regular working-hours that overlap with US time zones and the flexibility to shift your schedule when the work calls for it.
Our Engineering Team
The CMG engineering team consists of domain experts who work collaboratively within a culture of cross-domain knowledge sharing. We value engineers who are passionate about modern technologies and best practices.
Our engineers are encouraged to challenge the status quo and are constantly seeking improvement and efficiency in our code-base and platform. CMG engineers are empowered to explore solutions using leading edge technologies such as AI and bring recommendations to the table. We are in a period of making impactful engineering decisions.
As part of our process, we believe in taking the time for research and prototyping - this is critical in making the right decisions. Given the experience of our team, we have naturally adopted best practices from local development, through code review and into production rollouts. Besides the standard pull requests, test automation, code coverage tracking, containerization, and one-click deployments, we are constantly reviewing these foundational components to develop new best practices.