Full-Time
Legal Operations Specialist
JetBrains
1,001-5,000 employees
Develops IDEs and developer tools
No salary listed
Madrid, Spain
Hybrid
Flexible work is available from home or the office; the exact arrangement may vary by location.
 Legal (1) |
|---|
Get referred to JetBrains
See people who can refer or advise you
- A proven background in leading operational or process-improvement projects involving multiple stakeholders.
- Experience in legal operations, business operations, project management, consulting, product operations, process improvement, or a similar operational role.
- Experience gathering, analyzing, and documenting complex business requirements.
- A track record of turning business needs into structured implementation plans.
- Hands-on experience mapping out processes and driving continuous improvement.
- Experience managing vendor relationships or implementing new technology platforms.
- Familiarity working in cross-functional environments, particularly alongside legal, compliance, information technology, or risk teams.
- Map current workflows and build better, more efficient alternatives.
- Run legal operations projects from the discovery phase through implementation.
- Talk to stakeholders to understand their challenges and translate them into clear requirements and action plans.
- Manage legal technology vendors, handling onboarding, renewals, and ongoing evaluations.
- Track operational data to determine what is working, what is not, and where to focus next.
- Help the team adopt new tools and processes.
JetBrains builds a suite of developer tools, chiefly Integrated Development Environments (IDEs) for languages like Java, Python, JavaScript, .NET, and C/C++, plus related products for testing and project management. Their IDEs provide deep code understanding, smart editing, and refactoring to help programmers write and maintain software, and are sold via subscriptions (including an All Products Pack) with options for perpetual licenses and free Community Editions for some tools and non-commercial use. The company differentiates itself with a tightly integrated tool suite, language-agnostic support, strong refactoring capabilities, and a track record of popular products like IntelliJ IDEA and Kotlin, along with newer AI features and lightweight Fleet editor. JetBrains aims to help developers work more efficiently across multiple languages, ecosystems, and teams.
Company Size
1,001-5,000
Company Stage
N/A
Total Funding
N/A
Headquarters
Amsterdam, Netherlands
Founded
2000
Get referred to JetBrains
See people who can refer or advise you
Simplify's Take
What believers are saying
- TeamCity 2026.2 shipped September 2, 2026 with pipelines GA and BYOK AI.
- September 9, 2026 Defender analysis shows JetBrains still wins performance trust with Microsoft collaboration.
- September 2026 Saudi partnership with eSense expands enterprise distribution across Vision 2030 buyers.
What critics are saying
- CVE-2026-63077 enabled August 2026 Cadence intrusion; TeamCity still exposes supply-chain attack surface.
- July 2026 IntelliJ remote-session flaws and August YouTrack backup bug damaged trust.
- If another hosted-service breach leaks customer secrets, enterprise buyers will shift to Microsoft.
What makes JetBrains unique
- IntelliJ IDEA remains strongest on deep code understanding for Java and Kotlin teams.
- JetBrains controls the full stack: IDEs, Kotlin, TeamCity, YouTrack, and AI workflows.
- Its LSP preview spreads IntelliJ intelligence into VS Code and Cursor ecosystems.
Help us improve and share your feedback! Did you find this helpful?
Benefits
Flexible Work Hours
Remote Work Options
Conference Attendance Budget
Professional Development Budget
Growth & Insights and Company News
6 month growth
↑ 0%1 year growth
↑ 0%2 year growth
↑ 0%Why Rider and ReSharper were slow to Start, and how Microsoft helped fix the problem. September 9, 2026 When JetBrains launched ReSharper's out-of-process (OOP) architecture, users reported slower startup times for IDEs using ReSharper on Windows. After profiling, the cause surprised JetBrains: Microsoft Defender was scanning its process for longer than JetBrains expected. This post is about what JetBrains found, what JetBrains learned working with Microsoft, and a tool JetBrains built that allows others to run the same investigation. An unexpected factor in startup performance. Performance of its tools has consistently been the number one subject of feedback JetBrains has received from its users over the years. Its telemetry and user surveys confirmed what many of you have been telling JetBrains: Despite ReSharper's powerful features, the impact on Visual Studio's responsiveness was affecting your daily workflow. This led JetBrains down the path of developing its new out-of-process (OOP) architecture. JetBrains originally launched OOP mode for the public last year. (Now, thanks to these investigations, as of 2026.2.1 it is enabled by default.) In general, its telemetry indicated improved performance. However, at some point, JetBrains noticed something unexpected - customers started reporting slower startup times. After a few profiling iterations, the collected data pointed to an unexpected source of latency: Microsoft Defender. It turned out that processes in write-protected paths receive wider trust rules. Microsoft Defender barely touches those processes during startup - scanning takes a couple of seconds, even when ReSharper loads their DLLs from the user installation directory. But the moment ReSharper started running as a separate process, Defender scanned it in full, adding tens of seconds to first launch (see the chart below). This triggered its curiosity and sent JetBrains down a rabbit hole. JetBrains started analyzing Microsoft Defender ETW (Event Tracing for Windows) logs across dozens of developer tools, and the findings were striking: Some tools get scanned for 30+ seconds at startup while others finish in under a second, as JetBrains had observed above. JetBrains obviously wanted to learn the reasons behind that and find ways to speed up startup for JetBrains tools. An ambitious project, but JetBrains were up for the challenge! The first thing JetBrains needed was to set up a repeatable measurement process. That way JetBrains could share it with other teams in JetBrains, and with its colleagues from Microsoft to have a productive conversation. JetBrains is grateful for all Microsoft's explanations, openness, and willingness to help JetBrains with this investigation. Measuring the impact. JetBrains tracked the activity of Microsoft Defender in two ways: Microsoft Defender ETW logs (as mentioned above) and direct CPU time measurements. JetBrains found the two methods to be roughly equivalent for its scenario. If you're interested in the distinction, see its GitHub readme for more info. Microsoft Defender, like many other Windows components, uses ETW. It emits events under the Microsoft-Antimalware-Engine provider. Microsoft provides a PowerShell module for Defender-related performance investigations that uses this provider. It has two cmdlets: New-MpPerformanceRecording to collect a trace, and Get-MpPerformanceReport to analyze it. In its scenarios, most slowdowns came from Microsoft Defender's scan events. The Microsoft-Antimalware-Engine/StreamScanRequestTask ETW events report each scan's Start and End time, representing how long Defender spent scanning that stream in real-world elapsed time. The data JetBrains gathered showed JetBrains clearly how Defender was impacting its tool's startup wall time. Methodology. Performance measurements were run on a Dell Pro Max 16 (MA16250) laptop with an Intel Core Ultra 9 285H (16 cores) processor and 64 GB of DDR5-class memory. The host ran Windows 11 Pro. The workload was executed inside a Hyper-V VM configured with 8 vCPUs and 8 GB of static RAM. Each tool was measured 10 times. As per standard best practices when measuring performance, JetBrains rebooted its VM before each measurement to simulate a cold start. This reduced observed file and memory caching effects on its results. The charts below show the mean scan time with standard deviation error bars. Results of the experiment. As you can see, JetBrains measured a variety of development tools, and there were clear differences in the amount of time Defender took to scan them: * JetBrains IDEs (JetBrains IDEs, and some other editor-class tools) took roughly 10-40 seconds to scan at cold start, while Microsoft IDEs and various other editors had negligible scan times in comparison (all under 1 second). * CLI-based tools (the command-line agents) took under ~2 seconds to scan, likely because they're small, simple binaries with few DLLs. Collaboration with Microsoft and its solution. Even though JetBrains had built a tool to measure Microsoft Defender's impact, JetBrains still failed to fully understand Defender's scanning principles. JetBrains also consulted their documentation to no avail. So JetBrains reached out to its colleagues at Microsoft directly! They helped JetBrains understand the parameters which cause Microsoft Defender to perform more work. A core principle was that files in write-protected folders would be optimized for scanning. At this point, JetBrains reviewed all the ways JetBrains install and start its tools to find a way to reduce the scanning times. One observation was that JetBrains Rider is subject to even more intensive scanning than IntelliJ IDEA and ReSharper combined. The reason for this was also not clear to JetBrains, so JetBrains asked the Microsoft team for help again. They were able to make optimizations on their end for this specific case and adjustments to Defender released in version 1.449.454.0. Now ReSharper OOP and JetBrains Rider get the scanning performance boost when installed into a write-protected directory: JetBrains Toolbox installs software in the %LOCALAPPDATA%\Programs directory. Since this directory does not require elevation for writing, Toolbox can update the software seamlessly, but as you can see in the chart above, it does not receive the write-protected performance boost. As JetBrains has reported previously, Rider itself excludes some directories from Microsoft Defender during the installation process (more about this here). It uses the Add-MpPreference PowerShell cmdlet to help you automatically configure a Microsoft Defender exclusion. JetBrains is still evaluating the best way to support the JetBrains Toolbox installation of Rider and Microsoft Defender exclusions. You can follow its progress in its TBX-2851 issue. Note: The ability to add exclusions locally can be disabled/blocked by administrators in managed environments. Measuring for your own tool. If you're experiencing the slow startup of your own tool, it definitely makes sense to analyze whether Microsoft Defender is affecting it. To help with your investigation, JetBrains is releasing the tool JetBrains built for its own - the small and easy-to-use Defender Performance Tool. The source code and release builds are on GitHub. A few things you can do with it: * Watch your application's scan activity in real time as it starts, loads plugins, or compiles something. * Open snapshots recorded offline with New-MpPerformanceRecording, so you can investigate traces from another machine (for example, one collected by a customer). * Export a CSV file when multiple snapshots are loaded, for further analysis. JetBrains hope that helps you with similar investigations. Let JetBrains know of any interesting findings! Conclusion. As you can see, Microsoft Defender can have a large impact on tooling performance. JetBrains learned a lot working with Microsoft in this area, and JetBrains hope its findings help developers and vendors understand how best to maintain the security of their Windows systems by observing and tuning Microsoft Defender's behavior. Summary of best practices for working with Microsoft Defender: * Keep your Microsoft Defender definitions up-to-date. * Use the Microsoft PowerShell module for Defender-related performance investigations. * Try its new tool to help analyze Microsoft Defender logs, available on GitHub. * Optimize Microsoft Defender scanning by installing software to write-protected directories. * Use the Add-MpPreference PowerShell cmdlet to help you automatically configure a Microsoft Defender exclusion, if required. * Set up a DevDrive on your Windows machine for storing your repositories and package caches. Hopefully, you've noticed these improvements to ReSharper and Rider in your workflow too! ReSharper 2026.2.1 now ships with OOP enabled by default. Try it out today!
JetBrains Cadence breach exposes AWS credentials via TeamCity exploit. Attackers breached JetBrains' Cadence infrastructure by exploiting an unpatched TeamCity vulnerability. The company urges all users to rotate credentials immediately. * Threat actors exploited a critical TeamCity flaw to access JetBrains' internal systems. * The breach targeted Cadence, exposing AWS credentials and execution secrets. * JetBrains advises immediate credential revocation and rotation for all Cadence users. * Unpatched instances of TeamCity were the initial attack vector. * Organizations using Cadence must audit and secure their cloud configurations. JetBrains has confirmed a security breach affecting its Cadence workflow platform, stemming from attackers exploiting a known critical vulnerability in its TeamCity build system. The incident resulted in unauthorized access to internal systems and the exposure of sensitive AWS credentials. In response, JetBrains is advising all Cadence users to immediately revoke and rotate any credentials or secrets that may have been used in Cadence executions. This action is essential to mitigate potential abuse of exposed cloud resources and maintain secure operations. Vulnerability Exploitation. * Attackers leveraged a recently disclosed critical vulnerability in TeamCity to gain initial access. * The unpatched nature of the affected TeamCity instance enabled deeper infiltration into JetBrains' environment. * Exploitation led directly to the compromise of Cadence-related infrastructure and associated AWS credentials. Impact and response. * Sensitive execution secrets and cloud credentials were accessed during the breach. * JetBrains issued an urgent advisory recommending full credential rotation for Cadence users. * Organizations are advised to audit their AWS environments for signs of unauthorized activity. Sources.
Attackers breached jetbrains Cadence via unpatched TeamCity, extracting AWS credentials. Incident overview. JetBrains has confirmed that threat actors successfully breached their Cadence internal environment by exploiting a critical, unpatched vulnerability within the TeamCity CI/CD server platform. The attackers utilized this entry point to gain unauthorized access to internal systems, specifically focusing on the extraction of sensitive AWS credentials. The breach underscores the risks associated with vulnerable CI/CD infrastructure, as these tools serve as central hubs for code and production environments. JetBrains is currently investigating the full scope of the compromise, while the immediate impact involves potential unauthorized access to cloud-based resources via the exfiltrated keys. The incident remains active as the company works to contain the threat and verify if other assets were targeted. Strategic implications. This incident highlights the escalating risk profile of CI/CD pipeline tools, which are increasingly favored by state-sponsored actors and cybercriminals as high-value supply chain targets. For organizations, this breach signifies that vulnerabilities in developer tooling can grant attackers a foothold in critical production environments, potentially leading to widespread software supply chain compromise. The financial and reputational implications of such incidents are severe, often triggering complex incident response cycles and intensive regulatory oversight. As threat actors continue to target cloud credentials stored in build servers, organizations must reassess the security of their automated workflows and adopt a zero-trust approach toward CI/CD infrastructure to mitigate long-term operational and compliance risks. Critical insights. Security teams must treat unpatched TeamCity instances as high-severity vulnerabilities requiring immediate remediation and patch application. A primary mitigation strategy is to rotate all AWS credentials and secrets previously accessible to the affected TeamCity environment, as these must be considered compromised. Defenders should conduct thorough audits of their build pipeline logs to identify unusual access patterns or unauthorized calls to cloud APIs. Future security strategies should focus on enforcing strict identity and access management for build servers, including the use of ephemeral credentials and least-privilege principles to limit the impact of a potential breach. Continuous monitoring for signs of unauthorized lateral movement from the CI/CD segment into broader cloud infrastructure is essential for timely detection and containment.
JetBrains and eSense partner to strengthen Saudi Arabia's enterprise software-development. JetBrains, the global software company behind some of the world's most widely used professional developer tools, today announced a partnership with eSense to help government and enterprise organisations in Saudi Arabia strengthen their software-development capabilities, modernize engineering practices and adopt AI across the software-development lifecycle with greater visibility and control. The partnership comes as Saudi Arabia continues to expand its technology sector under Vision 2030. According to the Ministry of Communications and Information Technology, the Kingdom's ICT market has grown from SAR 105 billion prior to Vision 2030 to SAR 190 billion in 2025, while the number of jobs in the sector has increased from approximately 250,000 in 2018 to more than 406,000 in 2025. AI adoption is also accelerating, with data from the General Authority for Statistics showing that 33.1% of establishments used AI technologies in 2025, rising to 61.1% among establishments in the information and communications sector. This growth is increasing the need for professional engineering tools and practices that can support the development, quality and governance of software at scale. Founded in 2000, JetBrains is the global technology company behind widely used developer tools including IntelliJ IDEA, PyCharm and Rider, as well as Kotlin, the open-source programming language. Its products help developers and organisations build, understand, test and deliver software more effectively, supporting the full software development lifecycle from coding and collaboration to continuous integration, code quality and deployment. As a local JetBrains channel partner, eSense is a Saudi company, headquartered in Riyadh and serving the region, which brings more than two decades of experience delivering technology solutions to government and enterprise organisations. The Saudi-based company works with more than 200 government and enterprise customers, with capabilities spanning software engineering, Agile and DevOps delivery, cloud infrastructure, security, data and AI. Through the partnership, eSense will help Saudi organisations select and adopt the JetBrains tools that best fit their engineering environments, while providing local expertise across licensing, implementation planning and team enablement. Together, the companies will support customers from assessing existing environments and defining technical requirements to improving development workflows, code quality, DevOps and continuous delivery. They will also help organisations introduce AI in ways that maintain engineering oversight. JetBrains and eSense are already applying this approach to a strategic technology initiative supporting Saudi Arabia's food-security priorities. The engagement combines JetBrains tools with eSense's professional services and software engineering expertise to improve the maintainability, quality and reliability of software supporting complex operational requirements. The company is already working with leading Saudi organisations, including SDAIA, stc Group, D360 Bank, Tamara, Tabby, and Cyberani by aramco digital and is looking to grow its presence in Saudi Arabia significantly as local software development scales up. "Saudi Arabia has built the region's largest technology market and one of its strongest digital talent bases. The next stage is about giving Saudi organisations the engineering capability to build, understand and maintain increasingly complex software for themselves," said Nadia Rinsky, Head of Business Development for the MENA region at JetBrains. "AI can help teams produce more code, but producing code is no longer the hardest part. The real challenge is ensuring developers can understand what enters the codebase, verify it and remain accountable for the result." "This partnership brings together JetBrains' deep expertise in code intelligence and professional software development with eSense's knowledge of Saudi organizations, technology environments and delivery requirements," she added. "We want to help customers strengthen the entire software development lifecycle - from the development environment and code quality to DevOps, continuous delivery and enterprise AI governance. This is about building lasting in-house engineering capability, not simply deploying another set of tools." "Saudi Arabia's digital ambitions are raising the standard expected of the software behind government services and enterprise operations," said Wisam Banat, Chief Executive Officer of eSense. "These systems must be secure, maintainable and capable of evolving as operational needs change. That requires more than access to technology: it requires strong engineering practices, local implementation expertise and teams that can take long-term ownership of what they build." "JetBrains has spent more than 25 years building tools around the real work of professional software teams. Combined with eSense's local engineering, DevOps and professional-services capabilities, that gives customers a practical route to improving their development environments, code quality and delivery processes. It also helps them adopt AI without losing the human understanding and accountability on which dependable software ultimately rests." Through JetBrains AI Enterprise, organizations can make AI assistance available within the development environments their teams already use to write, understand, test and maintain code. Administrators can manage access through user profiles, determine which AI providers are available to different groups, control the number of enabled users, and review adoption and impact metrics. Developers remain able to inspect AI-generated suggestions and changes before deciding whether they should enter the codebase. JetBrains AI Enterprise supports the JetBrains AI service and connections to OpenAI Platform, Azure OpenAI, Google Vertex AI and Amazon Bedrock. Different supported providers can be made available to different user profiles, allowing organisations to configure AI-assisted development according to their technology architecture, security policies and cost requirements. Saudi organizations can meet JetBrains and eSense at their joint LEAP 2026 booth in Hall 2, stand N10, or contact eSense to discuss JetBrains products and enterprise adoption requirements. LEAP 2026 runs in Riyadh until 3 September. Middle East News 247 produces the latest news for the Middle East region, with a key focus on the GCC nations: UAE, Saudi Arabia, Qatar, Bahrain, Kuwait, and Oman. Contact News Desk: [email protected] Follow Me:
TeamCity 2026.2: pipelines general availability, BYOK for AI Assistant, and more. September 2, 2026 This major update for TeamCity On-Premises introduces a number of pipeline improvements that are now moving out of EAP and joining build configurations as official, stable options for designing CI/CD workflows. JetBrains is also shipping a number of AI-related features, including an MCP toolset extension and the ability to choose any major cloud AI provider or your local LLM to handle all interactions with AI Assistant in TeamCity. As always, you can see the complete list in its documentation. JetBrains also roll out two bug-fix updates for its previous major TeamCity On-Premises versions: 2025.11.8 and 2026.1.4. TeamCity pipelines. General availability. TeamCity 2025.07 introduced pipelines as an Early Access Program (EAP) feature - instantly available on TeamCity Cloud and on request for TeamCity On-Premises. Since then, JetBrains has been steadily closing the gap with classic build configurations, adding build feature support, .NET steps, the ability to link pipelines into build chains, and more. With this release, pipelines move out of EAP and are now generally available on both TeamCity Cloud and On-Premises, for projects of any size and complexity. However, its development of pipelines does not stop here - see its roadmap for what's next. Improved branch handling. Pipelines are now much better equipped to handle branches when your YAML file is stored in a Git repository. You can now select repository branches while in Edit mode, and design unique workflows for each branch. In addition, pipelines are now better at handling protected branches - the most common technique for safeguarding your main branches from unverified commits. Starting with version 2026.2, pipelines show clear warnings that edits made in the UI cannot be pushed to protected branches directly, and suggest saving them to other branches instead. Run through failures. When setting up job dependencies, you can now enable Run job even if upstream fails to ensure a pipeline runs until the very end, even when there are errors. The pipeline run will still be marked as failed overall, but this feature lets you ensure that specific jobs (for example, cleanup or notification steps) always run. Promote pipeline runs. Promote - the button that triggers the downstream part of a build chain from an older, already finished build - now works for pipelines, not just build configurations. For example, you can promote a successful Build Docker image run into the Upload to DockerHub configuration or pipeline to re-deploy that artifact without rebuilding it. Debug jobs. You can now debug individual jobs without leaving Edit mode and triggering the entire pipeline. This small addition allows you to design complex workflows faster because you can fix problems as they arise instead of having to work your way through the failure log at the very end. Unbound pipelines. You can now create pipelines without VCS roots attached. Previously, this option was only available for build configurations. Choose the Without repository option when creating a pipeline to create a custom workflow that does not check out any remote sources. New MCP tools. Your AI Agents can now use three more tools designed to work with TeamCity pipelines: teamcity_pipeline_get, teamcity_pipeline_post, and teamcity_pipeline_delete. To avoid any accidents, the post and delete tools are only available in Brave mode, which has to be enabled manually. TeamCity AI. AI continues to reshape software development. The TeamCity team is taking a practical approach: using AI to solve real CI/CD problems and remove friction from everyday tasks - all while keeping you in control of which AI capabilities you use and how you use them. AI Assistant. AI Assistant now supports Bring Your Own Key (BYOK), enabling you to plug in any supported LLM. Go to Admin | AI Assistant and enter your developer AI API key. Then you'll be able to use Anthropic, OpenAI, Google Gemini, or any other supported model to inspect the builds and debug your CI workflows. MCP enhancements. In version 2026.1, JetBrains has implemented an MCP endpoint that allows AI agents to use a TeamCity server as a source of tools. In this release, JetBrains is adding three more tools that let you use your preferred AI solutions to manage pipelines in addition to classic build configurations and projects. Moreover, JetBrains has implemented the OAuth/PKCE authorization flow, which means you no longer need to manually issue a personal access token and pass it to your AI environment configuration. Rerun failed chain builds. The Dependencies tab of build configuration settings now includes a Retry Settings group. Enable the Use custom retry settings option and enter a positive number of retry attempts in the corresponding box when you want to delay a downstream build and automatically retry a failing dependency in place - no need to rerun the entire chain. IDE integrations. JetBrains has updated its IDEA plugin so that it now comes with its CLI tool and offers seamless MCP server registration. This means you can set up integration with Junie or third-party AI agents with little to no manual setup. The plugin core functionality has also been improved: You can now view the results of TeamCity tests from the IDE and launch remote runs with local changes that have not yet been committed. In addition, Kotlin Multiplatform developers working with IDEA and Android Studio can now install this plugin to claim an exclusive free-tier TeamCity Cloud subscription (currently capped at 30,000 build credits per month) where it's possible to run automatically generated pipelines that test and build your iOS applications. The plugin also simplifies TestFlight integration, making the process of deploying your iOS applications significantly easier. GitHub integration. The Pull Requests build feature can now match pull requests by their source branch instead of their branch reference. This lets TeamCity recognize separate pull requests in different repositories as related changes and build them together in the same build chain, even when GitHub assigns them different pull request numbers. DSL compilation mode. For projects that store Kotlin DSL versioned settings in remote repositories, you can now choose where TeamCity runs this code: on the server or build agents. Executing kDSL on build agents is less restricting and more secure, but both options come with certain trade-offs, so make sure to check its documentation for all recommendations and caveats.