Senior Staff Software Engineer – Data Platform

This is a software engineering role on a software engineering team. The team builds and operates the data platform: the infrastructure, abstractions, and SDKs that the rest of Marqeta's data and ML organization runs on. We are not writing pipelines–we are building the platform pipelines run on. If you've spent your career building infrastructure that other engineers depend on; and you know the difference between “software engineering” and "data engineering", read on. We work Flexible First. This role can be performed remotely anywhere within the United States or from our Oakland office. We’d love for you to join us! Learn more about our Product and Engineering team. At Marqeta, participation in a rotational on-call pager duty is a required part of the software engineering role. The specifics of the rotation may vary by team, depending on team size and structure, and will be discussed further during the interview process. What you'd own The lakehouse and the streaming ingestion that feeds it. Iceberg/Delta on S3, Spark/Glue processing, Kafka and CDC pipelines, the abstractions that let other teams land data, build pipelines, and publish datasets without inventing the patterns themselves. You’d help set the multi-year technical direction, design the golden paths, and ship the work — directly, with your hands on the code that matters. How the team works You’d report to the Director of Data Engineering and partner with a peer Manager whose scope is people leadership and operational delivery. You own technical direction, application architecture, and the engineering bar. You’ll work alongside other senior staff engineers across the broader data platform org, and partner with security, compliance, and the consumer teams who depend on what we ship. What "hands-on" actually means here Worth being specific, because “hands-on” means different things to different people: - Yes: writing production code on the platform's hardest problems, owning the design and build of new abstractions end-to-end, leading design reviews, setting the engineering bar through the work itself. - Sometimes: prototyping, deep diving on a tricky migration, pairing with engineers on tough problems. What the work looks like - Modernization. Building out the lakehouse — the patterns Marqeta will run on for years. New abstractions, new tooling, the paved road internal teams want to use. - Live system work. Evolving and hardening the platform that's already in production. Reliability, performance, developer experience — improved without disrupting the teams who depend on it. - Engineering excellence. Testing confidence, release velocity. On call, blameless postmortems. What you bring We care more about demonstrated work than years on paper, but the experience this role asks for typically takes around a decade to accumulate. - A career building data platforms, not just pipelines. You can name the abstractions you've designed, the teams that adopted them, and the problems they solved. If most of your last several years has been writing transformations rather than building the system transformations run on, this isn't the right shape. - Production depth in modern lakehouse work. Iceberg or Delta in production. Strong fluency in the surrounding stack: AWS data services (S3, Glue, EMR), Spark, Airflow, Kafka, IAM boundaries for multi-tenant data access. You don't need depth in all of it — you need real depth in the lakehouse and credible engagement with the rest. - Mastery of Python in a production data-platform context, with credible depth in Go or Java. Idioms, ecosystem, performance characteristics, the parts that bite at scale. The ability to adopt the best tool for the job. - A track record of evolving live infrastructure. Improving reliability, performance, and DX on systems that real teams depend on, sequenced so the work doesn't disrupt them. - Ownership of major platform transitions. Build vs. buy, migration design, risk management, all the way through to delivery. You've led at least one of these end-to-end and can talk through what went right, what didn't, and what you'd do differently. - Influence as a working skill. You build alignment across platform, security, and consumer teams. You write design docs and RFCs people actually read. You can hold a strong technical position and update on evidence. - A history of growing other engineers — including peers at your level. The team gets stronger because you're on it. Helpful, not required: payments or fintech context (PCI-DSS, SOX, SOC 2). CDC tooling experience (Debezium, Kafka Connect). Data governance tooling (DataHub, Amundsen, Collibra). Public technical writing or open-source contributions to data infrastructure. Typical Process - Application Submission - Recruiter Video Call - Coding Interview & Hiring Manager Interview - Virtual "Onsite" consisting of four 45-60 min video calls - Offer! Compensation and Benefits Marqeta is a Flex First company which allows you to choose your best working environment, whether that be from home or at a company office. To support Flex First, we calibrate pay to a competitive value according to working location. Compensation is aligned according to three tiers within the United States: - National: A baseline tier that applies to most of the geographic territory of the United States. - Premium: Slightly elevated from the National tier, and oriented toward a narrower set of higher cost-of-living areas, such as Los Angeles CA and Seattle WA - Premium Plus: A tier for the most expensive working areas, like the San Francisco Bay area and New York City. Visit this page or consult with a Recruiter to determine which tier would be applicable to you. When determining salaries, we consider several factors including, but not limited to, skills, prior experience, and work location. The new-hire base salary range for this position is: - National: 200,500 - 250,600 - Premium: 210,200 - 262,800 - Premium Plus: 220,000 - 275,000 We also believe in recognizing the contributions of our people. That's why we award annual bonuses to eligible employees, rewarding both individual performance and the success of the entire company. Along with monetary compensation, Marqeta offers - Multiple health insurance options - Flexible time off – take what you need - Retirement savings program with company contribution and after tax contributions - Equity in a publicly-traded company and an Employee Stock Purchase Program - Family-forming benefits, fertility support, and up to 20 weeks of Parental Leave - Free therapy sessions, financial and professional coaching, and legal advice - Monthly stipend to support our remote work model - Annual “development dollars” to support our people growth and development - Through Flex First, the freedom to live and work wherever you and your family thrive

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...