Software Engineer

Credo•San Jose, CA

2d•$100,000 - $135,000•Onsite

About The Position

The Corporate Strategy group at Credo is looking for a Software Engineer to join our team in San Jose, CA and drive automation of internal workflows and toolsets, reporting to the SVP of Product. In this role, you become an integral part of the Corporate Strategy Team, mapping business processes across functional organizations, and identifying opportunities for automation using modern AI tools. This position emphasizes hands-on engagement with internal stakeholders, including business users, IT, and executive management, to negotiate data and process flow changes, define product requirements, and determine build-versus-buy paths. The role will also partner with cross-functional teams to develop, integrate, and drive adoption of AI-powered internal tools that accelerate Credo's operations.

Requirements

Bachelor's degree in computer science, software engineering, engineering, mathematics, or a related field, or equivalent demonstrated ability to build and ship software.
Two or more years writing production software, including at least one application you took from empty repository to real users and then supported once it was live.
Strong data modeling and systems-thinking skills, with the ability to turn ambiguous business processes, messy operational data, and evolving business rules into clear schemas, workflows, and application logic.
Working fluency in Python and SQL (Structured Query Language), plus experience building modern web applications across frontend frameworks, backend APIs, and relational databases.
Hands-on experience building with LLM application programming interfaces (APIs), not just using AI coding assistants or chat products.
Ability to write and communicate clearly for technical and non-technical audiences alike.
Comfort operating with competing priorities and incomplete information, and willingness to sit with business users to figure out what they actually need.

Nice To Haves

Two to five years in business process automation, internal tooling, or a forward-deployed engineering role, with tools that non-technical users logged into weekly rather than prototypes that were demoed once.
Experience building evaluation harnesses for LLM features, and a view on when a language model is the wrong tool for the job.
Integration work against enterprise systems of record: a customer relationship management (CRM) platform, an enterprise resource planning (ERP) system, a cloud data warehouse, and the Microsoft 365 and SharePoint APIs.
Track record of build-versus-buy judgment, including at least one case where you evaluated options and correctly chose to buy.
Domain literacy in semiconductors, hardware, or supply chain: bookings, backlog, design wins, forecast accuracy, bills of materials, lead times.
Experience working directly with executives, including presenting recommendations and having them challenged in the room.
Something you built outside of work that real people use or have used, and that you can demo.

Responsibilities

Partner with cross-functional teams to map how work actually happens, then build the fix yourself. Embed with sales, operations, finance, product, and procurement to trace how data and decisions move through their systems and spreadsheets and turn what you find into a prioritized automation backlog.
Build and ship internal applications end to end. Data model, backend, interface, authentication, deployment, and production ownership, with your first tool in the hands of real users inside your first month.
Wire Credo's systems of record together. Build and maintain integrations across all of our existing tools and data sources. Ensure sources of truth and resulting data is clean enough decision-makers can act on it without asking who checked the numbers.
Apply LLM tools where they fit and evaluate them rigorously. Retrieval, tool calling, and agentic workflows for multi-step tasks, each shipped with an accuracy target you can defend.
Own adoption, not delivery. Training, documentation, and office hours are part of the job, and you will be measured on weekly active users and on decisions that changed because of what you built, not on features shipped.