Ericsson
Master Thesis: Beyond Git: Source Control Architecture for Agentic Software Development
Be an Early Applicant
Investigate how Git-based source control and CI perform with hundreds of concurrent AI coding agents. Build simulations of up to approximately 500 agents, measure scalability, merge conflicts, CI impact, resource consumption, and semantic integration failures, and compare alternatives such as trunk-based development, merge queues, fine-grained changes, stacked changes, and speculative merging. Define benchmarking metrics and recommend improvements for agentic software development.
Join our Team
About this opportunity
Investigate how conventional Git-based source control behaves when hundreds of autonomous AI coding agents work concurrently on a shared codebase, and compare it with alternative architectures for agent-scale development. Build an experimental environment simulating up to approximately 500 concurrent agents and evaluate scalability, merge behavior, CI impact, resource consumption and semantic integration failures.
What you will do
AI coding agents are quickly moving from assisting individual developers to working autonomously and in parallel on the same codebase. Git and the CI pipelines built around it were designed for a small number of human contributors, not hundreds of agents committing, branching and merging at machine speed. This Master Thesis investigates where that model breaks down, and which alternative architectures handle agent-scale development better.
You are encouraged to research similar solutions at other large scale software companies. You will have freedom to define areas of exploration within the project. These could include, but are not limited to:
• Building an experimental environment that simulates up to approximately 500 concurrent AI coding agents working on a shared codebase:
o Designing realistic agent workloads and task distributions.
o Defining a reproducible setup for running and scaling the simulations.
o Selecting representative codebases of different sizes and levels of modularity.• Characterizing how conventional Git-based source control behaves under agent-scale load:
o Scalability, including repository growth, throughput and contention on shared branches.
o Merge behavior, including conflict rates, rebase and retry loops, and queue delays.
o Impact on CI, including build and test load, queueing and wasted compute.
o Resource consumption, including compute, memory, storage and network usage.• Investigating semantic integration failures, where changes merge cleanly but break behavior, and how often they occur as the number of agents grows.• Identifying and comparing alternative architectures for agent-scale development, such as:
o Trunk-based or merge-queue approaches.
o Fine-grained or file/symbol-level change models.
o Stacked changes, speculative merging or similar approaches.• Defining metrics and a benchmarking methodology to compare the architectures fairly.• Proposing recommendations for how source control and CI should evolve to support agentic software development.
The skills you bring
If you have most of the below, don't hesitate to apply.
• Knowledge in Computer Science, Software Engineering, or a related field.• Solid understanding of version control (especially Git) and continuous integration.• Experience in at least one programming language (python is a plus)• Solid understand of Linux environments and bash• Interest in distributed systems, performance analysis and experimental evaluation.• Eagerness to learn and explore new concepts.• Experience with LLM-based coding agents or agent frameworks• Experience with containerization and orchestration (e.g., Docker, Kubernetes).
About this opportunity
Investigate how conventional Git-based source control behaves when hundreds of autonomous AI coding agents work concurrently on a shared codebase, and compare it with alternative architectures for agent-scale development. Build an experimental environment simulating up to approximately 500 concurrent agents and evaluate scalability, merge behavior, CI impact, resource consumption and semantic integration failures.
What you will do
AI coding agents are quickly moving from assisting individual developers to working autonomously and in parallel on the same codebase. Git and the CI pipelines built around it were designed for a small number of human contributors, not hundreds of agents committing, branching and merging at machine speed. This Master Thesis investigates where that model breaks down, and which alternative architectures handle agent-scale development better.
You are encouraged to research similar solutions at other large scale software companies. You will have freedom to define areas of exploration within the project. These could include, but are not limited to:
• Building an experimental environment that simulates up to approximately 500 concurrent AI coding agents working on a shared codebase:
o Designing realistic agent workloads and task distributions.
o Defining a reproducible setup for running and scaling the simulations.
o Selecting representative codebases of different sizes and levels of modularity.• Characterizing how conventional Git-based source control behaves under agent-scale load:
o Scalability, including repository growth, throughput and contention on shared branches.
o Merge behavior, including conflict rates, rebase and retry loops, and queue delays.
o Impact on CI, including build and test load, queueing and wasted compute.
o Resource consumption, including compute, memory, storage and network usage.• Investigating semantic integration failures, where changes merge cleanly but break behavior, and how often they occur as the number of agents grows.• Identifying and comparing alternative architectures for agent-scale development, such as:
o Trunk-based or merge-queue approaches.
o Fine-grained or file/symbol-level change models.
o Stacked changes, speculative merging or similar approaches.• Defining metrics and a benchmarking methodology to compare the architectures fairly.• Proposing recommendations for how source control and CI should evolve to support agentic software development.
The skills you bring
If you have most of the below, don't hesitate to apply.
• Knowledge in Computer Science, Software Engineering, or a related field.• Solid understanding of version control (especially Git) and continuous integration.• Experience in at least one programming language (python is a plus)• Solid understand of Linux environments and bash• Interest in distributed systems, performance analysis and experimental evaluation.• Eagerness to learn and explore new concepts.• Experience with LLM-based coding agents or agent frameworks• Experience with containerization and orchestration (e.g., Docker, Kubernetes).
Ericsson Santa Clara, California, USA Office
Ericsson Santa Clara D-15 Innovation Center Office



Heart of Silicon Valley with leading tech companies nearby. Close to cafes, gyms and major highways, plus short commutes to San Jose, Mountain View and Palo Alto.
Similar Jobs at Ericsson
Cloud • Information Technology • Internet of Things • Machine Learning • Software • Cybersecurity • Infrastructure as a Service (IaaS)
Lead SoC IP architecture and roadmap for ASIC IP blocks, driving requirement breakdown, systemization, and technical direction. Support design, verification, and validation, improve design methodologies, and produce high-quality technical documentation while collaborating with cross-functional teams.
Top Skills:
AgileAmbaArmArm CoresightAsicDigital Asic DesignDoorsI3CJamaQspiSocSpiUvm
Cloud • Information Technology • Internet of Things • Machine Learning • Software • Cybersecurity • Infrastructure as a Service (IaaS)
Conduct a master’s thesis on early prediction and optimization of power, performance, and area in digital designs. Analyze RTL structures, simulation activity, synthesis configurations, and implementation data to identify PPA correlations and optimization opportunities. Develop and validate a reusable methodology or prototype flow, potentially using data-driven or AI-assisted techniques, while preserving functional correctness and timing and area requirements.
Top Skills:
Asic Design FlowsDigital SimulationFsdbLogic SynthesisPhysical ImplementationPythonRtlSystemverilogTclVcdVerilogVhdl
Cloud • Information Technology • Internet of Things • Machine Learning • Software • Cybersecurity • Infrastructure as a Service (IaaS)
Develop and systemize next-generation Radio Access Network products, focusing on baseband algorithms, radio resource management, MIMO, beamforming, and 5G/6G performance. Conduct technical studies, simulations, requirements analysis, and feature development. Collaborate with global engineering, product, and standards teams while contributing to system integration, standardization investigations, architectural input, and technical documentation.
Top Skills:
5G6GAIBaseband AlgorithmsBeamformingDigital Signal ProcessingMachine LearningMimoRadio Access NetworkRadio Resource ManagementSoftware Simulation
What you need to know about the San Francisco Tech Scene
San Francisco and the surrounding Bay Area attracts more startup funding than any other region in the world. Home to Stanford University and UC Berkeley, leading VC firms and several of the world’s most valuable companies, the Bay Area is the place to go for anyone looking to make it big in the tech industry. That said, San Francisco has a lot to offer beyond technology thanks to a thriving art and music scene, excellent food and a short drive to several of the country’s most beautiful recreational areas.
Key Facts About San Francisco Tech
- Number of Tech Workers: 365,500; 13.9% of overall workforce (2024 CompTIA survey)
- Major Tech Employers: Google, Apple, Salesforce, Meta
- Key Industries: Artificial intelligence, cloud computing, fintech, consumer technology, software
- Funding Landscape: $50.5 billion in venture capital funding in 2024 (Pitchbook)
- Notable Investors: Sequoia Capital, Andreessen Horowitz, Bessemer Venture Partners, Greylock Partners, Khosla Ventures, Kleiner Perkins
- Research Centers and Universities: Stanford University; University of California, Berkeley; University of San Francisco; Santa Clara University; Ames Research Center; Center for AI Safety; California Institute for Regenerative Medicine




