Shell Trading Technology Careers in London: Freight Engineering Roles

Jobs at shell

Energy-trading software engineers build and operate systems where data quality, timing, controls and resilience can affect commercial and regulated decisions. Shell’s official careers material describes software-engineering work and Trading & Supply hubs including London, but it does not make every role remote. Candidates should verify the exact requisition, hub cadence, on-call, data and market responsibilities. A strong portfolio demonstrates secure delivery, reconciled data, failure recovery and human controls without exposing trading logic or confidential positions.

What to verify

  • The official requisition, London or other hub, employment country, office cadence, permitted remote days, time-zone coverage, travel and current status.
  • Whether the system supports freight, physical energy, derivatives, scheduling, risk, settlements, data or analytics and which regulated controls apply.
  • Authoritative sources for instruments, counterparties, prices, trades, positions and settlements; identify freshness, lineage and reconciliation requirements.
  • Availability, latency, recovery, audit, change-approval, segregation-of-duties, access and incident-escalation expectations.
  • Current compensation and benefits from the official posting or offer; remove any historical vacancy terms.

Build evidence you can share

  • Create a fictional trade-lifecycle map from capture through validation, confirmation, position, risk, scheduling and settlement. Name system owners and control points.
  • Design idempotent ingestion and replay for market or reference data, with schema validation, stale-data detection, lineage and business reconciliation.
  • Threat-model privileged actions, service identities, secrets, approvals, log integrity and administrative access using least privilege.
  • Build a failure case: bad price, duplicate event, delayed feed or partial outage. Show detection, business stop, containment, correction, replay and post-incident action.
  • Explain observability across technical health and business correctness. A green service is not healthy if positions or settlements disagree.

For every example use context, responsibility, method or control, observable result, limitation and verifier. Separate fact, scenario and inference. Remove confidential employer, client, candidate, health, security or financial data. A smaller defensible example is more useful than a large unverified claim.

Put the guidance into practice

  1. Locate the exact role on the official careers site and record its hub, flexibility, on-call, business area and posting date.
  2. Map your projects to distributed systems, data quality, security, controls, incident handling and stakeholder communication.
  3. Create a sanitized architecture using fictional commodities, counterparties and values. Exclude algorithms, positions, identifiers and proprietary control thresholds.
  4. Ask how engineering partners with traders, operators, risk, compliance and settlements, and which decisions require human approval.
  5. Verify the recruiter and offer through official domains. Compare work mode and compensation with the written requisition before accepting.

Safety, accessibility and trust

Trading systems and data are commercially and regulatorily sensitive. Never publish live positions, pricing logic, credentials, counterparty data, surveillance rules or incident details. This guide does not provide trading, legal or regulatory advice; employer controls and applicable authorities govern. Use independently reached official domains. Never pay an individual for recruitment, equipment, training, identity checks or account recovery; never share passwords, one-time codes or unrestricted identity files. Provide keyboard-accessible controls, clear headings, descriptive links and text alternatives. Material medical, legal, tax, employment, privacy or security decisions require accountable qualified review.

Primary and official sources

Access date: 2026-08-09.

FAQ

Is Shell trading software work fully remote?

The official careers pages describe global hubs and software roles, but each requisition controls work mode. Confirm London cadence and on-call directly.

Do I need to be a trader?

Not necessarily, but engineers must learn the relevant lifecycle, data, controls and business consequences and know when to escalate.

What portfolio evidence is safe?

Use fictional trades and data to show architecture, reconciliation, security and failure recovery. Never expose proprietary positions or logic.

Why is business reconciliation different from monitoring?

Infrastructure can be available while trades, positions or settlements are wrong. Business reconciliation checks the consequential outcome.

Turn insight into action

Choose your next step

Keep your momentum with practical tools and verified remote-work opportunities.

01Find remote jobsBrowse current roles with clear location and application details.02Use career toolsImprove your search, application, interview, and career decisions.03Explore the Remote Work PassportSee what you can share and how to set up your profile.
WorkinVirtual community

Discuss this guide

Ask a useful question, share relevant experience, or add a practical correction. Helpful contributions publish immediately after automated safety checks.

0 public contributions
Keep it useful and safe. No applications, self-promotion, contact details, payment requests, identity documents, harassment, or external links. Job-specific questions belong in the protected “Ask the employer” channel.

Start a thoughtful discussion

Be the first member to add a question or practical insight about this topic.