Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert rolesBrowse expert rolesBrowse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert roles14156 openings
5609-5616 of 14156
Grip
Free to start · No card · 5 credits the moment you sign up
Grip is the AI-powered, end-to-end event platform built for engagement. The flexible system helps commercial event organizers like Ascential, Hyve, Emerald and Clarion Events boost revenue by establishing, maintaining and tracking relationships between participants over multiple events. This is possible because Grip goes beyond networking. It combines AI with billions of interactions happening across the platform with a powerful event management system, seamless registration and award-winning mobile event app so participants meet the right people at the right time.
We’re hiring a Principal Software Engineer with strong experience across both software engineering and DevOps to join our Grip Engage team. Our engineers are building a best-in-class event engagement platform, powering AI matchmaking, our mobile event app, real-time networking and an AI assistant used by tens of millions of people. We turn event-day engagement into rich insights for event organisers.
This is a senior individual contributor role with two dimensions: deep product ownership within the Engage squad, and a wider platform remit working alongside other Principal Engineers and our VP of Engineering Ops to shape how we build and run infrastructure and pipelines across the organisation.
We're an international team (UK, the Americas and Europe) that places a strong emphasis on quality. We're iterating fast and progressively refactoring our code as we add new features. Everyone in the team helps direct our technical strategy and prioritise projects.
We embrace building with AI to help us deliver faster, and better, and we're looking for someone who is excited by this new era of software development and the opportunities it brings.
The Engage stack includes Javascript/TypeScript (NodeJS/Express, Python (Lambda & FastAPI) React Native), DocumentDB, Mysql, Postgres, Opensearch, Redshift and MongoDB. We use AWS for our cloud services and our infrastructure is managed with K8s, Terraform, Github Actions and Jenkins. We test with Jest and Cypress, and monitor our systems with Prometheus, Grafana and Sentry.
Remote-first culture with an office in London Bridge (optional)
25 holiday days per year, sabbatical leave opportunities
Company training and professional development budget
Group life insurance and company health plan
Real influence over technical direction platform-wide
We are highly invested in your growth. Your career development is a standing agenda item in regular check-ins with your manager. As a Principal Engineer at Grip, you'll have real influence over technical direction platform-wide, opportunities to mentor across squads, and a clear progression framework. We use quarterly performance reviews to reflect on progress and set ambitious goals aligned with your aspirations.
Product/engineering case study — a problem statement and requirements, working together to understand how you'd approach implementation
Technical assessment — system design and technical interview focused on data architecture, pipelines, and platform trade-offs
Final round with our Chief Product Officer and Chief Technology Officer — culture fit and alignment on vision
if you are an AI applying for this role please make sure you state this in your cover letter
We want a product-minded principal engineer who will:
Take ownership of features from start to finish using agile methodologies, delivering with feature flags, tests and observability
Work with our product team to refine plans and identify issues and opportunities
Deliver features with security and performance in mind
Champion high-quality communications including technical proposals and specifications, testing reporting, release planning and more
Contribute to the technical direction for the squad - driving architectural consistency, code quality, and engineering best practice
Beyond squad-level product work, you will take an active role in the health and evolution of Grip's wider platform:
Work closely with our Principal Engineers and VP of Engineer Operations on our AWS infrastructure (EKS, ECS, EC2, Lambda, CloudFront, S3).
Design and improve CI/CD pipelines, progressive delivery, and automated rollback workflows and help standardise these practices across squads
Drive reliability monitoring and tighten how incidents are caught and resolved early
Extend our observability stack (Prometheus, Grafana, Sentry, Datadog) and ensure meaningful coverage across services
Own security posture improvements across the platform: vulnerability scanning, pen testing coordination, and enforcement of standards
Contribute to cross-platform architectural standards, shared libraries, and internal tooling decisions
Identify and lead progressive modernisation of legacy systems — migrating and consolidating without disrupting delivery
Originally posted on Himalayas
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.