Software Engineer, Platform
Job description
About the role
The role centers on platform services and developer experience for the Factory platform. You will partner with AI researchers to integrate platform components. Ownership of core infrastructure and internal tools defines the scope of this position. You will be responsible for designing and implementing the foundational services that power the development workflows of the organization. This position requires a proactive approach to identifying bottlenecks in the developer lifecycle and creating robust solutions. Collaboration is deeply embedded in the work, as you will work closely with cross-functional partners to translate requirements into technical implementations. Your contributions will directly impact the efficiency and velocity of the entire engineering organization. The position demands a strong sense of ownership to maintain and evolve critical systems that serve as the backbone for product development.
Key facts
What you'll do
Investigate and enhance search and indexing services to ensure rapid and accurate data retrieval across the platform.
Design and maintain authentication mechanisms that guarantee secure and seamless access for internal engineering workflows.
Optimize billing flows to support reliable operation and accurate transaction processing within the platform ecosystem.
Orchestrate integrations with external services to create cohesive experiences for internal tools and end users.
Construct and refine internal tooling to improve usability, efficiency, and onboarding for engineering teams.
Champion the support of foundational systems through close collaboration with AI researchers and engineers on component integration.
Analyze complex system requirements and translate them into resilient software architectures that scale under load.
Monitor production systems to identify performance regressions and drive improvements for high reliability.
Requirements
A degree in Computer Science, Engineering, or a related field is required alongside 3+ years of full stack engineering experience.
Experience building complex, high-performance, and reliable systems is necessary to thrive in this environment.
Background in software analysis tools, compilers, runtime systems, or similar domains is valued for this position.
Proficiency in one or more languages such as Python, Java, or C++ is required to implement core platform logic.
Familiarity with Git and CI/CD pipelines is required to automate the build, test, and deployment processes.
Understanding of systems programming and large codebases is necessary to navigate challenges in code manipulation and comprehension.
Strong debugging skills are essential to isolate issues in distributed systems and resolve them efficiently.
The ability to learn and adapt to new technologies quickly is essential given the fast-paced nature of the platform work.
Practical notes
The team works from the San Francisco office five days a week, with a location that is within walking distance of Caltrain.
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds.
Candidates often solve a coding problem, discuss past projects, and answer system design questions.
Some loops include a take-home task.
Final rounds typically cover team fit and give candidates a chance to ask questions.
Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer.
Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Platform roles focus on foundational services that enable product teams.
Strong full stack engineering skills are central to success in this area.
Toolchains such as Git and CI/CD are integral to daily workflows.
Collaboration with AI research efforts is common in platform-oriented positions.
Clear communication across engineering teams is essential for maintaining code quality and architectural consistency.
Questions to ask
Good questions to ask the employer in the interview: what does success look like in the first six months, how is the team structured, what is the current biggest challenge, and how are decisions made.
Asking about growth paths and the review process is also well received.
Employers expect questions, and good ones show preparation.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels.
Some engineers move into management and lead teams of five to twenty people.
Others stay on the technical track.
Growth follows demonstrated impact, not tenure alone.
A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship.
Moving up usually requires owning outcomes end to end rather than completing assigned tickets.