Find a job 
Featured Companies 
Featured Universities 
For Companies At a Glance
- Tasks: Lead technical direction and mentor teams while staying hands-on with coding.
- Company: Join a dynamic team focused on building innovative tools for a merchant-first ecosystem.
- Benefits: Enjoy a growth mindset, minimal bureaucracy, and opportunities for skill development.
- Why this job: Make a real impact by solving complex problems in a fast-paced environment.
- Qualifications: 10+ years in software engineering, strong skills in .NET or Java, and mentoring experience required.
- Other info: Payments experience is a bonus but not essential; reach out for more details.
The predicted salary is between 48000 - 84000 £ per year.
Are you a senior engineer who wants to stay hands-on while shaping the technical direction of a growing team? Do you enjoy designing and delivering complex systems that have real impact? If so, read on.
We’re building the next generation of tools to support a fast-moving, merchant-first ecosystem. We value empowered teams, practical thinking, and outcome-driven engineering—and we’re looking for someone who shares these values.
What We Prioritise:
- Small teams, real outcomes – Clear goals, the right tools, minimal bureaucracy.
- Growth mindset – Encouraging innovation, skill development, and cross-team learning.
- Solving real problems – Focused on delivering value through practical, scalable solutions.
The Role:
As Principal Software Engineer II, you’ll lead technical direction across a range of platform capabilities (e.g., APIs, billing, settlement). You’ll be responsible for architectural decisions, mentoring teams, and contributing to key delivery efforts—staying 50% hands-on with the code.
Key Responsibilities:
- Define and evolve engineering practices and architecture across teams.
- Own and contribute to technical strategy, standards, and documentation.
- Identify improvement opportunities and lead cross-team initiatives.
- Provide technical leadership and mentorship to developers.
- Guide technology decisions, including build vs. buy assessments.
- Stay hands-on with critical coding tasks tied to strategic goals.
Requirements:
- ~10+ years’ experience in software engineering and architecture.
- ~ Strong skills in .NET, Java, or similar languages; SaaS/API experience preferred.
- ~ Hands-on knowledge of SQL, middleware, caching, system integration.
- ~ Track record of addressing performance/scalability issues.
- ~ Experience in mentoring and leading technical teams.
- ~ Excellent communication skills and stakeholder engagement.
- ~ Comfortable working in a fast-moving, evolving environment.
Payments experience is a bonus, but not essential.
Please reach out to Brendan McCrory with any further questions.
Tech Principal Software Engineer employer: Ocho
Contact Detail:
Ocho Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land Tech Principal Software Engineer
✨Tip Number 1
Familiarise yourself with the latest trends in software architecture and engineering practices. Being well-versed in current technologies like .NET, Java, and SaaS/API solutions will not only boost your confidence but also demonstrate your commitment to staying relevant in the field.
✨Tip Number 2
Showcase your hands-on experience by discussing specific projects where you led technical direction or made architectural decisions. Prepare examples that highlight your problem-solving skills and how you've delivered scalable solutions in previous roles.
✨Tip Number 3
Network with professionals in the industry, especially those who have experience in payments or similar ecosystems. Engaging with others can provide insights into the company culture and expectations, which can be invaluable during interviews.
✨Tip Number 4
Prepare to discuss your mentoring style and experiences. As a Principal Software Engineer, you'll be expected to lead and guide teams, so having clear examples of how you've successfully mentored others will set you apart from other candidates.
We think you need these skills to ace Tech Principal Software Engineer
Some tips for your application 🫡
Tailor Your CV: Make sure your CV highlights your 10+ years of experience in software engineering and architecture. Emphasise your skills in .NET, Java, and any relevant SaaS/API experience to align with the job requirements.
Craft a Strong Cover Letter: In your cover letter, express your passion for hands-on coding and leading technical teams. Mention specific examples of how you've defined engineering practices or contributed to architectural decisions in previous roles.
Showcase Problem-Solving Skills: Provide examples in your application that demonstrate your ability to solve real problems and deliver scalable solutions. Highlight any past experiences where you addressed performance or scalability issues.
Highlight Mentorship Experience: Since mentoring is a key responsibility, include details about your experience in guiding and developing other engineers. Share specific instances where your mentorship led to successful outcomes for your team.
How to prepare for a job interview at Ocho
✨Showcase Your Technical Expertise
As a Principal Software Engineer, you'll need to demonstrate your deep understanding of software engineering principles. Be prepared to discuss your experience with .NET, Java, and any relevant SaaS/API projects. Highlight specific examples where you've tackled performance or scalability issues.
✨Emphasise Leadership and Mentorship
This role requires you to lead and mentor teams. Share your experiences in guiding developers and fostering a collaborative environment. Discuss how you've contributed to the growth of your team members and the impact it had on project outcomes.
✨Prepare for Architectural Discussions
Expect questions about architectural decisions and technical strategy. Be ready to explain your thought process behind choosing certain technologies or frameworks. Discuss any build vs. buy assessments you've conducted and the rationale behind your choices.
✨Demonstrate a Growth Mindset
The company values innovation and continuous learning. Share examples of how you've encouraged skill development within your teams or adapted to new technologies. Show that you're not just focused on current practices but are also looking for ways to improve and evolve.
