You are taking a **forced-choice work-style assessment** as part of the application for an entry-level Software Engineer (SDE I) role. This is the online personality/work-style questionnaire many candidates complete before or alongside the online coding assessment — not a coding test. Each item presents **two statements** separated by `<---->`. You rate which statement is more like you on a 4-point forced-choice scale (there is no neutral middle option): - **1** = the **left** statement is *most* like me - **2** = the **left** statement is *more* like me - **3** = the **right** statement is *more* like me - **4** = the **right** statement is *most* like me For each pair, select the response that best represents a strong, professional software engineer **while remaining internally consistent and authentic**. Within a pair, statements may be (a) both positive, (b) one positive and one neutral/negative, or (c) the same trait worded differently to catch inconsistent answers. **The 35 items:** ``` 1. I look for work where I can build new skills. <----> I will learn new things when I know I will apply them right away. 2. I often choose predictability over the unknown. <----> I adapt to change quickly. 3. I take initiative more than most people but less than some. <----> I wait for clear instruction before trying something new. 4. My team relies on me to check for mistakes. <----> I will occasionally make easy-to-fix mistakes. 5. I usually create a plan before starting my work. <----> I usually deal with problems as they come up. 6. I persist until a task is done. <----> I am about as reliable as everyone else on my team. 7. I am the first to notice an error. <----> I take initiative when asked to. 8. I usually make careful plans to avoid problems. <----> I like applying my existing knowledge to new areas. 9. Sometimes I work hard and sometimes I hardly work. <----> I like surprises. 10. If I notice something needs to be done, I point it out. <----> I notice details that most people miss. 11. I enjoy learning new things from time to time. <----> I always prefer working from a plan. 12. I want most of my co-workers to see me as dependable. <----> I am always looking for new ways to do things. 13. I seek out work that needs to be done. <----> I notice errors that others often miss. 14. Learning new perspectives helps me generate new ideas. <----> I always plan and prioritize my work tasks. 15. I like variety in my work. <----> I am known for getting work done. 16. People would describe me as detail-oriented. <----> I am proactive. 17. The key to completing tasks is having a detailed plan. <----> I like learning about new topics if I have time. 18. Sometimes I am diligent; other times I take a relaxed approach. <----> I am energized by change. 19. I follow plans diligently. <----> My learning interests are varied. 20. I adjust quickly to new settings. <----> Things rarely prevent me from meeting commitments. 21. People tell me I have a keen eye for detail. <----> I take initiative in the areas I am well-informed about. 22. Learning new things gives me more opportunities. <----> I enjoy creating detailed plans. 23. If you can get something mostly complete, you should move on. <----> Constant change is exhausting. 24. I catch more mistakes than most. <----> I am as much of a self-starter as anyone else. 25. I like to learn new things when I have extra time. <----> People describe me as organized. 26. People tell me I am dependable. <----> I am often the first to try new things. 27. I sometimes accept guidance from others. <----> I usually double-check my work. 28. Most projects need a structured plan. <----> Acquiring knowledge from different areas helps me solve problems. 29. I enjoy getting tasks off a to-do list. <----> I adjust to new situations as well as my peers do. 30. I am the first to notice when things change. <----> I will take initiative on well-defined projects. 31. I like applying my current skills to new challenges. <----> Most problems can be avoided by sticking to the plan. 32. Changing my routine inspires me. <----> I rarely lose motivation to work on a task. 33. I try to avoid errors so I do not have to fix things later. <----> When my work is complete, I look for more work. 34. I am a lifelong learner. <----> I produce my best work when working from a detailed plan. 35. New situations are uncomfortable. <----> I give less effort on uninteresting tasks, just like most people do. ``` **Deliverable:** a response (1–4) for each of the 35 items, plus the reasoning rule you used to resolve ambiguous "both-good" pairs. ```hint Answer the sheet, not the item The items aren't independent. Before scoring anything, decide what a small, fixed set of role-relevant work-style traits would say about you, and how you'd *rank* those traits when two of them collide. Then carry that one self-image through all 35 items rather than reacting to each pair in isolation. ``` ```hint Read what each side is really testing For every pair, decide what each statement is probing before you pick. Some pairs put two genuinely-good qualities head to head; others slip a deliberately unflattering statement (careless, passive, change-averse, "average like everyone else") opposite a good one. Treat those two situations very differently — lean hard away from the negatives, lean lightly between two positives. ``` ```hint Mind the strength of your rating, not just the side The 1–4 scale lets you signal *how* strongly, not only *which* side. A top rating (1 or 4) is warranted away from a clearly self-damaging statement; a measured rating (2 or 3) is safer when both sides are positive but in tension. A sheet full of extremes looks invalidly inflated to a forced-choice instrument that *expects* you to trade traits off. ``` ### Constraints & Assumptions > These are working assumptions about how this *style* of instrument behaves, inferred from the item wording — not facts from a published spec. The vendor does not release its scoring, so treat the trait list, the consistency mechanism, and the reverse-keying below as hypotheses to reason from, and say so in your answer. - **Ipsative (forced-choice) scoring.** Because you must pick a side, the score reflects the *relative* strength of traits within you, not absolutes — so you cannot be maximal on everything. Part of the exercise is deciding what that constraint implies for how answers should be distributed. - **Traits that appear to be measured.** The 35 items seem to reuse a small set of work-style dimensions. Reading the wording, plausible dimensions include: **Ownership / proactiveness (bias for action)**, **Dependability / follow-through**, **Attention to detail / quality (high standards)**, **Curiosity / learning agility**, **Adaptability to change**, and **Planning / organization**. Confirming which dimensions are real and how each item loads onto them is part of the task. - **Likely consistency checks.** Several items restate the same idea (e.g. "detail-oriented" vs "keen eye for detail" vs "catch more mistakes than most"). Instruments like this typically penalize wildly different answers to near-duplicate items via a hidden consistency index, so identify the duplicates and decide how to keep them coherent. - **Apparent distractor / reverse-keyed items.** Some statements are deliberately unflattering ("Sometimes I work hard and sometimes I hardly work", "I will occasionally make easy-to-fix mistakes", "New situations are uncomfortable", "Constant change is exhausting"). Decide which statements fall in this category and how that should affect your rating. - **Role context.** Entry-level SDE-1 / new grad. A defensible profile can be anchored to Amazon's Leadership Principles — **Ownership**, **Bias for Action**, **Earn Trust** (dependability), **Insist on the Highest Standards** (quality/detail), and **Learn and Be Curious** — but you should justify the anchor rather than assume it. - **No published answer key.** Vendors do not publish a key; the goal is a defensible, coherent profile, not a "correct" number. Any specific number sequence is *illustrative*, and your answer should flag the uncertainty rather than present numbers as ground truth. ### Clarifying Questions to Ask - Which work-style dimensions does this assessment score, and are any items reverse-keyed or planted purely as consistency checks? - Is there time pressure, and does going back to change an earlier answer to stay consistent help or hurt? - Are statements scored independently, or does the *pattern* across all 35 items (consistency, social-desirability) factor into the result? - Does the role/team weight some traits more than others (e.g. a quality-critical team valuing attention to detail over novelty-seeking)? - Will my answers here be cross-referenced against behavioral-interview stories later? - When both statements in a pair are positive, is it better to commit strongly (1/4) or to lean lightly (2/3)? ### What a Strong Answer Covers - **A coherent persona** anchored to role-relevant competencies (Amazon LPs), applied uniformly rather than item-by-item guessing. - **Per-item pole identification** — naming which trait each side measures and why one side is chosen. - **Distractor handling** — explicitly down-weighting careless / disengaged / change-averse statements. - **Consistency across near-duplicate items** — the same trait scored the same way wherever it reappears. - **A stated tie-break rule** for equally-positive pairs (extremes for core traits, moderate for the rest). - **Awareness of social-desirability and faking limits** — perfect, all-extreme answers look invalidly inflated; authenticity matters because answers must survive a later behavioral interview. - **A concrete, defensible answer set** for all 35 items (not just principles), while noting there is no official key. ### Follow-up Questions - A "perfect" candidate would max every desirable trait, but the instrument is forced-choice — what does that constraint imply about how you should distribute your answers, and how could over-faking be detected? - Two near-duplicate items (e.g. #16 "detail-oriented" vs #21 "keen eye for detail") are scored differently by a candidate — what does the assessment infer, and how would you avoid that? - How should your answers here line up with the STAR stories you'd tell in the behavioral round, and what happens if they contradict? - If a real team you joined valued shipping speed over exhaustive planning, would you change your answers, and is that ethical or strategic?