Full Stack Engineer, Command
Job description
About the role
This role leads product development for Command, a generative UI interface layered over Meter's internet infrastructure stack. The work blends product, models, and infrastructure to deliver a conversational control plane for network operations. You will shape how users inspect, configure, and resolve issues across networks through an expressive, intelligent interface.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Command drives full stack development across UX, backend, and model integration to unify system workflows. Teams craft frontend features using Next.js, TypeScript, and React to deliver responsive user interactions. Integration of LLMs and AI models enables natural language commands that control network behavior. Collaboration with users and cross-functional teams including modelers, application engineers, and support defines product direction.
Requirements
The posting states a bachelor's degree requirement. You seek excitement at the intersection of product, models, and infrastructure and bring full stack product experience with real users and high stakes. Deep thinking about product feel, interaction design, and system behavior guides quick movement without sacrificing reliability or clarity. Solving real problems for real people matters, and you thrive in early-stage environments where you can take ownership of an ambitious system. A degree as stated in the source requirements remains necessary for this position.
Practical notes
This role is based in San Francisco and requires standard work authorization as defined by applicable laws. The position is full_time with equity eligibility as noted in the compensation details. 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
Roles focused on infrastructure networking combine software design with operations realities. Modern frontend stacks such as Next.js and TypeScript streamline iterative UI delivery. Cloud platforms and database options like Planetscale enable scalable backends. Integration with large language models introduces conversational capabilities into operational tools. Teams building at the intersection of UI and infrastructure move quickly while managing reliability constraints.
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.