Browse All Roles

A typical Tuesday starts with a standup, then a few hours of focused coding on a new feature — maybe adding search to an app. You review a teammate's pull request, fix a bug that showed up in testing, and end the day pushing your changes to a shared codebase.

A typical Tuesday has you exploring a dataset in a Jupyter notebook, trying to understand why user retention dropped last quarter. You build a simple model, share a visualization in a Slack thread, and get pulled into a meeting where a PM asks if your findings support a product change.

A typical Tuesday: you're writing a data pipeline that cleans and prepares training data, testing a new model architecture, and figuring out why the inference latency is too slow in production. You're as much an engineer as a scientist — the code has to actually work at scale.

A typical Tuesday: reading two new papers in the morning, running experiments to test whether a modification to an existing method improves results, writing up your findings in a research document. Progress is slow and uncertain — a week of experiments might produce one interesting data point.

A typical Tuesday: a user interview in the morning to understand a pain point, then a meeting with engineers to clarify requirements for a feature in development, then writing a one-pager for leadership on a new initiative. You're constantly synthesizing — user needs, technical constraints, business goals.

A typical Tuesday: reviewing user research from last week, sketching wireframes for a new onboarding flow in Figma, presenting three design options to the team, and iterating based on feedback. You're constantly advocating for the user in conversations about what to build.

A typical Tuesday: writing a Python script to process genomic sequencing data, running a clustering algorithm to find patterns across thousands of cell samples, then meeting with wet-lab biologists to explain what the computational results might mean for the experiment.

A typical Tuesday: investigating why a deployment pipeline is failing, writing Terraform code to provision a new cloud environment, automating a manual process so the team never has to do it again. You care about reliability, speed, and making other engineers' lives easier.

A typical Tuesday: pulling data from a database with SQL, building a dashboard in Tableau or Looker that shows weekly sales trends, and presenting findings to the marketing team. You translate numbers into stories that help business teams make better decisions.

A typical Tuesday: writing a technical tutorial for a new API feature, recording a short demo video, answering developer questions on Discord, and meeting with the engineering team to relay feedback about a confusing error message. You're a translator between the product team and the developer community.

A typical Tuesday: running a cross-team sync to unblock a delayed feature, updating a project tracking doc, writing a post-mortem on why last sprint's release slipped, and investigating a dependency issue between two engineering teams. You make things move by removing friction.

A typical Tuesday: cleaning and analyzing satellite imagery data to track deforestation, building a model that predicts air quality based on weather and industrial data, and writing a summary for a government agency that will use your findings to inform policy.

A typical Tuesday: seeing patients in a primary care clinic, diagnosing a strep throat, adjusting a diabetes management plan, counseling a patient on anxiety, then reviewing lab results and prescribing medication. You operate with significant independence — in many states you can run your own practice.

A typical Tuesday: analyzing a client's supply chain data to find $5M in savings, building a PowerPoint deck to present recommendations to the C-suite, interviewing a plant manager to understand operational bottlenecks, and catching a flight to a client site. Variety is high, but so is the pace.

A typical Tuesday: updating a financial model to forecast next quarter's revenue, pulling data into Excel to compare actuals vs. budget, writing a variance analysis for the CFO, and joining a call with the sales team to understand pipeline changes. You're the person people come to when they need a number.

A typical Tuesday: interviewing an engineer about a new API endpoint, rewriting the quickstart guide based on user feedback, reviewing a PR that changes a CLI command (to update the docs), and testing a tutorial you wrote to make sure the steps still work. Good docs are invisible — you only notice when they're bad.

A typical Tuesday: mapping out a learning module for new-hire onboarding, reviewing a prototype interactive lesson, meeting with a subject matter expert to fact-check content, and analyzing completion rates from last month's training to see what's working. You use psychology and design to help people learn efficiently.

A typical Tuesday: cleaning a dataset from a county health survey, running regression models to identify risk factors for childhood asthma, writing a brief for a state health department, and joining a call with epidemiologists to discuss surveillance data. Your work influences policy that affects thousands of people.