Welcome to the SDET Technical Challenge!
This is a take-home technical challenge designed to take between 3-4 hours. It's designed to help us understand how you navigate an unknown technical product, comprehend acceptance criteria, and use your critical thinking skills to design testing scenarios, find issues, and make recommendations.
Fides Cloud is Ethyca's privacy automation platform that helps organizations manage data privacy compliance. In this challenge, you'll be testing our Data Subject Request (DSR) features, which enable consumers to exercise their privacy rights. Upon completion, please submit your E2E test suite and technical write-up in a GitHub repository. We'll then schedule a walkthrough of your solution to discuss the details together.
For this challenge, you'll be accessing a test Fides Cloud instance for an imaginary customer, the "Cookie House." You'll receive an email with your login credentials that will be valid for 7 days from receipt. To get started:
Fides Cloud Dashboard: https://fides-interview-b9f2.fides-staging.ethyca.com/ Privacy Center: https://privacy-fides-interview-b9f2.fides-staging.ethyca.com/ Test Customer Site: https://cookiehouse-fides-interview-b9f2.fides-staging.ethyca.com/
You're an Ethyca SDET helping the Lethe engineering team with a new feature: Access and Erasure Data Subject Requests (DSR). When consumers ask what personal data our customers have or request their personal data be deleted, our customers must comply with these requests. The Lethe team has built a product line that automates this process.
- User can submit their identity to the cookie house app.
- User can submit their identity for data subject requests to the privacy center.
- Customer service representatives can approve data subject requests through the fides UI.
- A download package is returned to the user with their information.
- Users can submit their identity for erasure to the privacy center.
- Customer service representatives can approve erasure requests.
You can use any of your preferred tools, languages, editors, or frameworks to assist here, but please achieve the following:
- A new comprehensive test suite that:
- Covers all acceptance criteria
- Includes both happy path and error scenarios
- Provides clear test documentation
- Is maintainable and extensible
- Includes appropriate logging and reporting
- Handles test data setup and teardown
- Can be run in different environments (staging, production)
- A technical write-up explaining:
- Your testing approach and strategy
- Choice of tools and frameworks with rationale
- Test coverage and scenarios
- Any issues or bugs discovered
- Recommendations for improvement
- Setup instructions for running the tests
- Any assumptions made during implementation
- Areas where additional testing might be needed
- Please work independently without code review by others.
- It's our intention that you spend between 3 and 4 hours on this task.
- This challenge is deliberately vague on detail to give candidates the opportunity for a wide range of solutions. That being said, feel free to reach out and ask questions as needed.
- There is no 100% correct solution, be creative! We are just as interested in your approach to problem solving as we are in your actual solution.
- Remember that we'll schedule a debrief interview with you afterwards to discuss the code and ask questions, so you'll be able to explain what you've done!
- Writing style, code comments, and general readability matter despite this being a test!
Here are some initial links for reference which might come in handy:
Please submit your solution as a GitHub repository containing:
- Complete test suite
- Technical write-up (in markdown format)
- Setup instructions
- Any additional documentation
Email the repository link to the hiring manager when complete. If you have any questions during the challenge, please don't hesitate to reach out to the hiring manager. Good Luck!