SIM Management, 5G Core Engineer
E-Space · Santa Clara, CA · 1 mo ago
On-siteEngineering$170k–$200k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Pay: posting states "$170,000 - $200,000 a year". So we can include Pay section with that. Schedule: not mentioned explicitly; maybe full time, exempt position, based out of Santa Clara, CA office. Could infer schedule: full-time. But we should not create Schedule unless posting actually states them. It says "This is a full time, exempt position". That's schedule info (full-time). So we can include Schedule with "Full-time". Benefits: there is a list: "Some of what you can expect when working at E-Space: An opportunity to really make a difference Sustainability at our core Fair and honest workplace Innovative thinking is encouraged Competitive salaries Continuous learning and development Health and wellness care options Financial solutions for the future Optional legal services (US only) Paid holidays Paid time off". That's benefits. So include Benefits section with those bullet points.
About the role: The introductory paragraph before "Key Responsibilities". Should be included as About the role. Must preserve all substantive info. So we need to capture the paragraph: "Ready to make connectivity from space universally accessible, secure and actionable? Then you’ve come to the right place! E-Space is bridging Earth and space to enable hyper-scaled deployments of Internet of Things (IoT) solutions and services. We are building a highly-advanced low Earth orbit (LEO) space system that will fundamentally change the design, economics, manufacturing and service delivery associated with traditional satellite and terrestrial IoT systems. We’re intentional, we’re unapologetically curious and we’re 100% committed to innovate space-based communications and deliver actionable intelligence that will expand global economies, protect space and our planet and enhance our overall quality of life. The SIM Management 5G Core Engineer will analyze, design, implement, and verify the configuration and integration of subscriber data management nodes(UDR / UDM), networks, and systems across our 5G infrastructure. Your scope of work includes introduction, upgrade, expansion, functionality, and capacity scenarios on modern cloud-native UDM and UDR deployments. You will be a key contributor to the convergence of subscriber databases as platform evolves — and your work will directly shape the reliability and scalability of the networks our partners depend on."
That is About the role.
Responsibilities: The bullet list under "Key Responsibilities". We need to convert to
- . Must preserve all details.
Qualifications: There's "Key Qualifications" with sub-bullets Technical — Subscriber Data Management, Technical — Network & Systems, Education & Background, Bonus Points..., Additional Requirements. We need to decide sections: Qualifications, Skills, maybe Requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. Likely "Requirements" could contain mandatory qualifications (Key Qualifications). "Skills" could contain bonus points? Or we could combine. But we must not create thin sections. Prefer few substantive sections. We could have About the role, Responsibilities, Qualifications (including education, bonus, additional requirements), Benefits, Pay, Schedule. Possibly also Skills if there is distinct skill list. The posting includes technical skills details under Key Qualifications; we could treat that as Qualifications. Bonus points could be under Skills? But they are also qualifications. Might be better to have Qualifications (mandatory) and Skills (bonus). However the instruction says prefer few substantive sections over many thin ones. So maybe combine all qualification-like content into Qualifications section, and not create Skills unless there is a distinct list separate. There's no separate "Skills" heading in posting. So we can omit Skills.
Requirements: Could be used for mandatory experience/education. But we already have Qualifications. Might be redundant. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we include only when posting has real specific content. So we need to decide which sections we have content for.
We have About the role (intro). Responsibilities (list). Qualifications (Key Qualifications + Education & Background + Bonus Points + Additional Requirements). Benefits (list). Pay (salary range). Schedule (full-time). That seems reasonable.
We must not repeat job title. Must not include Job ID etc. Must not include boilerplate like "We may use artificial intelligence (AI) tools..." that's maybe not boilerplate but it's about hiring process; could be considered part of posting but not substantive? It's about hiring process; maybe we can keep? It's not a responsibility or qualification. It's a note about AI tools. Might be considered boilerplate? It's not EEO/legal but still generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI note is not exactly those but could be considered part of hiring process; maybe we keep? It's not a substantive job detail. Safer to omit? It's not about the role. I'd omit it.
Also duplicate line: "The Company is not currently able to provide employment sponsorship for candidates who do not hold work authorization for the location of this role." appears twice; we should keep only once? The instruction: remove duplicated lines. So we should include only one instance if we keep it. But is that substantive? It's a requirement about work authorization. Could be considered a requirement. Might be placed under Qualifications or Requirements. But we already have many qualifications. Could include as a line under Qualifications. However it's a requirement about sponsorship. Might be considered a requirement. We'll include it once under Qualifications.
Now we need to format.
We'll produce:
About the role
... paragraph ...
Responsibilities
- Manage and operate UDR, and UDM nodes across 5G core domain, ensuring high availability and data integrity for subscriber profiles.
- Design and maintain subscriber provisioning workflows, including IMSI/MSISDN management, service profiles, and roaming configurations.
- Implement and verify HTTP/2-based (N8, Nudm) interfaces connecting subscriber data nodes to AMF and other core elements.
- Use and build dashboards to monitor subscriber node KPIs, quickly surface abnormal conditions, and identify patterns before they become outages.
- Own incident management for the subscriber data domain: follow communications procedures for internal escalation and external vendor coordination, ensuring SLAs are met.
- Perform maintenance, security audits, patching, and emergency response for UDM/UDR platforms.
- Undertake fault handling and corrective actions at node, service, and infrastructure level, including protocol trace analysis (Wireshark/tcpdump) on HTTP/2 signaling.
- Lead and contribute to project activities: E2E introduction of new subscriber management nodes, capacity expansions, software upgrades, and feature activations.
- Support onboarding by configuring subscriber data repositories, IMSI ranges, and roaming agreements in UDM/UDR systems.
- Collaborate with teams to resolve cross-domain subscriber authentication and registration issues.
Qualifications
At least 10 years of experience in core network engineering with a focus on subscriber data management in 5G Core networks.
- Technical — Subscriber Data Management: Deep operational knowledge of HSS/HLR or UDR/UDM platforms. Hands-on experience with configuration and troubleshooting. Practical experience with 5G UDM and UDR, including cloud-native deployments (containerized/Kubernetes-based NFs) and HTTP/2 SBI interfaces (N8, Nudm_SubscriberDataManagement, Nudr_DataRepository). Solid understanding of subscriber profile structures: 5GS subscription. Experience with IMSI/MSISDN range management, number portability (NP/MNP) integration, and SIM/eSIM provisioning workflows.
- Technical — Network & Systems: Working knowledge of 5G SA (AMF/SMF/UDM/UDR/AUSF/UDSF) core architectures and their subscriber data flows. Familiarity with 3GPP standards governing subscriber data: TS 29.503/29.504 (UDM/UDR SBI), TS 23.502 (5G procedures). Comfortable with Linux/Unix-based systems — able to navigate shells, interpret logs, manage processes, and perform basic system administration on telecom NF hosts. Hands-on with Wireshark, tcpdump, and vendor-specific trace tools for deep analysis of MAP, Diameter, and HTTP/2 subscriber signaling. Experience with high-availability configurations for subscriber databases: active/standby, geo-redundancy, and database replication/synchronization. Familiarity with cloud-native telecom platforms (Kubernetes) and Helm-based NF lifecycle management.
- Education & Background: Bachelor's or Master's degree in Telecommunications, Computer Science, or equivalent; post-graduate studies are a plus. 10+ years of core telecommunications network experience, with a minimum of 5 years hands-on with HLR, HSS, UDR, or UDM platforms.
- Bonus Points for the Following: Experience with 3GPP NTN core adaptations (Rel-17/18): satellite access node (SAN) architecture, timer and window parameter adaptation for high-latency links, or UPF placement in non-terrestrial topologies. Background in MVNO core architecture: roaming interfaces (N32/SEPP, Diameter S6a/S9), multi-PLMN federation, MVNO interconnect, or eSIM/SM-DP+ integration. Familiarity with 3GPP SA2/CT4 specifications or direct standards contribution experience. Experience with NEF or network exposure APIs and B2B API gateway architecture. Background in SIM provisioning platforms, subscription management, or UDM/HSS data modelling. Experience in a startup or fast-paced R&D environment where architectural decisions move at product speed.
- Additional Requirements: This is a fast-paced, high-impact environment - flexibility to occasionally work extended hours or weekends during critical periods is expected. This is a full time, exempt position, based out of our Santa Clara, CA office. The total compensation packaged will be determined by various factors such as your relevant job-related knowledge, skills, and experience. We are redefining how satellites are designed, manufactured and used—so we’re looking for candidates with passion, deep knowledge and direct experience on LEO satellite component development, design and in-orbit activities. If that’s your experience – then we’ll be immediately wow-ed. E-Space is not currently able to provide employment sponsorship for candidates who do not hold work authorization for the location of this role.