Inside the client's environment.
You work where the system runs, under the client's security rules, next to the people who will use it and the people who will review it. You see the problem first-hand, not through a ticket.
- About
- Careers
Careers
Build systems the people who rely on them can trust.
Our engineers work inside the client's environment and own the outcome with them, on Google Cloud.
Illustrative exampleWhat the work is.
- Where you workInside the client's environment
- GovernancePart of the build, from the first sprint
- DecisionsOne named owner each
- After handoverYou are there when it goes live
Open roles
Country
No open roles right now. Tell us what you do, and we will write to you when a role that fits opens.
Most engineers never see what happens to their work after handover. Ours do. You work alongside the people who use and review what you build, and you are there when it goes live.
How we work
Governance is part of the build.
The gateway policy, the access rules and the audit trail go in during the first sprint, and you help write them. You learn to build systems a risk team will sign, which most engineers only learn late.
One named owner per decision.
Every gate has a person's name on it, on our side and the client's. You always know who decides, and when the decision is yours, you know that too.
Learning on Google Cloud.
You build on Apigee, Gemini Enterprise, Vertex AI and BigQuery on live client work, and we support you through Google Cloud certification.
A week inside a client
Monday
You agree with the client's owner what this week's demo will show and what could stop it.
Signs: Client ownerTuesday
You build inside the client's environment, on their accounts, with their engineers.
Signs: Our delivery leadWednesday
Anything new gets its gateway policy, access rules and audit trail before it goes further.
Signs: Client security leadThursday
You walk the client's reviewer through what changed and answer their questions.
Signs: Client risk or security reviewerFriday
You demo working software to the people who will sign it off, and their decisions go into the log.
Signs: Client owner
How hiring works
Apply.
Send the form on this page with your resume, or email jobs@sidgs.com. A recruiter reads every application against the role.
A screening conversation.
A recruiter calls to talk through the role, the location, your notice period and what you want to do next.
A technical session.
You work through a real problem with one or two of our engineers: a design, a debugging session or a piece of code. Expect questions about how you would get it through review, not trivia.
An offer.
If it is a fit, you get an offer in writing and we agree a start date with you.
You hear from us by email at every step, including when the answer is no.
Apply
Tell us about yourself. Attach your resume and a few lines on the work you are proudest of. Your application goes to our recruiting team at jobs@sidgs.com.
Write to jobs@sidgs.comForm slot for WPForms. Keep the existing job application fields. Consent line: I agree that SID Global Solutions may store my application and contact me about roles. See our Privacy Policy. Button: Send my application. Confirmation message: Your application is with our recruiting team. You will hear from us at jobs@sidgs.com. If you applied for more than one role, we look at each one.
