Salary
💰 $167,000 - $200,000 per year
Tech Stack
AWSCloudDistributed SystemsDockerGoogle Cloud PlatformGraphQLJavaJavaScriptKotlinKubernetesMicroservicesNode.jsPythonReactRedisSpringSpring BootSpringBoot
About the role
- At Prosper, the Foundation team builds core tools, services, and shared libraries that enable product teams to build, ship, and run software quickly, reliably, and securely.
- Seeking a motivated platform engineer to design, build, and maintain robust, scalable services and frameworks for internal engineering customers.
- Responsibilities include owning shared libraries (e.g., internal Spring Boot library), building cloud-native microservices (Security, Document, Communication), partnering with product teams and SRE, and driving migration of legacy systems to GCP.
- Technologies used: Java, Kotlin, SpringBoot, REST APIs, NodeJs, Microservices, Python, GraphQL, React, Javascript, GCP.
- This role is hybrid: based two days a week (Wednesday & Thursday) from the San Francisco office.
Requirements
- BS in EE/CS with 8+ years of experience or MS in EE/CS or other applicable disciplines with 6+ years of experience.
- Proven experience working on a platform, foundations, or core services team is strongly preferred.
- Strong grasp of computer science fundamentals, including algorithms, object-oriented design, and distributed systems architecture.
- Expert-level proficiency in Java and the Spring Boot ecosystem, with specific experience designing, building, and distributing shared libraries or frameworks.
- Deep experience designing and building RESTful APIs and event-driven systems to be consumed by multiple engineering teams.
- Hands-on expertise with both relational and non-relational databases (e.g., Firestore, Redis, MemoryStore).
- Experience developing and operating services in a modern cloud environment (GCP or AWS) that utilizes CI/CD, containerization (Docker, Kubernetes), and infrastructure-as-code.
- Expertise in Authentication and Authorization solutions (e.g., OAuth2, OIDC, JWT).
- Familiarity with how backend APIs are consumed by various clients (e.g., front-end web, mobile, other services).