Lead Software Engineer – Test
San Francisco, California / $180000 - $210000
INFO
$180000 - $210000
LOCATION
San Francisco, California
Permanent
LEAD SOFTWARE ENGINEER -- TEST
HYBRID - REMOTE
SAN FRANCISCO, CA $180,000 - $210,000 + Competitive Benefits
Join a dynamic team and help drive the future of AI! As a Lead Engineer in Test Automation & QA, you'll play a critical role in shaping the growth of a fast-growing startup and pushing the boundaries of cutting-edge technology.
THE COMPANY
- COMPANY: Well-funded startup at the forefront of using AI to solve core industry challenges.
- TEAM: You will work alongside many talented Software Engineers and Applied Scientists. There will also be frequent opportunities to grow your leadership skills while still contributing as an individual.
- CULTURE: Highly collaborative and flexible work environment
THE ROLE
As a Lead Software Engineer in Test you will…
- Develop and implement a comprehensive test roadmap by analyzing the product and technology stack, identifying areas of improvement, and prioritizing testing efforts.
- Work closely with development and DevOps teams to ensure their code is being tested effectively.
- Take the company's current Minimum Viable Product version of their staging environment and elevate it to a more robust and reliable state to support effective testing.
YOUR SKILLS AND EXPERIENCE
- 5+ years of experience as a senior or staff-level engineer.
- Experience working with infrastructure teams, DevOps, and performing QA/testing in data-centric companies.
- Strong engineering skills and background with a focus on ensuring the backend of an application is working effectively.
- Prior experience working on data-intensive projects.
THE BENEFITS
As a Lead Software Engineer in Test, you can expect a base salary between $180,000 - $210,000 (based on experience) plus competitive benefits.
HOW TO APPLY
Please register your interest by sending your CV to Pouran Mehraban via the Apply link on this page.

SIMILAR
JOB RESULTS

Data Engineer Or Software Engineer: What Does Your Business Need? | Harnham US Recruitment post
+
We are in a time in which what we do with Data matters. Over the last few years, we have seen a rapid rise in the number of Data Scientists and Machine Learning Engineers as businesses look to find deeper insights and improve their strategies. But, without proper access to the right Data that has been processed and massaged, Data Scientists and Machine Learning Engineers would be unable to do their job properly. So who are the people who work in the background and are responsible to make sure all of this works? The quick answer is Data Engineers!… or is it? In reality, there are two similar, yet different profiles who can help help a company achieve their Data-driven goals. Data Engineers When people think of Data Engineers, they think of people who make Data more accessible to others within an organization. Their responsibility is to make sure the end user of the Data, whether it be an Analyst, Data Scientist, or an executive, can get accurate Data from which the business can make insightful decisions. They are experts when it comes to data modeling, often working with SQL. Frequently, “modern” Data Engineers work with a number of tools including Spark, Kafka, and AWS (or any cloud provider), whilst some newer Databases/Data Warehouses include Mongo DB and Snowflake. Companies are choosing to leverage these technologies and update their stack because it allows Data teams to move at a much faster pace and be able to deliver results to their stakeholders. An enterprise looking for a Data Engineer will need someone to focus more on their Data Warehouse and utilize their strong knowledge of querying information, whilst constantly working to ingest/process Data. Data Engineers also focus more on Data Flow and knowing how each Data sets works in collaboration with one another. Software Engineers – DataSimilar to a Data Engineers, Software Engineers – Data ( who I will refer to as Software Data Engineers in this article) also build out Data Pipelines. These individuals might go by different names like Platform or Infrastructure Engineer. They have to be good with SQL and Data Modeling, working with similar technologies such as Spark, AWS, and Hadoop. What separates Software Data Engineers from Data Engineers is the necessity to look at things from a macro-level. They are responsible for building out the cluster manager and scheduler, the distributed cluster system, and implementing code to make things function faster and more efficiently. Software Data Engineers are also better programers. Frequently, they will work in Python, Java, Scala, and more recently, Golang. They also work with DevOps tools such as Docker, Kubernetes, or some sort of CI/CD tool like Jenkins. These skills are critical as Software Data Engineers are constantly testing and deploying new services to make systems more efficient. This is important to understand, especially when incorporating Data Science and Machine Learning teams. If Data Scientists or Machine Learning Engineers do not have a strong Software Engineers in place to build their platforms, the models they build won’t be fully maximized. They also have to be able to scale out systems as their platform grows in order to handle more Data, while finding ways to make improvements. Software Data Engineers will also be looking to work with Data Scientists and Machine Learning Engineers in order to understand the prerequisites of what is needed to support a Machine Learning model. Which is right for your business? If you are looking for someone who can focus extensively on pulling Data from a Data source or API, before transforming or “massaging” the Data, and then moving it elsewhere, then you are looking for a Data Engineer. Quality Data Engineers will be really good at querying Data and Data Modeling and will also be good at working with Data Warehouses and using visualization tools like Tableau or Looker. If you need someone who can wear multiple hats and build highly scalable and distributed systems, you are looking for a Software Data Engineer. It’s more common to see this role in smaller companies and teams, since Hiring Managers often need someone who can do multiple tasks due to budget constraints and the need for a leaner team. They will also be better coders and have some experience working with DevOps tools. Although they might be able to do more than a Data Engineer, Software Data Engineers may not be as strong when it comes to the nitty gritty parts of Data Engineering, in particular querying Data and working within a Data Warehouse. It is always a challenge knowing which type of job to recruit for. It is not uncommon to see job posts where companies advertise that they are looking for a Data Engineer, but in reality are looking for a Software Data Engineer or Machine Learning Platform Engineer. In order to bring the right candidates to your door, it is crucial to have an understanding of what responsibilities you are looking to be fulfilled.That’s not to say a Data Engineer can’t work with Docker or Kubernetes. Engineers are working in a time where they need to become proficient with multiple tools and be constantly honing their skills to keep up with the competition. However, it is this demand to keep up with the latest tech trends and choices that makes finding the right candidate difficult. Hiring Managers need to identify which skills are essential for the role from the start, and which can be easily picked up on the job. Hiring teams should focus on an individual’s past experience and the projects they have worked on, rather than looking at their previous job titles. If you’re looking to hire a Data Engineer or a Software Data Engineer, or to find a new role in this area, we may be able to help. Take a look at our latest opportunities or get in touch if you have any questions.

Keepers of the Data Kingdom: the Analytics Engineer | Harnham US Recruitment post
+
If it seems the Data world is drilling down further into niche specialities, you’re right. Considering the swathes of information sent and received on a day-by-day, minute-by-minute, and second-by-second basis, is it any wonder? The sheer volume, depending on your business and what you want to know, requires not just a Data team, but must now include someone with a particular skillset, including the tech-savvy analyst who can speak to the executive team.So, who holds it all together? These swathes of information. Who organizes the information in a cohesive order, so anyone with a map, can make their own analyses? Enter the Analytics Engineer.What Makes an Analytics Engineer an Analytics Engineer?Though it’s a rather new speciality within the Data Scientist scope—think Machine Learning Engineer, Software Engineer, Business Analyst, etc—at its core, the definition of an Analytics Engineer is this: “The analytics engineer sits at the intersection of the skill sets of data scientists, analysts, and data engineers. They bring a formal and rigorous software engineering practice to the efforts of analysts and data scientists, and they bring an analytical and business-outcomes mindset to the efforts of data engineering.” Michael Kaminsky, consultant, and former Director of Analytics at Harry’s.In other words, analytics engineers, using best software engineering practices transform data through testing and documentation so that data analysts begin with cleaner data to analyze. As technically savvy as the engineer must be, they must also be able to explain to stakeholders what they’re looking at so they can formulate their own insights. Five Roles and Responsibilities of the Analytics EngineerLike all new niche specialities, there are core responsibilities to consider as well as that of skillsets required to either study to become an Analytics Engineer or to discover if you’re one already. How? Consider the questions you ask, your studies within Data Science, Computer Science, Statistics, and Math, and your balance between technical skills and soft skills. Below are five things to consider when thinking about this role:Programming language experience. Experience with programming languages like R and Python along with strong SQL skills which are at the core of this role. DBT technology knowledge. As the driving force behind the rise of Analytics Engineer as a separate role, it’s imperative anyone interested in pursuing it should have a firm grasp of DBT — the Data Build Tool — that allows the implementation of analytics code using SQL. Data tracking expertise using Git. Data modelling. Clean, tested, and raw data which allow executives and analysts to view their Data, understand it within the database or its warehouse. Data transformation. Analytics Engineers determine what Data is most useful and transform it to ensure it fits related tasks. It’s part of building the foundational layer so businesses can answer their own questions. Key Changes Leading to the Shift in Data RolesWith every technological advancement their comes new players to the field. The difference is here is that the job description already existed. We were only missing a title. But from the traditional Data team to the modern Data team, there are a few key changes that point directly to the rise of this niche field. Cloud warehouses (like Snowflake, Redshift, BigQuery) and the arrival of the DBT the foundational layer which can be built on top of modern data warehouses are the first two that come to mind. Then, the Software-as-a-Service (SaaS) tools like Stitch and Hevo are capable of integrating Data from a variety of sources, and the introduction of tools like Mode and Looker allows anyone interested in drawing insight from Data to do so on their own.Who Needs an Analytics Engineer? Small or Large Businesses?The short answer is it depends. But the general rule follows that while both large and small companies can benefit from having this professional on their staff, there are different things to consider. For example, a small business may be able to find what they need in a single individual. The Analytics Engineer is something of a jack-of-all-trades. Larger businesses, on the other hand, may already have a Data team in place. In this case, an Analytics Engineer adds to your team, something like an additional set of eyes increasing insight drawn from those large swathes of Data we spoke about earlier.So, what’s next for the role of Analytics Engineer? Who knows? The roles of any Data industry professional is constantly evolving. If you’re interested in Analytics Engineering, Machine Learning, Data Science, or Business Intelligence just to name a few, Harnham may have a role for you. Check out our latest Data & Analytics Engineering jobs or contact one of our expert consultants to learn more. For our West Coast Team, contact us at (415) 614 – 4999 or send an email to sanfraninfo@harnham.com. For our Arizona Team, contact us at (602) 562 7011 or send an email to phoenixinfo@harnham.com. For our Mid-West and East Coast teams contact us at (212) 796-6070 or send an email to newyorkinfo@harnham.com.

Sustainable Software And The Future Of Our Planet | Harnham Recruitment post
+
“Keep 1.5 Alive” The 2015 Paris Agreement pledge that has become the battle cry of COP26, rings in our ears as leaders look at ways that countries and corporations can limit global warming to 1.5 degrees Celsius to mitigate the devastating effects of climate change. New analysis by the Climate Action Tracker calculates that the world is heading for 2.4C of warming and with that in mind the need to adapt and embrace technologies that tackle and reduce the impact of climate change, is ever more pressing. The technology sector is well-placed to embrace data initiatives in support of a more sustainable future. Sustainable software and green data are emerging disciplines at the intersection of science, technology and climate science, which when considered as part of a business’ wider Environmental Social and Governance (ESG) policy can help businesses play their part in the Global Development Goals. The concept of sustainability is built around three pillars: ecological, economical, and social sustainability and there are a number of things to consider across the whole software lifecycle, from planning and programming, distribution and installation, usage, and disposal. Considering the first of these, the ecological impact of software, we can begin to see how sustainable software engineering can help bring positive change. The ecological impact of software Considering how to minimise resource and energy consumption are key. As pointed out by the Harvard Business Review, on its own, software doesn’t consume energy. The problem lies within the way software is developed, used and stored. Addressing hardware requirements Software runs on hardware, and as more software is developed, the reliance on hardware increases. In an ideal world, software requires as little hardware capacity as possible, and is compatible with power save settings and facilitates the ability of individual components to make optimum use of working memory. Longevity is also key, with software updates often rendering it impossible on older hardware. Improving software development Asking what is the smallest possible environmental footprint that could be used to make an application to guide the first stages of the software development cycle, should be fundamental. Allowing Software Engineers the flexibility of trade-off software performance with environmental impact is key. Using AI as an example, consider that training a single neural network model can emit as much carbon as five cars in their lifetimes, and the exponential increase in computational power required to run large AI training models, balancing performance against ecological impact might be a worthwhile consideration. Data Storage Not only might software development be a focus for businesses looking to improve their carbon footprint but also a consideration of data storage. Data centres consume about 2% of global electricity today; by 2030, they could consume as much as 8%. With modern applications often deployed over the cloud, factoring in software deployment methods and storage requirements might help turn curb this trend. How Software Engineers can help make software accountable The principles of Sustainable Software Engineering are a core set of competencies needed to define, build, and run sustainable software applications and companies have a duty to make software an integral part of their sustainability efforts. By judging data and software’s performance on its energy efficiency and by including green practices and targets in CIO performance reviews, business can help Keep 1.5 Alive. If you have competencies in sustainable software development or a business looking to incorporate green data initiatives, take a look at our latest Software Engineer jobs.

CAN’T FIND THE RIGHT OPPORTUNITY?
STILL LOOKING?
If you can’t see what you’re looking for right now, send us your CV anyway – we’re always getting fresh new roles through the door.